Have you each ADSL line connected to a NIC ethernet ?
You have 6 NIC ethernets ?
bests
andres
-----Mensaje original-----
De: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]En
nombre de Mark Coetser
Enviado el: Sábado, 03 de Julio de 2004 08:33 a.m.
Para: LARTC@mailman.ds9a.nl
Asunto: [LARTC] load balanced adsl lines
Hi Ppl
I have 5 adsl lines that after reading quite a bit i managed to get load
balanced now abvoiusly it doesnt load balance evenly and this works on what
routes are still in the routing cache. my question is my outbound
masquerading had to be modified to use snat in iptables instead of just
plain masquerading my outbound masquerading now works but my inbound port
forwarding doesnt work would this be an iptables problem or a routing
issue...
i have opened all the relavent ports on each of the interfaces and I am not
getting any logged denies the connection just never opens
I am running the following
debian woody
kernel 2.6.6
ip rule list
0: from all lookup local
32761: from 165.165.170.110 lookup T5
32762: from 165.165.187.47 lookup T4
32763: from 165.165.189.95 lookup T3
32764: from 165.165.163.95 lookup T2
32765: from 165.165.179.151 lookup T1
32766: from all lookup main
32767: from all lookup default
ip route sh
165.165.160.1 dev ppp1 proto kernel scope link src 165.165.163.95
165.165.160.1 dev ppp3 proto kernel scope link src 165.165.187.47
165.165.160.1 dev ppp4 proto kernel scope link src 165.165.170.110
165.165.160.1 dev ppp0 proto kernel scope link src 165.165.179.151
165.165.160.1 dev ppp2 proto kernel scope link src 165.165.189.95
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1
default
nexthop via 165.165.160.1 dev ppp0 weight 1
nexthop via 165.165.160.1 dev ppp1 weight 1
nexthop via 165.165.160.1 dev ppp2 weight 1
nexthop via 165.165.160.1 dev ppp3 weight 1
nexthop via 165.165.160.1 dev ppp4 weight 1
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/