I read this "That's a routing problem, not a network driver problem. That can happen if the gateway you specified is not reachable *within one hop*. Either you've specified the wrong gateway, the wrong network, or the wrong subnet mask."
(
http://www.beowulf.org/pipermail/rea...ry/000392.html)
So I modified the interfaces file to change from this:
auto eth1
iface eth1 inet static
address 10.0.0.1
netmask 255.255.255.0
gateway 192.168.1.254
to this:
auto eth1
iface eth1 inet static
address 10.0.0.1
netmask 255.255.255.0
gateway 10.0.0.1
And I got the following errors:
$ sudo vi /etc/network/interfaces
$ sudo ifdown eth1
ifdown: interface eth1 not configured
$ sudo ifup eth1
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
$ sudo ifdown eth1
$ sudo ifup eth1
RTNETLINK answers: File exists
run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
(see my last post about /etc/network/if-up.d/avahi-autoipd)
Well, I changed it back to 192.168.1.254 because internet stopped working... my guess here is:
192.168.1.254 is two hops far from 10.0.0.1 (192.168.1.10 is in the middle) so that's why it's telling me network is unreachable. So the question should be:
does eth1 really needs a gateway? and if it needs it which one is the best candidate?
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
200.76.191.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth2
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth3
0.0.0.0 200.76.191.3 0.0.0.0 UG 0 0 0 eth2