See - Its good to be intellectually limited like me.  I know exactly 2 tricks that usually works. 1.  Reinstall and reboot several times 2.  Reboot some more.

OK - what does your configuration look like?

No there isn't anything like that.

@doktornotor: You need to leave the box checked ONCE to get the URL saved. After that, does not matter. OK, that explains what's happening; thanks! That little bit of user interaction probably should be made a little more clear…

That is the symptoms - apinger is detecting both latency (delay) and packet loss in excess of the values specified in the WAN_DHCP gateway parameters. Why you are getting that loss is another question. Try something like "ping 8.8.8.8" for a while from a LAN client and see if it is losing packets, then ping your local pfSense gateway IP… and see where the packets disappear/get lots of latency. Or maybe a big download was saturating your link at the time.

@horace: I still don't understand how can i convert the key in order to use it with putty. Did i something wrong? You can use pkcs8 or rsa tools shipped with openssl to convert between those two: http://linux.die.net/man/1/pkcs8 http://linux.die.net/man/1/rsa

Thanks guys for your help, its working :)… I hope I did it right!.. Like kejianshi said, I added my subnet to the custom list in the Windows XP firewall and it worked :) Just to be clear about what I did and for anybody else who may not know how, here's how. In windows XP firewall settings under exceptions select "File and Print Sharing" and choose edit. Now add your subnet to the custom list. (don't forget to include the original subnet) Thanks again guys :)

As a quick note: I don't remember HP1810Gs supporting etherchannel or loadbalancing over ports on different switches (even Ciscos or Juniper switches have it only in high(er) price models). So I'd go with casper's recommendation: throw away VLAN configurations on NIC1/2 create LAGG interface with failover type (a Bond1 configuration) create all 6 VLANs on the lagg0 interface configure the port on both switches for those 6 VLANs don't forget to allow them through your LACP trunk, too ;) (coworker forgot that, after failover only the ports on the active switch were working) That should do it.

BTW, I tested the "Use IPv4 connectivity as parent interface" option. I was able to retain IPv6 connectivity. The only issue I had with it is that enabling it seemed to require a reboot. Aside from that, so far so good! Thanks a lot for this fix.  :) :) :)

Thank you. I feel like an idiot!

If a critical service process (dhcp, dns, OpenVPNs…) exits abnormally (system problem like out of swap space, program problem like divide by zero) there is no controlling script that called it that then gets the error code, and can loop around to try and run the program again. These services are forked off into independent processes by the bootup scripts. There is nothing else built into the system that monitors AND restarts them automatically. Yes, there are dashboard displays, but they don't take automatic action. And in any case, what if nobody has a dashboard running. So JimP has kindly made Service Watchdog - in a perfect world it would not be needed, just like a real watchdog. OpenVPN: in my experience the OpenVPN code is very good at trying forever to connect and eventually connecting once the underlying physical links and internet is up and working. I expect that an OpenVPN client would only stop trying to establish a connection if the process has actually crashed, which I have only seen happen because of "killed: out of swap space".

@heavy1metal: I'd go with Kejianshi's idea. Though for social media sites, I'd block every purchased IP range they own, thus blocking both site and chatting features… Google's DNS names for messaging services: https://support.google.com/chat/answer/161980?hl=en restrict access to use only your DNS servers: https://doc.pfsense.org/index.php/Blocking_DNS_queries_to_external_resolvers Regarding the link to the "blocking DNS" entry on the wiki: This: http://www.interspective.net/2012/07/pfsense-ntp-and-network-sneakery.html Can be applied to DNS too. I enable this "feature" sometimes for my girlfriend for facebook when she has to study. The rule to block facbook would look something like this: address=/facebook.com/62.112.159.61 The relevant page in the wiki for this is: https://doc.pfsense.org/index.php/Wildcard_Records_in_DNS_Forwarder

Might also want to reference my original thread http://forum.pfsense.org/index.php/topic,66234.0.html since the backed out patch looks remarkably like the one that was proposed there and where I raised my concerns as to whether comparing the interface address against $vipent['subnet'] will work (I think it won't). If possible, the two threads should probably be merged.

Yes but like I say if you have the same ISP you may end up with the same gateway on each WAN which confuses the gateway monitoring daemon. If you have PPPoE on each WAN you can just change the address being monitored to some other remote IP. If your WANs are dhcp you'll need to take other steps. One possible solution in that case is to leave the modems as routers so that pfSense sees the modem as its gatway. May not be an issue for you. Steve

I know this method based on the gui. I want to do the same from the shell :     1. Restore config.xml.     2. Install automatically packages requiered. Thanks, Yannick