Yes, there was a bug in 2.3.X that prevented IGMP proxy running on VLAN interfaces. You can read about it in that bug link I posted above.

That's just another reason you should upgrade, that is fixed in current.

Steve

Exactly!!! BS error that doesn't say what the problem is!

Thanks for the explanation, it's not my exact scenario but will help others.

Thank you everyone for assisting

I wrote another script on powershell which works for me, will post when it is fully functional with other additional features.

@1OF1000Quadrillion said in NTP / System Time Oddities:

PS - When I was in the BIOS I did not see an option to select or change time zone data - I saw date/time and that's it.

That's because the computer clock only knows whatever time you set it to. It has no other means of being set, so no need for time zones. In this respect, it's no different than any alarm or stove clock. On the other hand, NTP servers, which can be anywhere in the world, provide UTC, which a computer then offsets to local time. This is where the time zone comes in.

Yeah, as you found you can just add more keys below the first one.

@Pedro-ramirez said in Account:

some other option that you know, thanks.

https://docs.netgate.com/pfsense/en/latest/usermanager/locked-out-of-the-webgui.html
Forgotten Password with Locked Console

If the console is password protected and the password is unknown, all is not lost. It will take a couple reboots to accomplish, but it can be fixed with physical access to the console:

@lordofpc734 said in NTOPNG Reports TCP Out Of Order packets for 3 clients (2 wireless, one wired):

im in a SNR war with my ISP. (means im getting really high noises and crap service)

That is a likely cause. A noisy line means lost packets and that in turn kills performance, as TCP will have to wait for retransmission of lost packets.

The problem is fixed after removing ntopng.
No more spikes.

Thank you

It's open source you can change anything you want. 😉

There's no way to change that via the normal pfSense config though, you would need to edit the file that generates it.

Steve

It should show when it does renew at other times and you will see what the lease time your ISP gives you. pfSense will usually try to renew it at 50% of that time. If that's not happening it would be a problem.

Things like changing to a failover WAN, invalid firewall aliases, bootup, upgrade status, dynamic DNS IP update, CARP status change, etc.

Nope ntop doesn't block anything. Do you have Snort or Suricata installed? They are far more likely.

Or that could be a symptom of whatever is actually causing the problem, the laptop tries much harder to connect opening a lot of connections.

Steve

The USG appears to have a number of VPN options including OpenVPN so I would not expect any problem doing that.

The only issue might be the DynDNS setup and whether you can use an FQDN rather than an IP as the server but it seems unlikely that would not be allowed.

Steve

Yup. You should set a source IP (and an alias of IPs) to allow access from. Use a dyndns client if you don't know where you will be connecting from.

Steve

We don't include all of the necessary components for at to fully function out of the box.

The binaries are there, but notably the cron job is not present. I can't remember what else might be missing, though.

You could install the Cron package and then add an entry for this:

Yep, making the change to StartTLS just required the 16/11 trick and it's up and running. Thanks for the hand!

@Gertjan thanks for help

i changed my amazon smile donations to the freebsd foundation

Just running a lot of VM's on small disk/SSD space, not worth too much effort. Thanks for the input.