@uscut out of the box nothing is blocked. I am accessing it just fine (just checked), are you using proxy, or pfblocker or snort or anything? That seems more like a block on their end, Your trying http vs https?

@mikev7896 said in 22.05 Upgrade question - ZFS/snapshots: I assume that I'd need to download 2.7 CE and then re-upgrade to pfSense Plus? For reference, currently you would need to re-install 2.6, upgrade to 22.01 and then update that again to 22.05. At some point the CE > Plus upgrade repo will be switched to 22.05 and then it should be possible to update to it from either 2.6 and 2.7. Steve

@neiltiffin said in pfSense 2.5.2 video stalling and buffering: @stephenw10 I found in the last 10 years of using pfSense that being an early adopter is not wise. My experience with upgrades has not been good, often retreating to the command line and a reinstall even though I am on a Netgate Appliance. Ok so I upgraded from 2.5.x to 2.6.0 using the ui this time, and it worked. Pleasantly surprised. I hope this is the future as I had given up on using pfSense. We'll see how the next few upgrade go.

@danlad sorted it, had to do an system update and it was listed in there.

I haven't seen that happen here and I've restored several dozen times during 22.05 development with all sorts of different configuration styles. I haven't seen either of the behaviors you describe thus far. One thing you might want to check is the update branch in the saved configuration. Look for (and remove) the <pkg_repo_conf_path> tag(s) and contents before restoring and see if that makes a difference. Also if you have extra data in the backup such as RRD, DHCP leases, etc, then it can greatly increase the size of the backup file and can cause it to take longer to upload and restore.

@bingo600 If you create a allow rule with their IP, then when they create traffic to whatever that is allowed that would be logged. But only first instance of such traffic, which seems like what your after..

@stephenw10 said in No log entries: mber that opened a state. Then you can check which rule that was using: pfctl -vvs got it. ill do some testing today and report back.

Yes, that would leave you with the default sysctls.

It shouldn't just freeze. But if that's a real concern for you then setup an HA pair. Or maybe some OOB access to the console. Steve

@stephenw10 Thank you Steve! Late last night I realized that VLAN10 needed to be tagged on port 5 but completely missed removing port 2 from VLAN1. This got Wifi sort of working. The Airport would get an IP and DHCP clients would get IPs but this would hold for about 20 seconds and then it would lose its IP for 20 seconds, then get another for 20 seconds, endlessly cycling. I kept thinking I must have the DHCP service misconfigured somehow. Once port 2 was removed from the VLAN1 list everything started working properly. Thanks again Steve. As you can see I have the VLAN10 and VLAN1003 firewall rules set wide open while trying to figure this out, so the next step will be to lock them down more.

@jimp Ok, maybe. I actually went away to make breakfast and came back and was sitting at the login screen. So I don't think it was a timing related thing of being too trigger happy. I remember seeing this once before during the 22.05 betas and it's definitely just a cosmetic thing, so I won't worry about it. Let's see if any other people report it.

Not with pfSense. Not if you actually want to be able to use both 4G links for a single connection.

Necroposting a vague message on a 5 year old thread, they're most likely a spammer/spambot.

Understanding your wish for personal support... But as this is a forum, i think it helps everyone (well, at least more than one individual) when such stuff is posted for public, since many ppl might contribute knowledge and experience AND many can get some helpful input. Jm2c :)

@bearhntr said in pfSense 2.5.2 - Web Console super slow: @bmeeks When I had it setup before -- I was using the ORBI as my Router - DNS - DHCP...and Windows AD DS also seemed to be working in conjunction - but I would get strange outcomes from things there too. As I said, when using Windows AD, you really must use a Microsoft DNS server in order for all of the Active Directory things to work. Some bits and pieces might sort of work with a non-Microsoft DNS server, but some key parts will not work and lead to the strange outcomes you referenced.

@stephenw10 Yes, thanks for that, downloading the config file and examining it , I saw my old pwd described under "gold encryption password" as well my newly created one . Did another manual auto config backup , made a minor change to one of the comments on a VLAN then did a full restore to its previous state - all fine . I honestly had no appreciation before that literally everything is present in that config file - unhashed passwords, digital certificates etc, not a thing to leave lying around !

@nizo67 It is working fine with squid now. The desired sites could be blocked. Thanks to all of you for your help and support. Have a nice lovely weekend. Regards

pfSense will only allow access from the WAN side by default if there is only one interfaces assigned. As soon as you assign two of more interfaces all connections to WAN are blocked by default and you need to add WAN firewall rules to allow them.