Is your wireless a wireless card in pfsense?  An AP on your lan network, a wifi router?  Did you configure this wifi router as AP or is it also natting? So your saying clients wired to pfsense work just fine - its only your wireless that is having issues.  Please describe how your wireless is setup.  If interface on pfsense optX for example then you would have to configure the firewall rules on that interface to allow traffic.. By default any new opt interfaces you create in pfsense have NO rules and all traffic is blocked.

They are still routing to the IP address. But on the local segment traffic to the gateway address is ARPed then traffic is actually sent to the MAC address. All that happens is the backup node starts responding on the MAC address and the CARP VIP. The hosts don't see anything change. The switch moves the MAC address to the new port automatically. It all works pretty well.  Google for CARP, HSRP, and VRRP as has been mentioned. Good writeup in the pfSense book. You'll want to read the 2.2 release notes since the book is 2.1 and CARP VIPs changed in 2.2.

Hi John just thought I'd see if you had any more thoughts or suggestions or if you needed any more info from me.

VMs could look like more clients.  A bit of Googling should show up some tools that could help.

@LinuxTracker: So dooods.  All pfSense.org's DNS records have disappeared - pOoF! What happened? Just got JimP's tweet about it https://twitter.com/jimptwit/status/701769760560656384 "Some planned maintenance is running long." Looks like it's back… Was unable to reach anything this morning...

@Alex: You do realise you will just end up blocking Windows Update and Windows Defender, potentially leading to much wider security issues than Microsoft being able to see what apps you use. Yes, I do. Although, to be a nitpicker, the telemetry stuff is not a security concern. It's a privacy and control concern. I make the choice to have privacy (and control) in cost of security. Microsoft is not transparent and honest about what a patch does. It's not like FreeBSD, pfSense, and Linux distros. There are numerous articles mentioning that Microsoft introduced telemetry in Windows 7 and 8 WITHOUT being clear about. Without giving users the choice. If you use Windows, you have two enemies: the malware creators and Microsoft itself. By using Windows I accept that my computer is insecure. I mitigate the issue by using none of the bundled software (I hope that'll manage to have Skype updated, if not I'll just run it in a VM), using an anti-virus solution, relying on the firewall of my modem-router (and pfSense could very well replace that), and being religious about backups.

Hi, what is the status of Status: Gateways have a look in Status: System logs: Gateways maybe the apinger is doing some strange thing.

yes i believe @marcelloc contributed the code for the counters for 2.3 aswell (but don't shoot me if i'm mistaken)

I assume you mean VirtualIP as IP alias means something different in pfSense. Only thing I can think of is check your NAT/Firewall rules as I cannot think of any good reason why a VirtualIP would perform any different to the main IP.  Its just another IP address assigned to the same interface, nothing special about it.

I find using PFblockerNG DNSBL does a better job of blocking ads. I know this is not what you asked but it might be another option for you to consider :-) Cheers Jamie

Your physical WAN and LAN interfaces are only the parents to your VLANs, right? Then you have to filter on the vWAN1/2/3 and vLAN1/2/3.

Glad you got it working!  :)

https://forum.pfsense.org/index.php?topic=91074.0

An ISP tech came out here but he of course had no idea what the problem was… verified the WAN worked with a TPlink router set to the static IP. I'm going crazy trying to figure out what is wrong. I reinstalled pfsense, my last attempt the WAN connection worked for about a minute after turning off the modem, setting the IP to static on pfsense, then plugging the modem in. Currently spoofing the MAC of a Cisco router. On a machine on the LAN I had a continuous ping of 8.8.8.8 running. I ran a packet capture on the pfSense WAN interface during this whole process until I lost connectivity. I saw TCP application data, DNS response, ping replies, NTP exchanges, ARP broadcasts and replies, etc. Everything working fine. 40s into the capture it stops behaving and it shows nothing but DNS queries, ARP broadcasts from the ISP Router, ping requests, some TCP retransmissions... Right before I stopped getting ping responses for the gateway it ARPed for the static ip 5 times, once every ~30ms. pfsense responded immediately to each arp with the spoofed MAC as it did earlier in the capture. For the next 2 seconds I got 2 ping replies and then nothing.  :'( :'(