@stephenw10 Seems reasonable. Thanks for the advice on this. I will think about this a bit more. Appreciate it Stephen

@azureadministrator Sounds like it's a question for your host provider...

@stephenw10 We will try to find out. Thank you very much for your effort.

@michmoor That's a really nice looking flow chart/graph. Is that something you have as a plugin on pfSense? I've been looking for a way to get that for a long time. I too agree with your statements on NtopNG being useless for anything other than realtime flows.

Hello, Sorry about the delay. In fact the problem did not come from the configuration but simply from a DNS problem. I hadn’t paid attention, but the ping test was coming back to me from the IPs which does not concern my Network. The domain I thought was not used on the web is used. To make a test I tried to clamp PFSENSE so that it only gets my DNS from the AD without success. I changed the name of my domain and this time I made sure it was mine. Now it works out. thank you for your help.

@stephenw10 said in SSL termination, traffic forwarded to varnish cache: I would expect that work yes. There any many people using HAProxy on pfSense pretty much exactly like that. Just wondered if I was overlooking something or maybe someone had written a nice article on putting this together. Thanks for your input folks.

Everything is blocked by default incoming on WAN.

@johnpoz Thanks for your ongoing support! Not saying it's something wrong generally in 23.09 but at least something specific :-) Either in combination with my NTP server or something went wrong during the upgrade. Went back to 23.05.01 and everything is OK again [image: 1700388875485-bildschirmfoto-2023-11-19-um-11.01.37.png] [image: 1700388884603-bildschirmfoto-2023-11-19-um-11.01.52.png] After being back to 23.09 same as before... The flag "u" and "s" appears randomly or changes after some time, currently it is set to "u": [image: 1700389038112-bildschirmfoto-2023-11-19-um-11.16.09.png]

I just ran into a headache/nightmare trying to downgrade. I was utilizing the AT&T bypass (WAN Connectivity with 802.1X Authentication Bridging and VLAN 0 PCP Tagging). I also had a hard time using a backup to restore from... For whatever reason if I redid the basic configuration at least back to the LAN being my previous IP address AND THEN did the restore it worked. But I then had to troubleshoot why I didn't have WAN access which was due to the MAC spoofing needing to be undone... Very inconvenient from the Plus license changes...

@Gcon FYI I sorted this out with Netgate support. cheers.

Looks like this: https://redmine.pfsense.org/issues/14431 You have a number of interfaces that could apply to but I'd guess it's pppoe0. Do you have IPv6 enabled on that? On any other dynamic interface types? Steve

@stephenw10 A clean reinstall fixed the easyrule issues. All working fine now.

@JuneKlein the serial port is listed in device manager but may not be com3. There is a reset procedure for this model: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-4100/factory-reset.html

@stephenw10 Bless you! Have a lovely day.

Yup, rechecking I think I see the issue. The server timestamps changed when it was moved to new infrastructure so this is no longer true: https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/services_acb.php#L71 Setting that to UTC shows the correct times for me. Asked our admins how they want to handle it. I imagine correcting the server timezone will fix this but we shall see. Steve https://redmine.pfsense.org/issues/15005

FIXED. All i did was remove backend and frontend configuration and re-added it. Working fine. pcaps now show TLS communication with backend. Definitely a bug. Trying to reproduce so i can open a redmine but so far i cant.

@Gertjan My screen looks a little different, but I set it up this way and completed successfully. The 1dot~ address is the one I was trying to get from here. It seems it was actually a different one... https://blog.cloudflare.com/ja-jp/enable-private-dns-with-1-1-1-1-on-android-9-pie-ja-jp/ ! alt text