On Sun, Oct 11, 2009 at 10:00 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Sun, Oct 11, 2009 at 04:10:03PM -0500, Rob Townley wrote: >> So when an add-in PCI NIC has a lower MAC than the motherboard NICs, >> the add-in cards will come before the motherboard NICs. i don't like it. > > Huh? Have you used the MAC persistant rules? If you add a new card, > what does it pick for it? i have a hp-dl360 (two nics) with a fibre optic add in nic. On a fresh install, the add-in is eth0. i didn't like it, but ran it for years. > >> But please whatever is done, make sure ping and tracert still works when >> telling it to use a ethX source interface: >> >> eth0 = 4.3.2.8, the default gateway is thru eth1. >> ping -I eth0 208.67.222.222 FAILS >> ping -I 4.3.2.8 208.67.222.222 WORKS >> tracert -i eth0 -I 208.67.222.222 FAILS >> tracert -s 4.3.2.8 -I 208.67.222.222 WORKS >> tracert -i eth0 208.67.222.222 FAILS >> tracert -s 4.3.2.8 208.67.222.222 WORKS > > Again, is what we currently have broken? I am confused as to what this > is referring to. Yes, ping and traceroute are broken at least on Fedora, CentOS, and busybox. On a multinic, multigatewayed machine, passing ethX instead of the IP address will give the false result: "Destination Host Unreachable" when the machine's default gateway is reached thru the other nic. In the following example, the default gateway is thru eth1, not eth0. Pay attention to the text between the '*****'. ping -c 1 -B -I eth0 208.67.222.222 PING 208.67.222.222 (208.67.222.222) from ***** 4.3.2.8 eth0*****: 56(84) bytes of data. >From 4.3.2.8 icmp_seq=1 Destination Host Unreachable #ping -c 1 -B -I 4.3.2.8 208.67.222.222 PING 208.67.222.222 (208.67.222.222) from ***** 4.3.2.8 *****: 56(84) bytes of data. 64 bytes from 208.67.222.222: icmp_seq=1 ttl=55 time=562 ms > > greg k-h > -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
