Tom Eastep a écrit :
zorgman wrote:
Hi
I'm trying to monitor my multi ISP shorewall with swping, the script
works fine, i can see in log when an ISP is down, the script restart
shorewall and /etc/shorewall/isusable is called, however in the swping
log after the shorewall restart i see again
Tom Eastep teastep at shorewall.net writes:
Outgoing packets from that connection are being routed out of ppp0 by
your routing rules. Because those packets are not in the NEW connection
state, they do not pass through the ppp0_masq chain so their source IP
will be 6.1.3.4.
Ahhh. Thanx for
Shorewall warn me :
ERROR: Interface eth2.303 is not usable -- Provider freenew (1024)
Cannot be Added
Terminated
I guess you don't have interface option optional for eth2.303. You must
have interface option optional for every interface swping might return
failed.
--
Tuomo Soini
Brian J. Murrell wrote:
tcrules is what I likely want in the end anyway given that I will probably try
to utilize ipp2p to force the routing of bittorrent packets.
That won't work.
-Tom
--
Tom Eastep\ When I die, I want to go like my Grandfather who
Shoreline, \ died
Hello, thanks very much for your help.I answer each of your questions or
coments down:
I've an openvpn server running on the firewall and working on eth1 and
I´d like to config my firewall to let a pptp client, running on my LAN
(with IP 10.10.80.10), connect to a pptp remote vpn server of a
On Tue, 16 Feb 2010 22:52:45 -0800, Tom Eastep teas...@shorewall.net
wrote:
Nigel Aves wrote:
Thanks Tom, no hurry .
I've been able to reproduce the problem here.
-Tom
Sounds like we found a bug.
Thanks for your very prompt action on this - Nigel.
--
From the desk of Nigel
Tom Eastep wrote:
Nigel Aves wrote:
Thanks Tom, no hurry .
I've been able to reproduce the problem here.
Here's a patch:
patch /usr/share/shorewall/Shorewall/Tc.pm sfqclassnum.diff
Please let me know if it works for you.
-Tom
--
Tom Eastep\ When I die, I want to go like my
Miguel A. Velasco wrote:
Hello, thanks very much for your help.I answer each of your questions or
coments down:
Given that your external IP addresses are in the RFC 1918 range, you are
doing double NAT of all of your traffic. Do you know for certain that
this works in a single-ISP
Tom,
Patch worked perfectly ... Thank you.
Nigel.
-Original Message-
From: Tom Eastep [mailto:teas...@shorewall.net]
Sent: Wednesday, February 17, 2010 07:37
To: Shorewall Users
Subject: Re: [Shorewall-users] Adding download control for internal
interface - qdisk errors out
Tom Eastep
Tom:
On 2/16/2010 9:27 PM, Tom Eastep wrote:
I've done some experiments and unfortunately, setting
--hashlimit-htable-expire to 1 hour does not change anything; the
hashtable entries still expire in 10 seconds :-(
Are you seeing the save behavior as me? Or is it working fine for you?
I'd
Brian Schang wrote:
Tom:
On 2/16/2010 9:27 PM, Tom Eastep wrote:
I've done some experiments and unfortunately, setting
--hashlimit-htable-expire to 1 hour does not change anything; the
hashtable entries still expire in 10 seconds :-(
Are you seeing the save behavior as me? Or is it
Tom Eastep wrote:
Brian Schang wrote:
Tom:
On 2/16/2010 9:27 PM, Tom Eastep wrote:
I've done some experiments and unfortunately, setting
--hashlimit-htable-expire to 1 hour does not change anything; the
hashtable entries still expire in 10 seconds :-(
Are you seeing the save behavior as
Tom:
On 2/17/2010 9:27 PM, Tom Eastep wrote:
I've done some experiments and unfortunately, setting
--hashlimit-htable-expire to 1 hour does not change anything; the
hashtable entries still expire in 10 seconds :-(
Are you seeing the save behavior as me? Or is it working fine for you?
I'd
13 matches
Mail list logo
