@keyser Done on Server and done of Pfsense. All my internal buffering issues were resolved with this "Set-NetTCPSetting -SettingName "Datacenter" -MinRtoMs 300" wired or wireless, clean, direct play files, no issues, so server to switches and devices, again, wireless controller is a vm on the same vds as the pfsense server and no issues (LG TVs playing 144mbit streams, no buffering direct play) I removed pfsense, tested with an ASA firewall, tested with a 4451, issues are gone (I need my IPTV to work for I'm kinda stuck with PFSense and opnsense but opnsense has its issues) There something weird about uploading to people, the pfsence just seems to crap the bed on it. To add, 30-40 Streams at 20Mbit each, zero issues.......trancoding, the second a direct play hits and its bitrate is over 20Mbit, buffering like an idiot and only with a pfsence firewall.

For that kind of setup you'll also need the patch from https://redmine.pfsense.org/issues/11433 on 2.5.0/21.02

@howaziti Read my 3 posts hee https://forum.netgate.com/post/944383 /Bingo

@alex-ku What do you mean by CSV parts ?

@noplan said in unbound question generate keytag query _ta-4f66: _ta These : [image: 1614586564796-45d46f59-ddc4-4232-851b-0cbb020660e8-image.png] are inoffensive. They show that Unbound is using DNSSEC. (Most of) not all sites are not set up to expose DNSSEC in their domain. For your own domains : if your domain registrat has a plug-and-play version avaible, consider using it. But document yourself first for its advantages and inconveniences. Use https://dnsviz.net/ to check DNSSEC status of a domain.

@nguser6947 I don't know about the Netgate boxes, but that certainly wasn't the case with the community version. A few weeks ago, the computer I was running pfsense on died. When I installed it on the new computer I was able to copy over the config and it worked fine.

Missed this in my initial post but after doing another search I came across this: 1. Temporarily enable IPv6 on your LAN interface and set IPv6 Configuration Type to "Static IPv6", then assign it an IPv6 address ("::1" without quotes works with mask /128). Then Save. 2. Go to Services/DHCPv6 Server & RA/LAN/Router Advertisements then set Router Mode to "Disabled". Then Save. 3. Go back to the LAN interface and set IPv6 Configuration Type back to "None" then Save. Seems to have worked and I can now make changes to the LAN interface.

I was getting "diag.backup.php" file when a backup was generated. It appears this was a temporary issue. I'm now getting the normal file format (.xml) after a reboot.

You also are using public IPs in the P2 and NATing to them? How is it failing? More info needed! Steve

@choggy2840 Should have post in Firewall section to attract the best responses. Using floating rule aliases could simplify your firewall.

My issues were in part related to this I still think something isn't quite right, but will post in the proper forum.

Thanks for the link. Saving the wan settings again was the solution for getting IPv6 working again.

@stephenw10 said in Fresh install: WAN goes down and 502 Bad Gateway: running that as router-on-a-stick with VLANs rather than use a USB NIC if you can. Steve thanks. long story short: it was the usb nic. AX88179 controller is a pita for pfsense

@gwaitsi well, i got to the root of the problem but don't know how to solve. If I set the GW to WAN1 or WAN2, smtp is working. If I set the GW to WAN_GW or VPN_FW it is not working. This is true whether i put the WAN1/2 hard down. So something with using the gateway group is killing my smtp on certain clients. Have no clue on how to solve, everything else seems to work.