Well my requirements have changed. Due to multiple attempts to get
things working and the limitation of not being able to use a dhcp
assigned address as a fallback provider, and not to mention an angry
wife for the internet being up and down (I've GOT to keep her happy at
all costs.... lol), I've come up with the following scenario instead:
- keep the DSL on eth0 as it is now
- assign eth2 to the NAT'ed side of a wireless router so that way there
when I'm playing my wife will still have access to the internet without
remorse (via wireless)
- my theory is that I will be able to then use eth2 as a fallback in the
event the DSL fails for any reason, as well as assign particular traffic
to route over this link
So with that being said, does Shorewall care if the fallback interface
is a non-routable address (such as 192.x.x.x, 172.x.x.x, 10.x.x.x)? My
first guess would be no, because it's simply just going to route it to
the gateway you provide (which will be that of the wireless router in
this scenario)
I'm still poking and my limited knowledge of ip routing in this type of
scenario makes things a lot more challenging, but I don't give up easily :)
What are your kernel and iproute versions?
kernel: Linux bubastis 2.6.26-2-686 #1 SMP Mon Jun 21 05:58:44 UTC 2010
i686 GNU/Linux
iproute: ip utility, iproute2-ss080725
This is running on an updated stock Debian Lenny box.
Thanks,
Stephen
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
