Cool, thanks for the info.  If we decide to write up a script to save the logs, I'll certainly share it, although I have a feeling we'll probably resort to sending logs to a syslog server.

Not sure these nics even support it. Checking cables and switch might be a good idea as well.

Look again.  This was asked and answered in the last 24 hours.

Yeah most places are going to allow IPsec out, but you can run OpenVPN on any port you wish. By default it's 1194. It's UDP though, so running it on like port 80 may not be helpful if the network only allows TCP 80. But you can run it on UDP 500 if you want, then it should definitely work on any network that allows IPsec.

Just configure services>DynDNS. it will check for an IP change un reconnection and update the account if there has been a change (given that the pfSense WAN is your real WAN and not natted behind another router).

Entering a gateway at an interface will add NAT to it by default (unless you enable advanced outbound nat). Don't set a gateway at any of your LANs for the pfSense interface config. You only need firewallrules to prevent the LANs to talk to each other. A rule like this should do the trick:

At firewall>rules, LAN-tab: pass protocol any, source LAN-subnet, destination NOT LAN2-subnet, gateway default

At firewall>rules, LAN2-tab: pass protocol any, source LAN2-subnet, destination NOT LAN-subnet, gateway default

Now both LANs can get out to the internet but not to each other.

great thanks for that will get the nuts and bolts together

have found a few more nice features here that  will add.
(1) set the accounting update time
(2) allow to add a second radius server for fail back
(3) make all the changes to pptp server as well.

hope to have these done inside a week

ubuntu use apt for package updates, which usually use ftp or http. (cat /etc/apt/sources.list to see)

and remember that ubuntu just released their newest version, of course the mirrors will be slow

Have a look at http://forum.pfsense.org/index.php/topic,3330.0.html . It should fix your issue.

It's something I'm interested in, as I have an EVDO card for my laptop, but not anything I'll have time to look at for probably a few months. If you would like to shift priorities, start a bounty.

What you're describing is very typical of pegging your connection with cable. When you hit your cap, packets start to queue in your cable modem, and your latency goes through the roof.

hello
I have mentioned in very first post that I have already syslog machine… but it is useless in case of interfaces hanging

;)

Basically the config.xml is stored there only (the same file that can be downloaded at diagnostics>backup/restore). Additionally to that it will write the rrd data to this media on a clean shutdown (when performed from wengui or shellmenu). Everything elso is stored on ramdisk and therefore will be gone (like dhcp leases unless you have added static mappings which will be backed up in the config.xml).

That is what i use to test with.
http://www.nwlab.net/art/netio/netio.html
http://www.koepi.org/smbdownloader.html