Unable to ping gateway
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? Best regards Jacob Larsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
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? Best regards Jacob Larsen ifconfig? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
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? ifconfig? # 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 loLink 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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
can you ping the ethernet cards within the server? if you run shell~#ifconfig what is the output? and if you run shell~#route -n what is the output? 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? Best regards Jacob Larsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
can you ping your ethernet cards from within the server? if you run shell~#ifconfig what is the output? if you run shell~#route -n what is the output? 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? Best regards Jacob Larsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
On Mon, 2004-09-20 at 08:47, 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. 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 11100010 -- .226 -- mask This gives you 15 addresses. Why is the broadcast address not one of these 15? The broadcast should be 81.7.167.239 which is the highest address you have using that netmask. Not? I really don't know what bond0 is so I may be missing something. signature.asc Description: This is a digitally signed message part
Re: Unable to ping gateway
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 loLink 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 RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG0 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG0 00 eth1 0.0.0.0 81.7.167.2250.0.0.0 UG0 00 eth0 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? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Eric Gaumer wrote: On Mon, 2004-09-20 at 08:47, 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. 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 11100010 -- .226 -- mask This gives you 15 addresses. Why is the broadcast address not one of these 15? The broadcast should be 81.7.167.239 which is the highest address you have using that netmask. Not? I am a novice in this area. Could this help: # cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 81.7.167.226 netmask 255.255.255.240 gateway 81.7.167.225 auto eth1 iface eth1 inet static address 81.7.167.227 netmask 255.255.255.240 gateway 81.7.167.225 auto bond0 iface bond0 inet static address 81.7.167.228 netmask 255.255.255.240 gateway 81.7.167.225 up ifenslave bond0 eth0 up ifenslave bond0 eth1 post-down ifconfig eth1 down post-down ifconfig eth0 down I really don't know what bond0 is so I may be missing something. bond0 is Bonding. If eth0 is down eth1 takes over... Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
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 loLink 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 RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 eth1 0.0.0.0 81.7.167.2250.0.0.0 UG 00 eth0 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? Which transmit policy are you using ? Round robin XOR Active-backup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: Which transmit policy are you using ? Round robin XOR Active-backup I have no idea. How can I find out? # cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a #, and everything on the line after them are ignored. usb-ohci input usbkbd keybdev tg3 bonding miimon=250 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
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 loLink 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 RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 eth1 0.0.0.0 81.7.167.2250.0.0.0 UG 00 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.00.0.0.0 255.255.0.0 U 40 0 0 eth0 10.0.0.00.0.0.0 255.255.0.0 U 40 0 0 eth1 10.0.0.00.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]
Re: Unable to ping gateway
Depends on the value that you pass at mode parameter: mode=1 Active-backup policy, configuration not needed mode=0, mode=2, mode=3 it does need to be configured for Round robin, XOR and boradcast policies. On Mon, 20 Sep 2004 19:10:14 +0200, Jacob Larsen wrote: Sergio Basurto wrote: Which transmit policy are you using ? Round robin XOR Active-backup I have no idea. How can I find out? # cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a #, and everything on the line after them are ignored. usb-ohci input usbkbd keybdev tg3 bonding miimon=250 Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: 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.00.0.0.0 255.255.0.0 U 40 0 0 eth0 10.0.0.00.0.0.0 255.255.0.0 U 40 0 0 eth1 10.0.0.00.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 - So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: Depends on the value that you pass at mode parameter: mode=1 Active-backup policy, configuration not needed mode=0, mode=2, mode=3 it does need to be configured for Round robin, XOR and boradcast policies. Do you know which one is the default? I remember when I set bonding miimon=250 mode=1 in /etc/modules I couldn't make it work. Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
On Mon, 20 Sep 2004 19:38:20 +0200, Jacob Larsen wrote: Sergio Basurto wrote: 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.00.0.0.0 255.255.0.0 U 40 0 0 eth0 10.0.0.00.0.0.0 255.255.0.0 U 40 0 0 eth1 10.0.0.00.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 - So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Thanks, Jacob Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. If this do not help you can consult a good doc at: http://ece.wpi.edu/pit/rowitsch/linux-2.4.21/Documentation/networking/bonding.txt Kind Regards Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
On Mon, 20 Sep 2004 19:42:13 +0200, Jacob Larsen wrote: Sergio Basurto wrote: Depends on the value that you pass at mode parameter: mode=1 Active-backup policy, configuration not needed mode=0, mode=2, mode=3 it does need to be configured for Round robin, XOR and boradcast policies. Do you know which one is the default? I remember when I set bonding miimon=250 mode=1 in /etc/modules I couldn't make it work. Thanks, Jacob I'm not quite sure but I think is 1. Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. I am not sure that I understand what you mean by supersede. The only gateway I have is 81.7.167.225. Do you mean that I can have a gateway for eth0 and eth1 if it is different than that of bond0? By not setting a gateway for eth0 and eth1 in /etc/network/interfaces it still doesn't work. What should I do? Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Ok, send the shell~#route -n output... On Mon, 20 Sep 2004 22:21:58 +0200, Jacob Larsen wrote: So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. I am not sure that I understand what you mean by supersede. The only gateway I have is 81.7.167.225. Do you mean that I can have a gateway for eth0 and eth1 if it is different than that of bond0? By not setting a gateway for eth0 and eth1 in /etc/network/interfaces it still doesn't work. What should I do? Thanks, Jacob Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: Ok, send the shell~#route -n output... # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG0 00 bond0 On Mon, 20 Sep 2004 22:21:58 +0200, Jacob Larsen wrote: So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. I am not sure that I understand what you mean by supersede. The only gateway I have is 81.7.167.225. Do you mean that I can have a gateway for eth0 and eth1 if it is different than that of bond0? By not setting a gateway for eth0 and eth1 in /etc/network/interfaces it still doesn't work. What should I do? Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
move from your routing table, the entries for your eth's cards. route del ... On Mon, 20 Sep 2004 23:15:45 +0200, Jacob Larsen wrote: Sergio Basurto wrote: Ok, send the shell~#route -n output... # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 bond0 On Mon, 20 Sep 2004 22:21:58 +0200, Jacob Larsen wrote: So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. I am not sure that I understand what you mean by supersede. The only gateway I have is 81.7.167.225. Do you mean that I can have a gateway for eth0 and eth1 if it is different than that of bond0? By not setting a gateway for eth0 and eth1 in /etc/network/interfaces it still doesn't work. What should I do? Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: move from your routing table, the entries for your eth's cards. route del ... I am not sure I know what to do. If I do something wrong I have to drive 60km to fix it :) # route del ? Please help. Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
ok, #route del -net 87.7.167.224 netmask 255.255.255.240 eth0 #route del -net 87.7.167.224 netmask 255.255.255.240 eth1 then run #route -n and the output should not have the eth's entries. #ip neigh show and send the output On Mon, 20 Sep 2004 14:19:03 -0700 (PDT), Sergio Basurto wrote: move from your routing table, the entries for your eth's cards. route del ... On Mon, 20 Sep 2004 23:15:45 +0200, Jacob Larsen wrote: Sergio Basurto wrote: Ok, send the shell~#route -n output... # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 bond0 On Mon, 20 Sep 2004 22:21:58 +0200, Jacob Larsen wrote: So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0? Yes, But you also could have gw for your eth's cards, but you must assure that those routes do not supercede the bond0. I am not sure that I understand what you mean by supersede. The only gateway I have is 81.7.167.225. Do you mean that I can have a gateway for eth0 and eth1 if it is different than that of bond0? By not setting a gateway for eth0 and eth1 in /etc/network/interfaces it still doesn't work. What should I do? Thanks, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Ing. Sergio Basurto Juárez Tel: 04455-85322945
Re: Unable to ping gateway
This is what I got. Which package do I need for ip neigh show? # route del -net 87.7.167.224 netmask 255.255.255.240 eth0 SIOCDELRT: No such process # route del -net 87.7.167.224 netmask 255.255.255.240 eth1 SIOCDELRT: No such process # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 0 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG0 00 bond0 Sergio Basurto wrote: ok, #route del -net 87.7.167.224 netmask 255.255.255.240 eth0 #route del -net 87.7.167.224 netmask 255.255.255.240 eth1 then run #route -n and the output should not have the eth's entries. #ip neigh show and send the output -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
iproute2 under debian : #apt-get install iproute and try #route del -host 87.7.167.224 eth0 #route del -host 87.7.167.224 eth1 On Tue, 21 Sep 2004 00:02:29 +0200, Jacob Larsen wrote: This is what I got. Which package do I need for ip neigh show? # route del -net 87.7.167.224 netmask 255.255.255.240 eth0 SIOCDELRT: No such process # route del -net 87.7.167.224 netmask 255.255.255.240 eth1 SIOCDELRT: No such process # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth0 81.7.167.2240.0.0.0 255.255.255.240 U 00 eth1 81.7.167.2240.0.0.0 255.255.255.240 U 00 bond0 0.0.0.0 81.7.167.2250.0.0.0 UG 00 bond0 Sergio Basurto wrote: ok, #route del -net 87.7.167.224 netmask 255.255.255.240 eth0 #route del -net 87.7.167.224 netmask 255.255.255.240 eth1 then run #route -n and the output should not have the eth's entries. #ip neigh show and send the output Ing. Sergio Basurto Juárez Tel: 04455-85322945 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unable to ping gateway
Sergio Basurto wrote: #route del -host 87.7.167.224 eth0 #route del -host 87.7.167.224 eth1 # route del -host 87.7.167.224 eth0 SIOCDELRT: No such process # route del -host 87.7.167.224 eth1 SIOCDELRT: No such process # ip neigh show 81.7.167.225 dev bond0 lladdr 00:d0:00:e4:fc:0a nud reachable I wish I could be more helpfull. Thanks for your help so far! Best regards, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
