router hacking

johnh10000 · 03-21-2010, 02:54 AM

Hi folks, for the soul perpose of hacking a orange live box, i need to change my ip to something on 10.0.0 subnet.

I have tried this but i only get loopback / localhost.
http://www.jonathanmoeller.com/screed/?p=1291

the destuctions for the hack are here
http://www.agp.dsl.pipex.com/command_prompt1.html

and something similar are here

http://www.dbzoo.com/livebox/firmwar...vebox_recovery

I am presuming i set in the router broadcast ip as 10.0.0.1
and my ip to be 10.0.0.2

devwatchdog · 03-21-2010, 03:22 AM

Your broadcast IP is the result of whatever subnet/netmask you're using.

You can use a tool named 'ipcalc' to see what your broadcast IP is, plus whatever other information you'll need regarding the network config.

Example:

Code:

jcwx@haley:/etc/dhcp3$ ipcalc 10.0.0.0/24
Address:   10.0.0.0             00001010.00000000.00000000. 00000000
Netmask:   255.255.255.0 = 24   11111111.11111111.11111111. 00000000
Wildcard:  0.0.0.255            00000000.00000000.00000000. 11111111
=>
Network:   10.0.0.0/24          00001010.00000000.00000000. 00000000
HostMin:   10.0.0.1             00001010.00000000.00000000. 00000001
HostMax:   10.0.0.254           00001010.00000000.00000000. 11111110
Broadcast: 10.0.0.255           00001010.00000000.00000000. 11111111
Hosts/Net: 254                   Class A, Private Internet

jcwx@haley:/etc/dhcp3$

In the instance above, you can use any IP address from 10.0.0.1 to 10.0.0.254 when your netmask is 255.255.255.0 for your system. The example you provided from pipex.com indicates that the "orange live box" as you describe it is using IP 10.0.0.1, whereas the system that is being used to communicate with it is 10.0.0.2. Whatever IP you use is irrelevant, as long as it is between 10.0.0.1 & 10.0.0.254 and isn't the same as the router, and you use it instead of the 10.0.0.2 address in those instructions. In any event, your broadcast IP (or the router's) isn't going to be 10.0.0.1.

I looked at the second site you included. That one uses a completely different network scheme. You're going to have to figure out how the network is configured on the Livebox before you can proceed. Is there some sort of a management interface on it where networking is configured? That would be the easiest way. Otherwise, you could use tcpdump on the interface connected to it on your computer to capture traffic coming from it. Set up tcpdump, then boot the Livebox. It isn't guaranteed, but you'll probably see something coming from it.

If you are using it now does it have a DHCP server running on it? If it does, then the default gateway it assigns is the IP address you need to target. If this device runs in some sort of a bridged mode, then that might not work. I looked it up, and I'm guessing it probably does have a DHCP server running on it.

johnh10000 · 03-21-2010, 03:33 AM

Quote:

Originally Posted by devwatchdog

Your broadcast IP is the result of whatever

I looked at the second site you included. That one uses a completely different network scheme. You're going to have to figure out how the network is configured on the Livebox before you can proceed. Is there some sort of a management interface on it where networking is configured? That would be the easiest way. Otherwise, you could use tcpdump on the interface connected to it on your computer to capture traffic coming from it. Set up tcpdump, then boot the Livebox. It isn't guaranteed, but you'll probably see something coming from it.

well there's a box one can buy/make, but on sunday thats tricky. I thought that both sites said to change the lan ip to 10.0.0.1, how are they differant?

If you are using it now does it have a DHCP server running on it? If it does, then the default gateway it assigns is the IP address you need to target. If it this device runs in some sort of a bridged mode, then that might not work. I looked it up, and I'm guessing it probably does have a DHCP server running on it.[/QUOTE]
yep it does by defult but the hack says to yurn it off. so i do that, and of course can't talk to it

will try and figure out the ip numbers, if you don't get a response the livebox, on my ubuntu ftp server.

oh and the objective is for my friend who has a blackbury, and virginmedia, and wants wifi. I have tried with a bt homehub 2a, but win and linux refuse to talk to it via the parrell port. i found the livebox the other week.

devwatchdog · 03-21-2010, 04:37 AM

Quote:

Originally Posted by johnh10000

well there's a box one can buy/make, but on sunday thats tricky. I thought that both sites said to change the lan ip to 10.0.0.1, how are they differant?

The second site doesn't mention 10.0.0 anything. Everything they discuss involves the 10.7.58/24 network.

Quote:

yep it does by defult but the hack says to yurn it off. so i do that, and of course can't talk to it

You will have to set a static IP address in Network Manager on Ubuntu. If you follow the instructions on the first site, then you will set it up to have 10.0.0.2 as the IP, netmask at 255.255.255.0 and a gateway of 10.0.0.1. If you set these parameters with ifconfig when the interface isn't active, where the Livebox isn't running, when the Livebox is booted, Network Manager will reset the interface to whatever it has configured, thereby changing your 10.0.0.2 address to whatever it is using.

I have been screwing around with some networking stuff over the last few days, and have grown to despise Network Manager in Gnome. It has a bad habit of requiring one to enter a default gateway for a static IP address on an interface - which is all well and good if you're only using one interface. I have a wireless connection that I use for communication with a cable modem, which provides a default gateway. When I use Network Manager to configure a static IP on an ethernet port, when it comes up the unneeded gateway displaces the proper one.

I'm damn near removing it now. It's a PITA. I've got scripts I use on other Linux & OpenBSD systems that do the job well enough for wireless and everything else I need.

Once you have everything set up the way you think it should be, run this command in a terminal:

ifconfig

You should see the ethernet interface you just configured there, with the 10.0.0.2 address. There will be an interface identification assigned to it that more than likely will start with 'eth'. Take that interface ID and enter it in this command in a terminal:

sudo tcpdump -nni ethX

replace 'ethX' with eth0, eth1, or whatever shows up in the results of ifconfig.

Then start the process you have of booting the Livebox. You should see traffic coming into the port. Seeing it is going to a ftp server you have set up on your system, there should be traffic destined for port 21 on 10.0.0.2

Also, there is a chance that when you run ifconfig, that you will see something like this:

Code:

jcwx@haley:/etc/dhcp3$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0f:1f:1d:08:4a  
          inet6 addr: fe80::20f:1fff:fe1d:84a/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:508529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:994007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:44702072 (44.7 MB)  TX bytes:1481122392 (1.4 GB)
          Interrupt:18

The IP address is absent because either the cable is unplugged, or the ethernet port the interface is connected to, which in your case will be the Livebox, isn't powered up. When I power up the device the cable is connected to, the interface then shows this:

Code:

jcwx@haley:/etc/dhcp3$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0f:1f:1d:08:4a  
          inet addr:10.xx.23.18  Bcast:10.xx.23.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:1fff:fe1d:84a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:508529 errors:0 dropped:0 overruns:0 frame:0
          TX packets:994038 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:44702072 (44.7 MB)  TX bytes:1481126561 (1.4 GB)
          Interrupt:18

That's pretty annoying behavior. Probably the result of Network Manager's generally annoying antics.

Quote:

will try and figure out the ip numbers, if you don't get a response the livebox, on my ubuntu ftp server.

oh and the objective is for my friend who has a blackbury, and virginmedia, and wants wifi. I have tried with a bt homehub 2a, but win and linux refuse to talk to it via the parrell port. i found the livebox the other week.

If you follow the instructions I saw on the first site, it all seems fairly straighfoward. (heh)

I know that in a perfect world, all instructions would work. We all know this isn't a perfect world, however.

Disable the DHCP server on the Livebox, give it an IP address of 10.0.0.1 netmask 255.255.255.0, then on your system 10.0.0.2 netmask 255.255.255.0.

When you change the IP address of the Livebox, at the point of which you make that change, you will lose connectivity with the Livebox. This is when you will have to change your IP to 10.0.0.2

johnh10000 · 03-21-2010, 05:28 AM

Quote:

If you follow the instructions I saw on the first site, it all seems fairly straighfoward. (heh)

I know that in a perfect world, all instructions would work. We all know this isn't a perfect world, however.

Disable the DHCP server on the Livebox, give it an IP address of 10.0.0.1 netmask 255.255.255.0, then on your system 10.0.0.2 netmask 255.255.255.0.

When you change the IP address of the Livebox, at the point of which you make that change, you will lose connectivity with the Livebox. This is when you will have to change your IP to 10.0.0.2

[/quote]

Thanks for that, now it's sat on 10.0.0.1 i'm on 10.0.0.2 now to pursuade it to run the linux commands, via the backport. My ftp server is silently very board, not an access since 6:30 this morn, livebox should have grabbed the telnetd by now

devwatchdog · 03-21-2010, 12:19 PM

Quote:

Originally Posted by johnh10000

Thanks for that, now it's sat on 10.0.0.1 i'm on 10.0.0.2 now to pursuade it to run the linux commands, via the backport. My ftp server is silently very board, not an access since 6:30 this morn, livebox should have grabbed the telnetd by now

Yes, it should have finished within a minute actually. I uploaded a 3 meg image to a device yesterday that took a matter of seconds.

The Livebox should have rebooted after uploading the image. You should be able to access it now if the image transfered ok.

You can see if it is available with nmap:

nmap 10.0.0.0/24

That should show you a device at 10.0.0.1, with whatever services the new firmware has available on the network. You might have to download nmap with:

sudo apt-get install nmap

as I don't think it is part of the default install. Might be, don't remember.