-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok so far so good... but I do need some clarification on a few things.
First, to summate, here are my goals: - - send and receive all traffic with the exception of SIP and IAX based traffic for VoIP over the cable link. - - have the cable modem act as a backup in the event the DSL link fails, this will include my normal web and mail server traffic. I understand the tcrules setup (I think) in regards to what I am trying to accomplish for outbound VoIP traffic. Inbound traffic will be directed to the cable link as well, I'm going to create SRV records to provide redundancy, will shorewall still process my DNAT rules regardless of which ISP they arrive from? For example, let's say my cable modem goes down, and I have an SRV record of a higher weight to point to my DSL connection, I should expect to still be able to receive inbound calls without hassle? What about outbound calls in this scenario? What would be the best way to deal with that? Here are my config files thus far, I don't know that many of the options are sane however (pastebin'ed because they kept wrapping in my email client): http://www.pastie.org/1050858 Some of my configs may undoubtedly be wrong or not optimized, so any help appreciated :) Thanks, Stephen On 7/19/10 11: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. > > -Tom > > > > ------------------------------------------------------------------------------ > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkxEpQwACgkQ3sJXNEncx7jJmACgqNYktE7Jgqfv5LQc2w7ttnfc e04AoLrYAFnbKqaCUS9M+w7Kn5lHJwLJ =QQGr -----END PGP 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
