Re: Debian Etch with 2 Internet Connections Load Balanced
On 5/27/06, Mark <[EMAIL PROTECTED]> wrote: On Sat, May 27, 2006 at 09:13:43AM -0400, Roberto C. Sanchez wrote:> Prepaid wrote:> > Hi> >> > So I'm trying to configure a Debian Etch box that is connected to 2> > internet connections (WAN) both have static IP configurations and work > > fine if a default route points to only 1 of them and 1 LAN connection.> >>> You may also want to consider shorewall, which can specifically deal> with multi-ISP setups and load balancing between them. >I've not seen that - might be interesting.Presently I'm load balancing between two ISPs using sarge and ip tools.The method is described here in light form, with a url for the realdetails... http://www.linuxquestions.org/linux/answers/Networking/Spanning_Multiple_DSLsYou don't need to have physically separate interfaces, as the lartc document indicates, but I've found that you /do/ need to have multipleaddresses for the same interface if you do not.I could look into shorewall, but I'm baffeled as to why my configuration isn't working. I dropped my eth1/eth2 and all ip route stuff, and went exactly with the configuration from the website mentioned above (but changed eth0=eth1), but I still get miss matched IP routes.office:~# ip route get to 11.1.1.111.1.1.1 via 192.168.0.1 dev eth2 src 192.168.0.200 cache mtu 1500 advmss 1460 hoplimit 64 office:~# ip route get to 12.1.1.112.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200 cache mtu 1500 advmss 1460 hoplimit 64office:~# ip route get to 13.1.1.113.1.1.1 via 192.168.0.1 dev eth2 src 192.168.0.200 cache mtu 1500 advmss 1460 hoplimit 64office:~# ip route get to 14.1.1.114.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200 cache mtu 1500 advmss 1460 hoplimit 64office:~# ip route get to 15.1.1.1 15.1.1.1 via 192.168.0.1 dev eth2 src 192.168.0.200 cache mtu 1500 advmss 1460 hoplimit 64office:~# First of all it seems to never want want to route via eth1, and we see a mismatch where eth1 source ip is trying to go out via eth2, and this is the exact same behavior my configuration is having. Totally stumped..
Re: Debian Etch with 2 Internet Connections Load Balanced
On Sat, May 27, 2006 at 09:13:43AM -0400, Roberto C. Sanchez wrote: > Prepaid wrote: > > Hi > > > > So I'm trying to configure a Debian Etch box that is connected to 2 > > internet connections (WAN) both have static IP configurations and work > > fine if a default route points to only 1 of them and 1 LAN connection. > > > > You may also want to consider shorewall, which can specifically deal > with multi-ISP setups and load balancing between them. > I've not seen that - might be interesting. Presently I'm load balancing between two ISPs using sarge and ip tools. The method is described here in light form, with a url for the real details... http://www.linuxquestions.org/linux/answers/Networking/Spanning_Multiple_DSLs You don't need to have physically separate interfaces, as the lartc document indicates, but I've found that you /do/ need to have multiple addresses for the same interface if you do not. -- Mark Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Etch with 2 Internet Connections Load Balanced
Prepaid wrote: > Hi > > So I'm trying to configure a Debian Etch box that is connected to 2 > internet connections (WAN) both have static IP configurations and work > fine if a default route points to only 1 of them and 1 LAN connection. > You may also want to consider shorewall, which can specifically deal with multi-ISP setups and load balancing between them. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Debian Etch with 2 Internet Connections Load Balanced
HiSo I'm trying to configure a Debian Etch box that is connected to 2 internet connections (WAN) both have static IP configurations and work fine if a default route points to only 1 of them and 1 LAN connection. I've followed the directions at: http://lartc.org/howto/lartc.rpdb.multiple-links.html many times and am at a loss. My first step is just to quasi load balance the outgoing connections from the debian box onto the 2 WAN connections eth1+eth2. I can get my routing to work via only 1 WAN connection, but if I try to get both to work through:ip route add default scope global nexthop via 10.10.30.1 dev eth1 weight 1 nexthop via 10.10.90.1 dev eth2 weight 1I can't get any internet connectivity (would just get destination host unreachable through PING but it would alternate between for different connections so it seems like it's trying to do some kind of load balancing). From 10.10.90.251 icmp_seq=2 Destination Host Unreachable (on an attempt to 1 host)From 10.10.30.250 icmp_seq=2 Destination Host Unreachable (on an attempt to a different host) eth0: my IP: 10.10.11.1 netmask: 255.255.255.0 (LAN)eth1: my iP: 10.10.30.250 gateway 10.10.30.1 netmask: 255.255.255.0 (WAN1 / DSL)eth2: my IP: 10.10.90.251 gateway 10.10.90.1 netmask: 255.255.255.0 (WAN2 / cable)Here's my settings from /etc/network/interfaces:auto eth1iface eth1 inet static address 10.10.30.250 netmask 255.255.255.0 network 10.10.30.0 broadcast 10.10.30.255 post-up ip route add 10.10.30.0/24 dev eth1 src 10.10.30.250 table dsl post-up ip route add default via 10.10.30.1 table dsl post-up ip rule add from 10.10.30.250 table dsl post-down ip rule del from 10.10.30.250 table dslauto eth2iface eth2 inet static address 10.10.90.251 netmask 255.255.255.0 network 10.10.90.0 broadcast 10.10.90.255 post-up ip route add 10.10.90.0/24 dev eth2 src 10.10.90.251 table cable post-up ip route add default via 10.10.90.1 table cable post-up ip rule add from 10.10.90.251 table cable post-down ip rule del from 10.10.90.251 table cable #ip route show 10.10.30.0/24 dev eth1 proto kernel scope link src 10.10.30.25010.10.11.0/24 dev eth0 proto kernel scope link src 10.10.11.110.10.90.0/24 dev eth2 proto kernel scope link src 10.10.90.251default nexthop via 10.10.30.1 dev eth1 weight 1 nexthop via 10.10.90.1 dev eth2 weight 1# ip rule show0: from all lookup local32764: from 10.10.90.251 lookup cable32765: from 10.10.30.250 lookup dsl32766: from all lookup main32767: from all lookup default/etc/iproute2/rt_tables:## reserved values# 255 local254 main253 default0 unspec## local##1 inr.ruhep201 dsl202 cableAny ideas? Much thanks in advance! I've been beating my head on this for many many hours and I bet it's something stupidly obvious.
