@Rasco: I am looking for a script that can ping hosts on the LAN and WLAN and when there are no host left, then pfSense router can halt the system. The reason is that my network 70% of the day doing nothing. Why not do it the other way around? Configure your router to use wake on lan (WOL) and if there IS traffic, it boots up and stays up. Sounds dangerous to allow a script to shut down the system. How ever a quick and dirty shell or perl script that checks the output of, for example tcpdump on an interface and a loop and a counter to check if nothing happened for X amount of minutes etc. OT: If electricity cost is the issue, why not switch to less power hungry components such as Intel Atom or similar, the power consumption on these while idling is almost none and probably switches, UPS, etc consumes more power than the router itself during these times your network users are busy IRL? Cheers E

Should just be a matter of importing it via the certificates manager: http://doc.pfsense.org/index.php/Certificate_Management Steve

Hi! OK I went to: Diagnostics: Packet Capture and start to capture my gateway IP. In log now I have ping echo request and ping echo reply every second. So I should monitor this and when link disconnected I stop to capture and see if there is a gap in log file. Correct? Regards, m

Actually in many configurations, pfSense 2.0.x is much faster than 1.2.3 with interfaces. Especially with large numbers of VLANs. There are quite a few factors that can go into it though. It really depends on the specific action you're taking that you believe feels slow.

Those come up now and then on FreeBSD lists - since you're basically using FreeBSD in a server role there (mostly squid, and freeradius), suggestions for tuning the values mentioned on the error for FreeBSD in general may be good to follow. Have a search/look through the freebsd-stable and/or freebsd-questions archive and the FreeBSD forum.

Sorry to dig up this old thread, but this happened to me recently, TWICE. And the fix for me was to go inside lightsquid config and change the squid log directory to var/squid/log. The default on install tell lightsquid to search on var/squid/logs

You can just reassign the LAN interface from the webgui in Interfaces: Assign network ports: Use the drop down to set LAN as bridge0. However there is a strong possibility that when you do that you will lock yourself out of the box. Make sure you have firewall rules in place so that doesn't happen, or some plan to get back in! See my post here, particularly the attached screenshots. The way bridges are controlled in 2.0.X is in fact better once you realise how it works, it's more flexible. However I agree it's confusingly different.  ;) Steve

Not entirely clear what you're trying to do, can you elaborate?

Means it can't ping whatever you have set as the monitor IP (gateway IP if you don't have any set).

What do your traffic and quality RRD graphs look like? That'll tell the story on whether it's that you're just exhausting your bandwidth, or if it's a connection problem of some sort.

@luke240778: Is there a way that an admin can setup so that pfsense sends an email to a certain address whenever a certain user makes any changes?  For example, when user "a" adds a name to Captive Portal MAC passthrough list, that i get an email? Also, setting up the email notifications.. cant seem to do it with my email which is hosted by 1and1.com  has anyone else had any luck ? Is there any way to have pfSense send me an SMS text, or email when a user logs in to OpenVPN?  This would be very helpful for me.

^ exactly – it is possible for your machine to have a locally cached record for what your doing that got cached from elsewhere. Really need to understand how your resolve, and what what your actually wanting to resolve to make sure your resolving the fqdn your wanting to use correctly. a simple ping should show you what the box resolves your fqdn too, which should be the exact same thing your ssh client resolves. as mentioned before using actual resolvable stuff as example is bad.  And again I would stress if running your own local zones - I would use something that can never be resolved on the public for your tld, like .local or .lan or .localdomain -- when you use actual tlds that can be resolved public you might be having an issue where its being resolve using public dns vs locally if you don't have something setup correctly on your local nameserver.

Thanks for the explanations. All clear now  :).

@chpalmer: Id see if you can find a firmware update for your modem. Is it possible your running pppoa on the modem but pppoe on your pfsense box when the modem is bridged? Thanks for that and I had checked that possibility.  With different modems, it still dropped.  Remove the Realtek cards,,,,,,no more drops. I appreciate you taking the time to reply…........

It has nothing to do with what they're using for DNS, you have to configure your firewall rules to only permit traffic to the proxy and other traffic you need to allow directly out, and not allow HTTP or HTTPS directly out.

Yep, figured after research. Fixed.

Distinguishing a legit RDP user vs. a brute force attacker is impossible to do accurately at the network level. Nothing at the network level has that kind of visibility into RDP. Limiting the number of simultaneous connections per IP is the best you can do. That type of scenario has to be detected by the server, or something monitoring the server. To react to it, something on the server or monitoring the server could be scripted to block the IP on the firewall.

Not on a 32 bit piece of hardware.

Big Thanks to MIQ in the IRC channel!! here is how to do it for any future searches: Pf sense >firewall>virtual IPs add a new rule: type ip alias, wan interface type network (IP address/subnet mask) save and apply Pf Sense >firewall>nat outbound tab, save in manual mode then add a new rule: leave do not nat unchecked. interface wan select protocols source (your internal server) destination any translation choose your alias save and apply. move rule up or down in the outbound mappings. If all goes well then that box should go out on the IP specified in your alias good luck