@Patch @stephenw10 Thanks for your help! Replacing the switch fixed the issue! I factory reset the TP Link managed switch and it's working now too. It's sometimes the simple stuff you over look on the troubleshooting path that trip you up. I could not determine any reason why the TP Link managed switch was preventing the Proxmox GUI from coming up. I checked everything before I reset it. Thanks again!

Hmm, I don't think I've ever tried to do that! You're right it doesn't ask if you want to enable https after setting the interface IP. I wouldn't call that a bug though, an oversight maybe but that's the intended operation. You can always set it in the config file if you really need to enable it before you have access to the webgui. You can open a feature request: https://redmine.pfsense.org/ Steve

@jhonthan said in DDNS doesn't work on version 2.5.2: DDNS doesn't work on version 2.5.2 Anyone saw this problem? No, DDNS works fine. Keep in mind that the "DynDNS" facility build in pFSense uses : /* * PHP.updateDNS (pfSense version) * * +====================================================+ * Services Supported: * - DynDns (dyndns.org) [dynamic, static, custom] * - No-IP (no-ip.com) * - EasyDNS (easydns.com) * - EasyDNS IPv6 (easydns.com) * - DHS (www.dhs.org) * - HN (hn.org) -- incomplete checking! * - DynS (dyns.org) * - ZoneEdit (zoneedit.com) * - FreeDNS API v1 (freedns.afraid.org) * - FreeDNS IPv6 API v1 (freedns.afraid.org) * - FreeDNS API v2 (freedns.afraid.org) * - FreeDNS IPv6 API v2 (freedns.afraid.org) * - Loopia (loopia.se) * - StaticCling (staticcling.org) * - DNSexit (dnsexit.com) * - OpenDNS (opendns.com) * - Namecheap (namecheap.com) * - HE.net (dns.he.net) * - HE.net IPv6 (dns.he.net) * - HE.net Tunnelbroker IP update (ipv4.tunnelbroker.net) * - SelfHost (selfhost.de) * - Amazon Route 53 (aws.amazon.com) * - DNS-O-Matic (dnsomatic.com) * - Custom DDNS (any URL) * - Custom DDNS IPv6 (any URL) * - Cloudflare (www.cloudflare.com) * - Cloudflare IPv6 (www.cloudflare.com) * - Eurodns (eurodns.com) * - Gandi LiveDNS (www.gandi.net) * - GratisDNS (gratisdns.dk) * - City Network (citynetwork.se) * - GleSYS (glesys.com) * - DNSimple (dnsimple.com) * - Google Domains (domains.google.com) * - DNS Made Easy (www.dnsmadeeasy.com) * - SPDYN (spdyn.de) * - SPDYN IPv6 (spdyn.de) * - All-Inkl (all-inkl.com) * - DuiaDNS (www.duiadns.net) * - DuiaDNS IPv6 (www.duiadns.net) * - Hover (www.hover.com) * - DreamHost DNS (www.dreamhost.com) * - ClouDNS (www.cloudns.net) * - GoDaddy (www.godaddy.com) * - Azure DNS (azure.microsoft.com) * - Dynv6 (www.dynv6.com) */ Just recently, last week or so, OpenDNS broke their server side app. That's repaired now. Namecheap has issues right now - see recent threads about namecheap. no-ip has regularly ( ? ) problems ...

@gertjan yes, I checked yesterday and it's also fixed for me. Thanks!

@aglarond You will find many a post by me going over transit networks ;) have to explain it like every other day it seems ;) Users are always trying to use their normal lan as transit and then wonder why they run into asymmetrical issues. Here is a good drawing that explains what has to be down with a downstream router. [image: 1639335337947-pfsense-layer-3-switch.png]

@stephenw10 Thank you very much for the reply. I searched, but couldn't phrase my question properly to find that.

It depends what the fibre is. It's probably GPON? In which case your options are limited.

@mattfiller said in Could this be malware in my pfSense - it is not blocking MS RDP attacks: (we have 5 incoming 3389-MS RDP Port Forwards to individual PCs so people can work from home) Yeah this is a bad idea for sure - and your going to see tons of traffic to those ports. I don't have it open but just looking at the firewall logs sees lots of noise to that port [image: 1639234463663-3389.jpg] If you have remote workers that need to rdp to some machine on your network. As suggested by @stephenw10 either VPN in (best option).. Or lock down the source IPs to who can hit that port and be forwarded. Best would be to lock down to the remote users specific IPs.. You could use say dyndns entries so even if their IPs change, etc. While changing the port from 3389 on your wan side is not really a security measure, if you used different ports to to your specific devices 3389 port, this would remove some of the log spam, and lower the amount of stuff that is forwarded to the actual client.. While security through obscurity is not something you should rely on - it doesn't hurt if you make bots looking for open rdp ports harder to find you. Once some bot or outside finds your rdp port is open, they will normally bomb you with brute force attempts to get in.. Trying all kinds of username/password combos..

Your memory usage is unrelated. pfSense does not include log4j neither do any of the available packages. log4j is not even in our repo so to be affected you would have to have manually installed it from the FreeBSD repo and configured it to be listening somewhere. Steve

@mediatek said in Installing Pfsense as a VM: After I made the change I have to do the command again... This is the main problem, That is not a problem, it is expected. That command disables the firewall entirely. It should only ever be a temporary workaround to allow access while you add a rule to allow something for long term access. You can see your rule has not created any states or passed any traffic to however you're testing that it's not matching. Steve

Assuming it's an IPSec VPN then that's the way to work around it. https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/access-firewall-over-ipsec.html#static-route-workaround And, yes , in pfSense you should never be manually editing a conf file like that. Steve

No, there's no way to change the default sort order as far as I know. Yeah, I was asking for a screenshot because I couldn't replicate what you were seeing. I don't actually think they are sorted by IP address. They just appear to be to you because you only have static leases configured. When you apply a sort order it's shown above the column and that is not that case in the default view. Steve

What latency are you seeing now? What do you expect to see? What traffic are you looking to apply this to? Steve

First learn how to port code to FreeBSD. Then port that Linux code to FreeBSD. Once it builds for FreeBSD try running it in pfSense. It may be easier to write a FreeBSD module from scratch. As far as I know there is no FreeBSD implementation so nothing we can add in pfSense currently. What exactly do you want to use this for? You realise that TCP congestion control is only applied at the end points of the TCP session? That means almost no traffic through pfSense is subject to it. It's the reason we don't include other CC modules by default. Steve

@stephenw10 said in Can't access the specific website after configuration in Netgate Pfsense: so you have Squid running Wt*** ?!? @Tiger-0 Couldn't you just post images like : [image: 1639143056544-4bb56e1f-30f2-47c1-951a-4d6e6a7b721b-image.png] The issue would have been solved in a couple of seconds. That is, for us. For you it would have been solved after you know how it set up 'Squid'.

@stephenw10 Yep, got a few ideas I'm exploring now, thanks for the assist however. I did read an article about using Squid on pfSense to get data that was decryptable in wireshark, but for the life of me know can I heck as like find it. :-)

Yeah, it will always be running in 21.05.2. You can apply the linked patch above to stop it running by default. However your free ram never gets close to 0 so that's probably not the cause here. Steve

I'm confused. Did you try installing pfSense bare metal (no hypervisor) on any hardware?

Was going to say pretty much the same thing - but Bill did it way better ;)

@stephenw10 Thanks sir, I will do that, but first I wanted to try a few more things to gather and capture data for reference, i.e. like trying the WAN>server (or something that will work since I don't have my own server setup) LAN>client iperf3 test (like in the video and the discussion post @johnpoz referenced.