You are running 32bit and not even the latest 32bit version. That CPU can run 2.4.3_1 so you should be on that really. You have no DNS resolution at the client. Is Unbound even running? Check Status > Services. Try Diag > DNS lookup which should try pfSenses own DNS servers. You can ping 192.168.10.1 from the client but can you ping 192.168.1.20 or 192.168.1.1? Steve

@andyc Yeah, i want to have access to my ESXi management from work and at home. (only for a while, as I am preparing everything for my VM ect ..) i will make a IP restriction or something like that if it's possible, to allow only my home public IP and the work IP Or i can just do a VPN with my pfSense (i saw come options to do this), i don't know, i'll think about it

More info needed @OP What exactly are you trying to make work that is not working across subnets? Not really a pfSense question at this point. Steve

Probably not in this case.

It works with Google DNS on Apple TV manually. Thanks for your help guys!

Mmm, it does seem unlikely we can do anything to help much in pfSense then. If you are at some other location, not behind pfSense, and it still behaves the same then that would confirm it. Steve

Ok I am calling this fixed. I've got an uptime of 14 days after disabling AES/NI on this machine. Previously I couldn't make it past 4-5 days.

@slimaxpower Me?

@strike101 With that user count and speed the Netgate SG-1000 might be tempting. Product page https://www.netgate.com/solutions/pfsense/sg-1000.html Speed https://www.netgate.com/docs/pfsense/solutions/sg-1000/faq.html#what-should-my-speed-test-results-be Price @ $150 https://store.netgate.com/SG-1000.aspx

What do you have net.link.bridge.pfil_member set to? That needs to be set to 1 to filter traffic on the bridge member interfaces which it sounds like you're trying to do. And setting both to 1 is probably not required. Do have the bridge interface assigned even? Do you actually need a bridged setup? You can disable NAT without bridging but you still route. Steve

there is not enough info to go on.... Start by removing all VPN related configuration .... then reboot to be sure all routes are cleared. a)do you get an ip from pfsenses dhcp server ? b)can you ping from the client to pfsense? c)can you ping from the client to 8.8.8.8? d)can you ping from the client to google.com? If you manage to get 'd' working, start adding the VPN stuff back in

Solved by a clean install. Something must have gotten messed up over numerous upgrades.

@ivor said in Change date format: I'll see what can be done. Keep reporting things like these, thank you! Just to clarify, are you talking about forum? Or about pfSense? Pfsense you can change the format on here fine. His post was 7 days ago forum wasn't here than =D

You're welcome glad you get it working

No worries. It's an interesting script but it's old and clearly needs some tweaks for a current pfSense version. All of your CPU time to create random PIDs seems extreme!  ;) Steve

Your rules are kind of a mess. Is this problem only happening for users on VLAN13, or is it everyone?

Hi. Did you enable enable Transparent proxy and SSL filtering? Just in case follow the instructions in the following link. https://www.howtoforge.com/pfsense-squid-squidguard-traffic-shaping-tutorial