On 7/19/10 8:36 AM, Tom Eastep wrote: > On 7/19/10 8:25 AM, Stephen Brown wrote: >> I recently ordered a residential class cable connection from Comcast to >> complement my static DSL connection for redundancy. >> >> My eventual goal is to run all of my VoIP traffic (SIP and IAX) over the >> cable connection and to also use it as a backup to my other services >> (mail, web, openvpn, etc) if the DSL fails for any reason, but I've got >> to get the cable connection working with linux first then I can deal >> with the shorewall config. >> >> I've read the Shorewall documentation on Multi ISP's but I am having one >> hurdle that I can't seem to get past, and I'm hopeful someone has the >> answer as I'm sure it's simple. >> >> Everything works as expected until I plug the cable modem into eth2. It >> creates another default route and kills everything, and I'm not sure how >> to deal with that or prevent it from happening? >> > > Please look at the 'Complete Example' at the bottom of the Multi ISP > article at shorewall.net. It has almost exactly the configuration you > are trying to set up.
Also, you must get the Shorewall configuration created and installed *first*; once the configuration is working with the cable interface disconnected, then, you can plug in the cable modem and it will work. You can't do it the other way around. -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
