/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
It can be done. I too have DSL and Cable. Cable being much faster than
DSL is
the default route. But DSL supports serving information so it is the
default
route back for traffic, because you need all traffic that came in for
Cable
going back out Cable and in for DSL back out on DSL. Too many providers
will
drop packets with source addresses not in the right range for security
reasons.
Here is how I set my stuff up, it may not be ideal but IT WORKS!!
I have many extra routing tables that set defaults for different
situations
eth0 - Cable (with multiple IPs, non routable)
eth1 - DSL (with multiple routable IPs, call them DSLNetIPs)
eth2 - Internal machines 192.168.124.1 and .2 and .3
eth3 - External servers 192.168.125.1 and 2 CableIPs (not main) and 2
DSLNetIPs
2 - default route via Cable src CableIP
3 - default route via DSL src DSLIP
5 - default route via eth2 src 192.168.124.1
6 - default route via eth3 src 192.168.125.1
7 - default route via eth3 src CableIP
8 - default route vai eth3 src DSLNetIP
I then added some rules based on the 'to' address being 192.168.124.* or
192.168.125.* to route using the table 5 or 6
I then added rules based on the 'to' address being any one of my Cable
address
to use table 7, and likewise for my DSLNetIPs to route via table 8
This then has all inbound traffic going to the right cards with correct
routing
Then I added appropriate From rules that route back out the appropriate
eth0/eth1 interface depending on the source address.
WORKS LIKE A CHARM! No load balancing or anything, but in a flash I can
reassign my basic default route to either cable or DSL, and relatively
quickly
move over if one of the lines should fail. Nothing automatic yet, but I
am
working on it!
"M . Jackson Wilkinson" wrote:
> /* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
> /* ALSO: Don't quote this header. It makes you look lame :-) */
>
> Okay, I hope this isn't noise, since I did search through the archives...
> anyway...
>
> I have had DSL masq'ed for a while now, but decided to get cable in addition
> for my home network. However, I need to keep the DSL on the server, since
> they allow servers explicitly.
>
> so, right down to it, I need my internal network (10.5.1.0/24 on eth0) to be
> routed through cable (eth2) and the masq box's default route to be through
> DSL (eth1). This is using iptables on 2.4.0, by the way.
>
> I've tried setting eth1 as the default route and using:
>
> iptables -t nat -A POSTROUTING -o eth2 -j MASQUERADE
>
> for masq'ing, but the masq simply won't work.
>
> Any help is much appreciated,
> Jack Wilkinson
>
> _______________________________________________
> Masq maillist - [EMAIL PROTECTED]
> Admin requests can be handled at http://www.indyramp.com/masq-list/ --
> THIS INCLUDES UNSUBSCRIBING!
> or email to [EMAIL PROTECTED]
>
> PLEASE read the HOWTO and search the archives before posting.
> You can start your search at http://www.indyramp.com/masq/
> Please keep general linux/unix/pc/internet questions off the list.
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ --
THIS INCLUDES UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
