[pfSense] ipsec tunnel closes

2011-12-19 Thread Nick Upson
I'm running 1.2.3 I have an IPsec tunnel to another site, which closes unless there is traffic I want it up 24/7 so I put a remote IP in the keep alive, automatically ping host section of the setup. It still behaves the same way. Is this to be expected (known bug or something) or have I done

Re: [pfSense] ipsec tunnel closes

2011-12-19 Thread Chris Buechler
On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote: I'm running 1.2.3 I have an IPsec tunnel to another site, which closes unless there is traffic I want it up 24/7 so I put a remote IP in the keep alive, automatically ping host section of the setup. It still behaves the same

Re: [pfSense] ipsec tunnel closes

2011-12-19 Thread Nick Upson
Nick Upson On 19 December 2011 14:55, Jochem de Waal joc...@caresoft.nl wrote: ** ** ** ** I'm running 1.2.3 I have an IPsec tunnel to another site, which closes unless there is traffic I want it up 24/7 so I put a remote IP in the keep alive, automatically ping host section of the

Re: [pfSense] ipsec tunnel closes

2011-12-19 Thread Ian Bowers
On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote: I'm running 1.2.3 I have an IPsec tunnel to another site, which closes unless there is traffic I want it up 24/7 so I put a remote IP in the keep alive, automatically ping host section of the setup. It still behaves the

Re: [pfSense] ipsec tunnel closes

2011-12-19 Thread Nick Upson
Nick Upson On 19 December 2011 15:00, Ian Bowers iggd...@gmail.com wrote: On Mon, Dec 19, 2011 at 9:49 AM, Nick Upson n...@telensa.com wrote: I'm running 1.2.3 I have an IPsec tunnel to another site, which closes unless there is traffic I want it up 24/7 so I put a remote IP in the

Re: [pfSense] ipsec tunnel closes

2011-12-19 Thread Ian Bowers
one thing to check is what IP that ping ends up getting sourced from, and making sure it's in the right subnet. tcpdump should work I'm thinking one reason it can get closed is if IP/50, UDP/500, and/or UDP/4500 arent allowed in both directions on the other end. when requesting VPN ports from

[pfSense] bug reports closed on this but I still see it on current version: ipfw-classifyd: unable to write to divert socket: No buffer space available

2011-12-19 Thread Greg Whynott
Hello, re: ipfw-classifyd: unable to write to divert socket: No buffer space available I'm seeing thousands of these errors in the logs every day, when i did a search (using google and the bugtracker at pfsence.org) I found several folks having the same issues going back a year or so. 2

Re: [pfSense] WAN DHCP change of default GW ...

2011-12-19 Thread Jeppe Øland
are you using Canal Digital as ISP by any chance? No this was on a local San Francisco ISP. It's not something they do on a regular basis, so chances are I will never see the problem again - but I would like to understand what happened! Regards, -Jeppe

Re: [pfSense] Installing on Dell R310 / Perc H200

2011-12-19 Thread greg whynott
Hello, I got around a similar issue by making some changes in the bios. try these: set the Processor to use only 1 core, C state disable,turn off all power saving options (max performance), disable PXE, and USB back ports only. After I did this I was able to install on both a R310 and a

Re: [pfSense] particular site not working

2011-12-19 Thread RCD
It's not squid, I don't have it installed. Look at this: http://www.downforeveryoneorjustme.com/bsnl.co.in Seems the site is simply down. Ryan On 12/16/2011 10:19 PM, Guruprasad R wrote: Hi my setup: i have pfsense 2.0 amd64 bit installed in amd 64 based system. i have configured squid