Re: [Shorewall-users] masq file: interface or ip address in source field?

On Thu, Oct 1, 2009 at 8:41 PM, Jerry Vonau wrote: > On Thu, 2009-10-01 at 09:19 +0530, Rags wrote: > > On Wed, Sep 30, 2009 at 11:02 PM, Jerry Vonau wrote: > > On Wed, 2009-09-30 at 10:38 +0530, Rags wrote: > > > Hello, > > > > > > I'm using Shorewall perl 4.4.1.

Re: [Shorewall-users] masq file: interface or ip address in source field?

Rags wrote: > On Thu, Oct 1, 2009 at 8:41 PM, Jerry Vonau > wrote: > > 192.168.32.0 is your local lan right? Did you really intend to masq just > 192.168.32.1 or is that meant for the entire local lan connected to > eth0? If it's the entire lan you want, think y

[Shorewall-users] 4.4.2: check yields internal error from routestopped

After upgrading to 4.4.2, "shorewall check" yields this error if my routestopped file includes the "routeback" option: ERROR: Internal error in Shorewall::Config::emit at /usr/share/shorewall/Shorewall/Config.pm line 823 : /etc/shorewall/routestopped (line 2) "shorewall restart" works fine,

Re: [Shorewall-users] 4.4.2: check yields internal error from routestopped

David Rothenberger wrote: > After upgrading to 4.4.2, "shorewall check" yields this error if my > routestopped file includes the "routeback" option: > > ERROR: Internal error in Shorewall::Config::emit at > /usr/share/shorewall/Shorewall/Config.pm line 823 : > /etc/shorewall/routestopped (li

Re: [Shorewall-users] 4.4.2: check yields internal error from routestopped

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Eastep wrote: > David Rothenberger wrote: >> After upgrading to 4.4.2, "shorewall check" yields this error if my >> routestopped file includes the "routeback" option: >> >> ERROR: Internal error in Shorewall::Config::emit at >> /usr/share/shor

Re: [Shorewall-users] 4.4.2: check yields internal error from routestopped

Tom Eastep wrote: > Tom Eastep wrote: >> David Rothenberger wrote: >>> After upgrading to 4.4.2, "shorewall check" yields this error if my >>> routestopped file includes the "routeback" option: >>> >>> ERROR: Internal error in Shorewall::Config::emit at >>> /usr/share/shorewall/Shorewall/Confi

[Shorewall-users] multi-isp, multi-lan.

okay, so here's what I've been called upon to do: I have two ISPs and two separate LANs (we have a two-family household) lets call them lan1 and lan2, and isp1 and isp2. I've been asked if I could configure a router such that.. all traffic from lan1 is sent through isp1 by default, and all traffi

Re: [Shorewall-users] multi-isp, multi-lan.

Some more details would be great and it would be helpful to know wether you start from scratch or if you started to setup by your own and now stuck at a specific point. Anyway, policy based routing is what you are looking for. You are interested in having two tables, one with a default route to

Re: [Shorewall-users] multi-isp, multi-lan.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christ Schlacta wrote: > okay, so here's what I've been called upon to do: > I have two ISPs and two separate LANs (we have a two-family household) > > lets call them lan1 and lan2, and isp1 and isp2. > > I've been asked if I could configure a router