Wierd going on's with tftip 10.137.103.2

[reptilianman]

Hi everyone need some help can anyone get a stable connection with tftip 10.137.103.2 as i have been using a 20meg mac in a dynamic area with felix's test fix 0.2 for around 8 months on this server.

All of a sudden two days ago i got kicked from the server and nothing i can do will help me get the mac working again. i have enabled bpi+ 1.1 and set my adapter to 192.168.100.10 by doing this i am able to get back into haxoware to check settings ect and it shows the mac as being operational BUT when i set the ip to be determined by the server the default gateway will not give me a valid IP to surf with resulting in limited or no connectivity???

Prior to this i have noticed now that all connections from various macs that i have scanned for if any lead to tftip 10.137.103.2 then they will show operational in Hax but no default gateway IP is issued. Unfortunately all these macs would appear to be or i have a suspicion that there are 20meg macs

Can anyone shed some light on this as all i can seem to get working are 10 and 2meg macs as they point to other tftip's thank you.

[scott27]

20 megs are abit odgey just now pal, why not try a 10mb see what happens, i havesame tftp m8, ive been fine for months, what area are u in?

scott

[sr20]

Originally Posted by reptilianman

Hi everyone need some help can anyone get a stable connection with tftip 10.137.103.2 as i have been using a 20meg mac in a dynamic area with felix's test fix 0.2 for around 8 months on this server.

All of a sudden two days ago i got kicked from the server and nothing i can do will help me get the mac working again. i have enabled bpi+ 1.1 and set my adapter to 192.168.100.10 by doing this i am able to get back into haxoware to check settings ect and it shows the mac as being operational BUT when i set the ip to be determined by the server the default gateway will not give me a valid IP to surf with resulting in limited or no connectivity???

Prior to this i have noticed now that all connections from various macs that i have scanned for if any lead to tftip 10.137.103.2 then they will show operational in Hax but no default gateway IP is issued. Unfortunately all these macs would appear to be or i have a suspicion that there are 20meg macs

Can anyone shed some light on this as all i can seem to get working are 10 and 2meg macs as they point to other tftip's thank you.

Enabling BPI+ in the Haxor GUI won't do anything mate as you don't have valid certs for the MAC. But yeah it's likely BPI+ being now forced on the CMTS that's stopping it from working.

Just go with 10/2m while they still work

sr20

[reptilianman]

Hi scott27 im on the ash which i think stands for the ashton server if that's any help to you.

sr20 thanx for the reply finally some proper definitive information on this problem i thought in these versions of hax that we use now the certs were dumped from a valid modem and can be generated within hax??? would updating my modem soft to the original latest version of hax do anything for me?

So is 20meg officially a thing of the past now with no possible bypass or fix just asking its a nice connection after all.

yep 10meg works fine no problem logs onto a different tftip as stated in my first post. Thanx again looking forward to your reply as ive been unable to keep up with whats been going on.

[sr20]

Originally Posted by reptilianman

Hi scott27 im on the ash which i think stands for the ashton server if that's any help to you.

sr20 thanx for the reply finally some proper definitive information on this problem i thought in these versions of hax that we use now the certs were dumped from a valid modem and can be generated within hax??? would updating my modem soft to the original latest version of hax do anything for me?

So is 20meg officially a thing of the past now with no possible bypass or fix just asking its a nice connection after all.

yep 10meg works fine no problem logs onto a different tftip as stated in my first post. Thanx again looking forward to your reply as ive been unable to keep up with whats been going on.

A lot of the dumps for VM floating about have valid BPI keys dumped from subs, but Haxorware writes its own BPI+ certificates everytime you change the MAC. Haxorware 'tries' to make certificates but doesn't really do a good of making anything useable on VM. It makes Motorola certificates rather than the required Ambit ones, and they're not a very good copy of legit ones even then.

They don't work for us and get you a 'permanent authorisation failure' in the event log as confirmation. I'm sure people will work on other vunerabilities in the system, not sure if they'll get released as easily as prev hacks though.

It'll get harder to find working MACs as even 10 and eventually 2meg go over to Docsis 1.1. The 'free upgrade' VM did recently for 2m customers not only only went from 2m to 10m, but also from Docsis 1.0 to 1.1 (with BPI+). Make of that what you will.

Yeah for now 10m and 2m works pretty easily, that's likely to change as more MACs move to docsis 1.1. Then it'll be about finding the needle in the haystack MAC that for some reason has stayed on the 1.0 system..like it is for 20m now.

sr20

[G77]

yup, list of macs as long as your arm from just about every ubr in lancs. 2 x 20mbit still on 1.0. mine, lol.

[reptilianman]

Hopefully when all macs like 2mb and 10mb dissapere on bpi+1.1 those who know allot about these things will be stimulated into finding other exploits or improve on haxowares ability to make proper certs for various modem types as well. can only wait it out and dream right now im happy with 10meg but it wont last as ive already noticed a significant decline in the amount of macs dhcp sniffer returns under brute mode so.............

[eshaq786]

Have you tried resorting to just using mac that is on 20mb? That should pull the dynamic config for the 20mb mac and therefore you shouldn't need to use the tftp ip server 10.137.103.2 .