MESSAGE
DATE | 2014-08-16 |
FROM | Ruben Safir
|
SUBJECT | Subject: [NYLXS - HANGOUT] networking puzzle
|
My current setup for my server in the house is a fit/pc connected to a optimum static subnet that is described as follows
eth1 Link encap:Ethernet HWaddr 00:01:C0:09:A6:09 inet addr:96.57.23.82 Bcast:96.57.23.87 Mask:255.255.255.248 inet6 addr: fe80::201:c0ff:fe09:a609/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2290256 errors:0 dropped:0 overruns:0 frame:0 TX packets:3117484 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:741616664 (707.2 Mb) TX bytes:3512272625 (3349.5 Mb)
I use an internal set up that is described as follows
www:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:01:C0:09:A6:08 inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::201:c0ff:fe09:a608/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:773973 errors:0 dropped:0 overruns:0 frame:0 TX packets:916441 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:71336040 (68.0 Mb) TX bytes:728493565 (694.7 Mb)
My routing has behaved very strangely since I've had this setup and it is a real mystery to me as to why it seems to be broken.
The current routing is as follows
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1 10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0 96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1 96.57.23.81 0.0.0.0 255.255.255.255 UH 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
This is extreme overkill It should work like this
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 96.57.23.82 0.0.0.0 UG 0 0 0 eth1 10.0.0.0 10.0.0.5 255.255.255.0 UG 0 0 0 eth0 96.57.23.80 96.57.23.82 255.255.255.248 UG 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
This defines the internal route to 10.0.0.0 connecting through 10.0.0.5 and that works.
the external network should work as defined at 96.57.23.80 through 96.57.23.82 which is eth1. This seems to work since I can ping 96.57.23.81 which is the cable modem gateway.
However 0.0.0.0 through 96.57.23.82 fails misserably. It won't route out unless I explicitely define 96.57.23.81 as a host routed through eth1 and only then can I add another default
0.0.0.0 96.57.23.81 0.0.0.0 UG 0 0 0 eth1
This shouldn't be necessary. What am I missing here?
Ruben
|
|