On 5/27/06, Mark <[EMAIL PROTECTED]> wrote:
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.1
11.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.1
12.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200
cache mtu 1500 advmss 1460 hoplimit 64
office:~# ip route get to 13.1.1.1
13.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 14.1.1.1
14.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200
cache mtu 1500 advmss 1460 hoplimit 64
office:~# 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 64
office:~#
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..
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.
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.1
11.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.1
12.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200
cache mtu 1500 advmss 1460 hoplimit 64
office:~# ip route get to 13.1.1.1
13.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 14.1.1.1
14.1.1.1 via 192.168.0.1 dev eth2 src 192.168.1.200
cache mtu 1500 advmss 1460 hoplimit 64
office:~# 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 64
office:~#
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..
