Re: [Shorewall-users] Shorewall 4.4.4.-1 with squid 3.0Stable20-1 as non-transparnt proxy

2009-12-15 Thread Tom Eastep
Asim Ahmed Khan wrote: > hi, > > First i tried to run squid as transparent (interception) proxy that > didn't work. Browsing and other internet usage became too > inconsisten. too many break ups were occuring and all of a sudden > browsing stop and restart after some time ranging from a 30 seco

[Shorewall-users] Shorewall 4.4.4.-1 with squid 3.0Stable20-1 as non-transparnt proxy

2009-12-15 Thread Asim Ahmed Khan
hi, First i tried to run squid as transparent (interception) proxy that didn't work. Browsing and other internet usage became too inconsisten. too many break ups were occuring and all of a sudden browsing stop and restart after some time ranging from a 30 seconds to a few minutes. hitting F5 keys

Re: [Shorewall-users] Multi ISP

2009-12-15 Thread Fernando Rodriguez
Do you have an example of the needed tcrules and yes all 3 links go to the same ISP you can find wanitor in this address .. http://www.aitelecom.net/wanitor/ you can test it and if you think its ok we can link it from the page Fernando Rodriguez f...@aitelecom.net On Dec 15, 2009, at 12

Re: [Shorewall-users] Multi ISP

2009-12-15 Thread Tom Eastep
Fernando Rodriguez wrote: > Kernel 2.6.22.19 This can happen when multiple connections exist to the same server; they can go through different routes. The SAME marking target in /etc/shorewall/tcrules is designed to get around that issue. > > Wanitor is similar to LSM with the exeption that if y

Re: [Shorewall-users] Multi ISP

2009-12-15 Thread Fernando Rodriguez
Kernel 2.6.22.19 Wanitor is similar to LSM with the exeption that if you have multiple isp it will not monitor the gateway only but it will also make a route to the internet to scecified ip tru the interface you are testing because we have noticed that your initial gw might be alive but there i

Re: [Shorewall-users] params file not being parsed correctly

2009-12-15 Thread Tom Eastep
Peter Wrangell wrote: > My apologies, for taking up your time. I'll try again running the > latest version. I was just confused as to why the params file was not > being parsed as a collection of variables. Given enough time I'll > figure it out. Thanks for responding so quickly, and once again sor

Re: [Shorewall-users] Multi ISP

2009-12-15 Thread Tom Eastep
Fernando Rodriguez wrote: > Hello, > > I have a multi ISP setup with 3 providers, but there is something > funny happening with only 1 of the 3 providers i have no issues at > all with 2 or the 3 providers i start having issues regarding > connections they seem to jump from one to the other for ex

[Shorewall-users] Multi ISP

2009-12-15 Thread Fernando Rodriguez
Hello, I have a multi ISP setup with 3 providers, but there is something funny happening with only 1 of the 3 providers i have no issues at all with 2 or the 3 providers i start having issues regarding connections they seem to jump from one to the other for example: with skype i get cutoff duri

Re: [Shorewall-users] Manual Chains Knock.pm DNAT-

2009-12-15 Thread Tildar
Thanks Tom. I'll go over my configuration a few more times. On Mon, Dec 14, 2009 at 5:49 PM, Tom Eastep wrote: > Tildar wrote: >> I am attempting to use the Knock.pm from >> http://www.shorewall.net/ManualChains.html >> >> I am not having much luck making the DNAT- knock work for some reason. >>

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Tom Eastep
Tom Eastep wrote: > Stephen Brown wrote: >> I'm using 4.4.0, so that would make RFC1918_STRICT deprecated? >> >> I'm just a little confused now on the network settings for the port that >> is attached to the DSL modem, it's on eth0. >> >> I currently have this setup in /etc/network/interfaces (I'm

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Tom Eastep
Stephen Brown wrote: > I'm using 4.4.0, so that would make RFC1918_STRICT deprecated? > > I'm just a little confused now on the network settings for the port that > is attached to the DSL modem, it's on eth0. > > I currently have this setup in /etc/network/interfaces (I'm running > Debian 5.0 "Le

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Stephen Brown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm using 4.4.0, so that would make RFC1918_STRICT deprecated? I'm just a little confused now on the network settings for the port that is attached to the DSL modem, it's on eth0. I currently have this setup in /etc/network/interfaces (I'm running De

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Tom Eastep
Stephen Brown wrote: >> I didn't even add a static route. I've a similar setup (Netgear >> DM111P) and the only thing I've had to do is add a rule to allow the >> traffic to that IP address (otherwise it gets blocked by all the >> RFC1918 rules). The modem knows that to reach my public IP it has to

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Simon Hobson
I wrote: >They could probably be narrowed down to : ># RFC1918 >ACCEPT net:192.168.x.1 $FW udp 67-68 >HTTP(ACCEPT)loc net:192.168.x.1 >Telnet(ACCEPT) loc net:192.168.x.1 >Ping(ACCEPT)loc net:192.16

Re: [Shorewall-users] Help with aliased interface/rules

2009-12-15 Thread Simon Hobson
Stephen Brown wrote: > > I didn't even add a static route. I've a similar setup (Netgear >> DM111P) and the only thing I've had to do is add a rule to allow the >> traffic to that IP address (otherwise it gets blocked by all the >> RFC1918 rules). The modem knows that to reach my public IP it