@alhaunts The way to sync time in pfsense is ntp.. You don't have to provide time services to anyone else. Ntp is both a client and a server.. There is no setting for like sntp that I am aware.. If you want pfsense time to be correct, you would setup ntp.. By default it just points to pool out on the internet provided by ntp.org If you want to make sure none of your clients sync to it - then just set the listen interface to localhost only.

@jimp Thanks for responding. StephenW10 sorted me out and Jan 31st backup restored today!

@andreanet said in correct installation and configuration: the source 10.10.10.9 is the IP address of the Lansonia router Do you have another "router" connected or perhaps you mean wifi Access Point? If it's an AP, and 10.10.10.9 is just the management interface for that AP, try disabling that rule. Then you will still see that all wifi clients will be able to access internet. Any traffic not targeting rule number two (destination 10.10.10.1 I suppose) will simply hit the last rule allowing internet access.

@bmeeks Patching was never easy to begin with. What I'm saying is that a package can be updated without releasing any interim pf release, so it needs less regression testing, than a full point release Maniplulationg text (php) and configuration files is different from changing binary files. What Im trying to say is that ce version isn't something left to its (security) fate, only to be fixed if and when the sun is shining.

It wouldn't be shown there. If it's anyway it will be in the main system log covering the boot up time or immediately after boot.

@netblues thanks a lot. this is what i thought :)

Oh, you can't have the same user defined more than once like that. You would need to add it without an IP so it just pulls an address from the pool. It should then be able to authenticate multiple times and pull multiple IP addresses.

I think this is to allow access to single snapshots for the general internet rather than actually viewing the webcam directly. I had something like that setup at one time (a while ago!) and used a separate webserver with a script that periodically pulled a jpg.

Yes. Unless it has a serial console which is generally preferred since you can copy/paste the output etc.

@johnpoz said in Unable to synch with internal network NTP server: Also a poll of 8 seconds seems a bit excessive if you ask me ;) Not for a LAN based server. I have done a lot of hw ntp testing in the past. I use -4 (16 per second) for my main servers. Unfortunately, ntpd cannot operate below 3 (8 seconds per).

The CPU in the 8200 is a lot more powerful so you see the widget usage in the 1100 far more. That is especially so because the refresh rate can start to hit the time taken to pull the data. Did you try the patch linked above to revert to the previous widget behaviour?

@elvisimprsntr Ok, thanks for the details. Your "NVG599" seems to be to a DHCP-relay, so it re transmits to the real DHCP server, somewhere in the ISP network. Anyway, the DHCP WAN seems fine and not a cause of your issue.

You could be seeing some conflict there but I would expect a complete loss of connection in most cases if that were happening. Try disabling one or the other and see what's effected, if anything.

Many thanks I’ll dig it out May take a while tho

I figured this out. I just had a big brain f@rt. I was trying to change my wan to one of my local address. I let Pfsense do its thing. P.S and thank you because I did still have to reboot. Appreciate the help

Send me your NDI in chat I'll check it. But, no, you would not need to reinstall if you had to register a new NDI.

thank you all

@Gertjan said in 24.11-RELEASE Shows update available, but the update appears to be a beta release: edit : also : afaik : Here, very soon now, a 25.03 Beta release bulletin will be posted. There it is : https://www.netgate.com/blog/tag/pfsense and it's shows up on the dashboard : [image: 1739013725474-9b54c578-ac85-4c71-9951-dbc77ef09d57-image.png]

@stephenw10 I decided since I was going to do a completely clean install that I'd follow the instructions to install an nmve ssd. Much success - everything works including reboot. But there was a mystery - tehere's a step to erase the metdata on your emmc drive. But when I got in to the recovery mode there were no drives at all. I suspect I had a bum emmc drive and it finally gave up when I went to do the reinstall. Good/lucky timing I guess.

If you never logged from 192.168.1.100 then that looks bad!