How to not get your NIC MAC blackisted...

[cockneysean]

I just tested a theory there, which may clear up some issues for some.

When you are sniffing for and testing various MACs, you need to change the NIC MAC every time ideally.

I just changed MAC 4 times, the changed back to my working MAC, connected for 5 mins, then BANG; activation page.

I then changed the MAC of my router, and now I am back working again.

So if you are persistently getting the activation page then you need to be changin your NIC MAC;

TL;DR - Every time you change HFC MAC, change NIC MAC too.

[fitz]

Well spotted. That certainly never used to happen.

I find best Mac change process is:
change modem MAC, save settings but don't reboot the modem
change your nic mac + apply
reboot modem

cheers, fitz

[MorriSoft]

Originally Posted by fitz

Well spotted. That certainly never used to happen.

I find best Mac change process is:
change modem MAC, save settings but don't reboot the modem
change your nic mac + apply
reboot modem

cheers, fitz

Exactly how I do it.

Fitz, i appologise mate, i didnt manage to get online last night - unforeseen problems with my ex missus!

Will still be testing that other modem with the older haxorware on it tonight though, so here to hoping

[fitz]

Thats cool mate. An updated version should be in downloads here later. 0.1c seemed to fix some completely, extend times between reboots for many and do nothing for a few.

In the updated one i've put in pretty much every idea from everyone that i've read about.

Mines on....but then it's been fine since the very 1st ver of the dump i did.

If your connection craps out, PM me, i'll give you my email so you can send me the telnet logs. Or you can convert it into an image and put it in photobucket...then link to it from your post....which is pretty much the only way to post them on this forum. Talk about having to reinvent the wheel.

If no-one can see exactly what the problem is...it's not going to get fixed.

cheers, fitz

[MorriSoft]

Originally Posted by fitz

Thats cool mate. An updated version should be in downloads here later. 0.1c seemed to fix some completely, extend times between reboots for many and do nothing for a few.

In the updated one i've put in pretty much every idea from everyone that i've read about.

Mines on....but then it's been fine since the very 1st ver of the dump i did.

If your connection craps out, PM me, i'll give you my email so you can send me the telnet logs. Or you can convert it into an image and put it in photobucket...then link to it from your post....which is pretty much the only way to post them on this forum. Talk about having to reinvent the wheel.

If no-one can see exactly what the problem is...it's not going to get fixed.

cheers, fitz

I wish to look into this deeply, as i genuinely have an interest in the way the whole system works. As mentioned, I have a subbed 20 meg modem, which, im going to check the logs over for parricull, in turn these may have some clues to whats been happening.

I will also try to fire up both modems, older haxorware first, to see where I can get with it, I believe i now have no more macs that are valid though.

[fitz]

Originally Posted by morrisoft

I wish to look into this deeply, as i genuinely have an interest in the way the whole system works. As mentioned, I have a subbed 20 meg modem, which, im going to check the logs over for parricull, in turn these may have some clues to whats been happening.

I will also try to fire up both modems, older haxorware first, to see where I can get with it, I believe i now have no more macs that are valid though.

If you're in pure ntl...use dhcpsniffer on your subbed modem...put your subbed mac in the discover box, then do a brute force.

[cockneysean]

Bumping for great justice....

[fitz]

VM, your BPI has no chance to survive...make your time

cheers, fitz

[Ciwan]

What actually happens when you tick BruteForce in DHCP Sniffer ?

Can someone please explain.

Thanks

[cockneysean]

I'm not entirely sure of the ins and outs, but it basically finds MACs from outside your node.

I think probably by sending fake packets or something then waiting to see if there is a response.