Hi,
I've upgraded to the 1.2.3 version on one end, and have a monowall at my
end... whenever I ping a host over the tunnel, they reply...
But doing anything else (http, rdp, ...) it simply does nothing at all !
(eventually, I got a timeout) - but the tunnel is up, and I can ping.
My rules
look at this http://forum.pfsense.org/index.php/topic,13847.0.html
On Sat, Jan 31, 2009 at 10:37 AM, Michel Servaes mic...@mcmc.be wrote:
Hi,
I've upgraded to the 1.2.3 version on one end, and have a monowall at my
end... whenever I ping a host over the tunnel, they reply...
But doing
G R E A T, many thanks - this works out just like pointed out in this
forum!!!
On Sat, Jan 31, 2009 at 11:22 AM, Ermal Luçi ermal.l...@gmail.com wrote:
look at this http://forum.pfsense.org/index.php/topic,13847.0.html
On Sat, Jan 31, 2009 at 10:37 AM, Michel Servaes mic...@mcmc.be wrote:
are these on a managed switch so you can see if there are any errors,
short frames, overruns etc?
One of the offices has a semi-managed switch, on which, looking at the stats I
can't see anything obviously wrong. The other office just has an el-cheapo 5
port switch.
do you have tcp
Thanks for your thoughts on this one. For me, it ended up being a dotnet
application pool issue on the server set to 60 minutes instead of a specific
time or 24 hours :).
Curtis LaMasters
http://www.curtis-lamasters.com
http://www.builtnetworks.com
On Sat, Jan 31, 2009 at 8:36 AM, Chris
Try using the log-rotate-feature...
So every night your swap.state should be compacted...
Are you on the latest pfsense release and the newest squid package ?
Regards,
Martin
-Ursprüngliche Nachricht-
Von: Wayne Langdon [mailto:wa...@langdon.co.za]
Gesendet: Freitag, 30. Januar 2009
Thanks for your thoughts on this one. For me, it ended up being a dotnet
application pool issue on the server set to 60 minutes instead of a specific
time
or 24 hours :).
Just to confirm, are you saying that 1.2.2 has definitely *not* introduced any
new issues in your environment?
On Sat, Jan 31, 2009 at 3:15 PM, Chris Bagnall li...@minotaur.cc wrote:
Thanks for your thoughts on this one. For me, it ended up being a dotnet
application pool issue on the server set to 60 minutes instead of a specific
time
or 24 hours :).
Just to confirm, are you saying that 1.2.2 has
Confirmed... pfSense 1.2.2 has NOT had an adverse effect on our network.
The problem was found on the Web server and has been 100% verified as the
root cause.
Curtis LaMasters
http://www.curtis-lamasters.com
http://www.builtnetworks.com
On Sat, Jan 31, 2009 at 2:45 PM, Chris Buechler
I have managed (thanks to help on this list) to get my ALIX board running a
full install of pfSense on 8GB CF card, so that I could enable Snort service
(default install with embedded kernel).
I ran into the problem of it downloading the snort rules and it would fail.
After adjusting the time
On Sat, Jan 31, 2009 at 8:31 PM, Chuck Mariotti cmario...@xunity.com wrote:
I have managed (thanks to help on this list) to get my ALIX board running a
full install of pfSense on 8GB CF card, so that I could enable Snort service
(default install with embedded kernel).
I ran into the problem
I should add, that I have rebooted 5 times since then without issue.
From: Chuck Mariotti [mailto:cmario...@xunity.com]
Sent: Saturday, January 31, 2009 8:31 PM
To: support@pfsense.com
Subject: [pfSense Support] Problem when rebooting... Embedded on ALIX
I have managed (thanks to help on this
12 matches
Mail list logo
