On 7/21/10 4:11 PM, Stephen Brown wrote: > 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
Yep. > > 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) Not in the least. In fact, I did something similar while I was getting Comcast Business Class set up. Wife was only moderately happy, however, since we run our own mail server which was behind the Shorewall box :-) -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
