On Mon, 20 Sep 2004 18:16:20 +0200, Jacob Larsen wrote: > > Sergio Basurto wrote: > > can you ping the ethernet cards within the server? > > Yes. > > > if you run > > shell~#ifconfig > > what is the output? > > # ifconfig > bond0 Link encap:Ethernet HWaddr 00:0F:20:7A:7A:53 > inet addr:81.7.167.228 Bcast:81.255.255.255 > Mask:255.255.255.240 > UP BROADCAST RUNNING MASTER MULTICAST > MTU:1500 Metric:1 > RX packets:1494 errors:0 dropped:0 > overruns:0 frame:12 > TX packets:809 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:21 txqueuelen:0 > RX bytes:112805 (110.1 KiB) TX bytes:99044 > (96.7 KiB) > > eth0 Link encap:Ethernet HWaddr 00:0F:20:7A:7A:53 > inet addr:81.7.167.226 Bcast:81.255.255.255 > Mask:255.255.255.240 > UP BROADCAST RUNNING SLAVE MULTICAST > MTU:1500 Metric:1 > RX packets:1037 errors:0 dropped:0 > overruns:0 frame:6 > TX packets:403 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:11 txqueuelen:1000 > RX bytes:77395 (75.5 KiB) TX bytes:48278 > (47.1 KiB) > Interrupt:18 > > eth1 Link encap:Ethernet HWaddr 00:0F:20:7A:7A:52 > inet addr:81.7.167.227 Bcast:81.255.255.255 > Mask:255.255.255.240 > UP BROADCAST RUNNING SLAVE MULTICAST > MTU:1500 Metric:1 > RX packets:457 errors:0 dropped:0 overruns:0 > frame:6 > TX packets:406 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:10 txqueuelen:1000 > RX bytes:35410 (34.5 KiB) TX bytes:50766 > (49.5 KiB) > Interrupt:19 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:402 errors:0 dropped:0 overruns:0 > frame:0 > TX packets:402 errors:0 dropped:0 overruns:0 > carrier:0 > collisions:0 txqueuelen:0 > RX bytes:42547 (41.5 KiB) TX bytes:42547 > (41.5 KiB) > > > and if you run > > shell~#route -n > > what is the output? > > # route -n > Kernel IP routing table > Destination Gateway Genmask Flags > Metric Ref Use > Iface > 81.7.167.224 0.0.0.0 255.255.255.240 U
> 0 0 eth0 > 81.7.167.224 0.0.0.0 255.255.255.240 U > 0 0 eth1 > 81.7.167.224 0.0.0.0 255.255.255.240 U > 0 0 > bond0 > 0.0.0.0 81.7.167.225 0.0.0.0 UG > 0 0 > bond0 > 0.0.0.0 81.7.167.225 0.0.0.0 UG > 0 0 eth1 > 0.0.0.0 81.7.167.225 0.0.0.0 UG > 0 0 eth0 ---------------------------------------------------- When bonding is set up with the ARP monitor, it is important that the slave devices not have routes that supercede routes of the master (or, generally, not have routes at all). For example, suppose the bonding device bond0 has two slaves, eth0 and eth1, and the routing table is as follows: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth0 10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 eth1 10.0.0.0 0.0.0.0 255.255.0.0 U 40 0 0 bond0 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo In this case, the ARP monitor (and ARP itself) may become confused, because ARP requests will be sent on one interface (bond0), but the corresponding reply will arrive on a different interface (eth0). This reply looks to ARP as an unsolicited ARP reply (because ARP matches replies on an interface basis), and is discarded. This will likely still update the receive/transmit times in the driver, but will lose packets. The resolution here is simply to insure that slaves do not have routes of their own, and if for some reason they must, those routes do not supercede routes of their master. This should generally be the case, but unusual configurations or errant manual or automatic static route additions may cause trouble. From:"Linux Ethernet Bonding Driver mini-howto" ----------------------------------------------------- > > > On Mon, 20 Sep 2004 17:14:51 +0200, Jacob Larsen > wrote: > >>I can ping my server, and the gateway from my home pc, > >>but can not ping > >>the gateway nor another server on the same subnet from > >>the server. > >>I use bond0 for eth0 and eth1. > >>When I clear iptables there is no change. > >> > >>Any ideas? Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
