Thank you Phil! This is good information.  I appreciate your time and perspective.  We've tried to keep anything out of DropBox and Google that was the least bit security sensitive.  But it's helpful to know some of the good reasons for that practice.  :-) I also hadn't thought about the certificates being stored in the XML file.  That's a very good point. Does anyone know if there is a limit to the size (length) of the AutoConfigBackup key? Thanks again!

Thanks for your reply. We don't have asymetric routing. There is just one LAN. pfSense acts as the NAT, firewall with less than a dozen rules, and DHCP server. I still have the packet capture file; I'd be happy to upload it to a place which is convenient for you.

Virtual machine equals Win server 2012 ye, sorry for not pointing that out. I did some configurations yesterday and managed to make static WAN work out! I sat WAN to 192.168.10.103 (static) and gateway as pfSense LAN adress. I also sat my homerouters IP-adress as DNS-server and I can ping everything included Windows Server from pfSense :) But I'm still not able to browse the web… So I guess it has to be something blocking port 80? I tried to check both Windows Firewall and pfSense firewall but couldn't find any settings that would block port 80. So there's still some troubleshooting left for me.

Steve, you were right: it was hardware related!  ;)

I currently have the same issue :( EDIT: Okay I have managed to get it working, it turned out for some really odd reason the network port the PPPoE was on wasnt the correct one, in fact it wasnt anything… As shown there is now the interface (alc0) for PPPoE but before hand there was nothing shown here also... [image: sdsdsd.png] So using the webconfigurator all I did was assign the WAN to alc0 (MY direct incoming connection (ISP infinity cable coming from the VDSL modem) using the assign interfaces, then I went into the settings specifically for WAN and configured it like so… [image: sesersdfd.png] Then as if by magic it suddenly started working, and the right interface was assigned to WAN [image: Capture.PNG]

This is really basic stuff here - not sure how it could be worded better? you have this client –- lan (pfsense) wan --- internet If your pfsense stuff going to clients would be out the lan, stuff from clients would be in on lan.  On wan stuff going to internet would be out, and stuff coming from internet to pfsense would be in.  Look at the traffic flow from pfsense perspective

The simplest thing is plug your modem into 1 Ethernet and your LAN into another one and enable snort. You could use LAN's but you will need a managed switch which isn't over easy unless you know what your doing.

During 2.1 development, there was a time when the "rate" utility returned stats for all IP addresses and I added the "Filter" option to the Traffic Graph GUI - Filter "All", "Local" or "Remote". Some time later, the "rate" utility was put back to just displaying what it was asked to (a subnet specified with the "-c" parameter to "rate"). Reading this got me thinking that actually the Filter option can be fixed up using the current "rate" binary but driving it creatively from bandwidth_by_ip.php This pull request fixes up the Filter option so it works as intended: https://github.com/pfsense/pfsense/pull/906 Hopefully this will be fixed in 2.1.1. From there, it should be relatively easy to add more filter options to display wider sets of IP addresses - people could suggest what groupings of subnets would be useful. [image: TrafficGraphAllFQDN.png] [image: TrafficGraphAllFQDN.png_thumb]

I might have been getting something similar to the crossed out stuff in this post, although I never had the same options checked.

Well can you not add a second nic to your hyperV box?  You could do it with vlans - does your switch(es) support vlans?

There is no conclusive list at the moment, but generally speaking: CARP Events (config sync errors, VIP state transitions, etc) Filter reload errors Gateway failures Corrupt config.xml Inability to upload a config with AutoConfigBackup Basically, anything that makes a notice flash in the upper right, plus a few other things. The notifications will be quite a bit more flexible in the future but probably not until after 2.2 ships.

Did it panic and reboot and offer a crash dump in the GUI? What sort of NICs are in the system?

Ah, of course, that would explain the rules. I'll just use the IP addresses and ranges rather than the pre-defined options. Thanks again!

See 4 posts below yours:  ;) https://forum.pfsense.org/index.php/topic,72307.0.html Steve