net0 --> eth0 for Automatic Backdoors

[JJBliss]

I just had to upgrade from 2.5.1 to 2.5.2 (no way am I doing 3.1) because I finally got the local whammy.


I used Superzaps upgrade, but promptly deleted the XPlusZ components, so i could do some of my own stuff.

I did all the hacks I needded by hand, converted the rc.net file to static IP, and took care of everything, I think....

However, Superzaps upgrade load IP on net0. I know this prevents the daily call, but I would prefer to have it on eth0 so that backdoors are enabled automatically.

I tried changing the line from :

/sbin/ifconfig net0 192.168.1.188 netmask 255.255.255.0 up

to

/sbin/ifconfig eth0 192.168.1.188 netmask 255.255.255.0 up

but it didn't work properly.

I think it has something to do with the ax88796.0 driver in /lib/modules but I'm not sure. Was that driver modified to NOT allow eth0 ?

Any suggestions on what I should do, or is there any OTHER way to "automatically" enable backdoors, without running a tcl script that does the appropriate sendkey commands (I know about that way)

JJ Bliss

[BubbleLamp]

Originally posted by JJBliss
I just had to upgrade from 2.5.1 to 2.5.2 (no way am I doing 3.1) because I finally got the local whammy.


I used Superzaps upgrade, but promptly deleted the XPlusZ components, so i could do some of my own stuff.

I did all the hacks I needded by hand, converted the rc.net file to static IP, and took care of everything, I think....

However, Superzaps upgrade load IP on net0. I know this prevents the daily call, but I would prefer to have it on eth0 so that backdoors are enabled automatically.

I tried changing the line from :

/sbin/ifconfig net0 192.168.1.188 netmask 255.255.255.0 up

to

/sbin/ifconfig eth0 192.168.1.188 netmask 255.255.255.0 up

but it didn't work properly.

I think it has something to do with the ax88796.0 driver in /lib/modules but I'm not sure. Was that driver modified to NOT allow eth0 ?

Any suggestions on what I should do, or is there any OTHER way to "automatically" enable backdoors, without running a tcl script that does the appropriate sendkey commands (I know about that way)

JJ Bliss

I believe that version was hacked to load as net0. If you get the driver from Nick's web site (silicondust.com) it will load as eth0, and accepts the command line argument if you wish to change that.

You are attempting to change the name with the ifconfig line, but that will just error since it won't find the eth0 device.

[DarkWing]

the newer turbonet driver can assign the name of the interface when the module is loaded. Look for where the ax8876.o file is loaded.

If it's a mod'd module, then you could get the version on my website, you spec the interface name at the end of the insmod line:
insmod -f /lib/modules/ax88796.o macaddr=040203 timing=5 devicename=net0

[JJBliss]

Originally posted by DarkWing
the newer turbonet driver can assign the name of the interface when the module is loaded. Look for where the ax8876.o file is loaded.

If it's a mod'd module, then you could get the version on my website, you spec the interface name at the end of the insmod line:
insmod -f /lib/modules/ax88796.o macaddr=040203 timing=5 devicename=net0

Thanks DW.
Actually, with Superzaps EBD (Enable Back Doors) code from xPlusz, I don't need the eth0 anymore.

net0 wil suffice, protect me from risk of the daily call, and still allow backdoors automatically

Thanks again
JJ