On 9 August 2011 18:51, Darac Marjal <[email protected]> wrote:
>
> Here's your problem. eth0 has no address. The only IPv4 connectivity you
> have is to 127.0.0.1/255.0.0.0 via lo (below). Your computer has no way
> to reach 192.168.1.254 so is legitimately returning "Network is
> unreachable".
>
> Try the following command:
>
> # ip addr add 192.168.1.1 broadcast 192.168.1.255 dev eth0
>
Done!
and /sbin/ifconfig now looks like this:
Bandit:/home/weaver# /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.255
inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21888 (21.3 KiB) TX bytes:21435 (20.9 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12246 errors:0 dropped:0 overruns:0 frame:0
TX packets:12246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:955628 (933.2 KiB) TX bytes:955628 (933.2 KiB)
>
> then point your web browser to "http://192.168.1.254";.
With two separate browsers, the same message - "Network is unreachable"
Restarted the modem, same result.
> As Camaléon and
> others have pointed out, you need to have an address on the same subnet
> as your router to be able to talk to it. Often, this is done with DHCP,
> but you may not have that set up if you've previously configured the
> router.
>
This is brand new.
The second one after I took the first one back, thinking it had a firmware
problem.
Thanks.
Regards,
Weaver.
--
Religion is regarded by the common people as true,
by the wise as false,
and by the rulers as useful.
— Lucius Annæus Seneca.
Terrorism, the new religion.
