Very strange, multiple IP addresses on the same Ethernet carddo not route properly
in [Linux Networking]
|
Prev: Very strange, multiple IP addresses on the same Ethernet card donot route properly
Next: Reserved addresses in subnet & Number of subnets
From: unruh on 10 Jan 2010 18:53 ["Followup-To:" header set to comp.os.linux.networking.] On 2010-01-10, Ignoramus27261 <ignoramus27261(a)NOSPAM.27261.invalid> wrote: > I have a small IP subnet to myself (16 IP addresses, actually 13 after > subtracting router .1, .0, and broadcast .15). > > I used to have an old Fedora server that used to serve almost the > whole subnet. Always worked great, I had eth0:1 ... etho:11 or so > addresses and all worked. > > I am omving to a new Ubuntu server (Ubuntu Hardy). > > If I delete an interface on the old server, and create it (with the > same ifconfig command as on Fedora) on Ubuntu, the IP address is > created. It is also visible from the subnet, as in, I can telnet to > this IP:80 from the old server (and get results clearly indicate that > it is properly on the new server). > > However, the IP, if hosted on the new server, is not reachable from > outside of the subnet. > > The only difference in routing that I see between the old and new > server, is "Metric". > > (the 10.0.0.0 route is a leftover from when the server was set up on my home network). > > The old server network card s eth0 and the new one is eth1. No, both eth0 and eth1 are on the old system. eth0 was a connection out to the world and eth1 was the internal network. On the new system you only have one network, it is installed on eth1 and connects to the outside world. What I suspect is that your ethernet lines have gotten misnumbered. What does ifconfig say? > > OLD::~==>/sbin/route -n |grep -v ' lo' > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 65.182.171.160 0.0.0.0 255.255.255.240 U 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 > 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth1 > 0.0.0.0 65.182.171.161 0.0.0.0 UG 0 0 0 eth0 > > NEW::~==>route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 65.182.171.160 0.0.0.0 255.255.255.240 U 0 0 0 eth1 > 0.0.0.0 65.182.171.161 0.0.0.0 UG 100 0 0 eth1 > > So, why is the new server not routing properly, is what puzzles me at the moment. Because it is doing what you ( or probably the system) told it to do. > > I tried both ifconfig, as well as /etc/network/interfaces, it makes no difference). Why do you not show us what ifconfig says. Also tell us what you want to do. Note that any address 10.x.x.x CANNOT be addressed from outside the local network. those are private addresses, and no public router recognizes them-- ie throws them away. That are probably a thousand machines on the net labeled 10.0.0.1 > > i
From: Ignoramus27261 on 10 Jan 2010 19:21 On 2010-01-10, unruh <unruh(a)wormhole.physics.ubc.ca> wrote: > ["Followup-To:" header set to comp.os.linux.networking.] > On 2010-01-10, Ignoramus27261 <ignoramus27261(a)NOSPAM.27261.invalid> wrote: >> I have a small IP subnet to myself (16 IP addresses, actually 13 after >> subtracting router .1, .0, and broadcast .15). >> >> I used to have an old Fedora server that used to serve almost the >> whole subnet. Always worked great, I had eth0:1 ... etho:11 or so >> addresses and all worked. >> >> I am omving to a new Ubuntu server (Ubuntu Hardy). >> >> If I delete an interface on the old server, and create it (with the >> same ifconfig command as on Fedora) on Ubuntu, the IP address is >> created. It is also visible from the subnet, as in, I can telnet to >> this IP:80 from the old server (and get results clearly indicate that >> it is properly on the new server). >> >> However, the IP, if hosted on the new server, is not reachable from >> outside of the subnet. >> >> The only difference in routing that I see between the old and new >> server, is "Metric". >> >> (the 10.0.0.0 route is a leftover from when the server was set up on my home network). >> >> The old server network card s eth0 and the new one is eth1. > > No, both eth0 and eth1 are on the old system. eth0 was a connection out > to the world and eth1 was the internal network. > On the new system you only have one network, it is installed on eth1 and > connects to the outside world. > What I suspect is that your ethernet lines have gotten misnumbered. No. Both old and new server have eth0 and eth1, respectively. The old server has eth0 for the main ethernet line. The new server has eth1 for the main ethernet line. Two outputs of "route -n" were done on two separate servers. > What does > ifconfig > say? > On old server, with IP address activated eth0:3 Link encap:Ethernet HWaddr 00:30:48:74:5B:09 inet addr:65.182.171.165 Bcast:65.182.171.165 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Base address:0xb400 Memory:fea60000-fea80000 On new server, with IP address activated: eth1:3 Link encap:Ethernet HWaddr 00:30:48:7f:20:48 inet addr:65.182.171.165 Bcast:65.255.255.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:217 Base address:0xc000 (obviously I try to make sure that they are not up at the same time). The bcast on the old server seems wrong, but it does not matter and everything works anyway. >> >> OLD::~==>/sbin/route -n |grep -v ' lo' >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 65.182.171.160 0.0.0.0 255.255.255.240 U 0 0 0 eth0 >> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 >> 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth1 >> 0.0.0.0 65.182.171.161 0.0.0.0 UG 0 0 0 eth0 >> >> NEW::~==>route -n >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 65.182.171.160 0.0.0.0 255.255.255.240 U 0 0 0 eth1 >> 0.0.0.0 65.182.171.161 0.0.0.0 UG 100 0 0 eth1 >> >> So, why is the new server not routing properly, is what puzzles me at the moment. > > Because it is doing what you ( or probably the system) told it to do. Yes, but what exactly. > >> >> I tried both ifconfig, as well as /etc/network/interfaces, it makes no difference). > > Why do you not show us what ifconfig says. See above > Also tell us what you want to do. I want to make sure that when an external (to the subnet) IP connects to 65.182.171.165:80, connections occur and work properly. > Note that any address 10.x.x.x CANNOT be addressed from outside the > local network. those are private addresses, and no public router > recognizes them-- ie throws them away. > > That are probably a thousand machines on the net labeled 10.0.0.1 Yes, but I do not care about 10.0.0. routing. i
From: Pascal Hambourg on 11 Jan 2010 05:02 Hello, Ignoramus27261 a �crit : > > I want to make sure that when an external (to the subnet) IP connects > to 65.182.171.165:80, connections occur and work properly. Is the problem solved ? It works for me : $ tcptraceroute 65.182.171.165 [...] 10 65.182.183.150 164.545 ms 165.194 ms 165.175 ms 11 65.182.178.109 163.803 ms 163.825 ms 164.157 ms 12 65.182.171.165 [open] 164.250 ms 164.109 ms 165.336 ms
From: Ignoramus21069 on 11 Jan 2010 09:56 On 2010-01-11, Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: > Hello, > > Ignoramus27261 a ?crit : >> >> I want to make sure that when an external (to the subnet) IP connects >> to 65.182.171.165:80, connections occur and work properly. > > Is the problem solved ? It works for me : > $ tcptraceroute 65.182.171.165 > [...] > 10 65.182.183.150 164.545 ms 165.194 ms 165.175 ms > 11 65.182.178.109 163.803 ms 163.825 ms 164.157 ms > 12 65.182.171.165 [open] 164.250 ms 164.109 ms 165.336 ms No, it is not solved, I simply restored the IP on the old server by now. The old server is over 5 years old, and I want to decommission it ASAP. (having to pay for two servers does not help, either). i
From: Tauno Voipio on 11 Jan 2010 11:22
Ignoramus21069 wrote: > On 2010-01-11, Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: >> Hello, >> >> Ignoramus27261 a ?crit : >>> I want to make sure that when an external (to the subnet) IP connects >>> to 65.182.171.165:80, connections occur and work properly. >> Is the problem solved ? It works for me : >> $ tcptraceroute 65.182.171.165 >> [...] >> 10 65.182.183.150 164.545 ms 165.194 ms 165.175 ms >> 11 65.182.178.109 163.803 ms 163.825 ms 164.157 ms >> 12 65.182.171.165 [open] 164.250 ms 164.109 ms 165.336 ms > > No, it is not solved, I simply restored the IP on the old server by > now. The old server is over 5 years old, and I want to decommission it > ASAP. (having to pay for two servers does not help, either). > > i The broadcast address on the new server does not match the IP and netmask of the Ethernet interface. What should the network be, and what are the other Ethernets? Please show the whole ifconfig output. -- Tauno Voipio |