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!

Yeah the MAC address being the same is odd...

Yup there we go. Tailscale acts more like a proxy in firewall terms. You can only see the traffic to/from it and not the source/destination inside the tailscale network.

Thanks All, The other confusing part for me was that I couldn't ping the Windows machines as you have explained. However, I could ping the Debian12 machines. Boy is there a lot to learn. Thanks again.

So if any one 'flow' exceeds 2Gbps then all other traffic will be dropped? You can apply limiters with masks set retrict any particular flow to 2Gbps, or just below that. https://docs.netgate.com/pfsense/en/latest/trafficshaper/limiters.html#creating-limiters

Some services are pre-defined in the shaper wizard but it's by no means definitive.

@stephenw10 @nimrod Thanks for the advice guys. I have been so busy but managed to get free to look into this. I nuked my pFsense and this time I set a keep alive 25 seconds on the peer, now I get handshakes. I followed every step in the Mullvad guide, looks like I've got a Mullvad IP assigned and no DNS leaks so I guess it worked. Only issue I noticed is that if I reboot my Protectli, there is still a handshake between the peer and tunnel but I can't get internet access. I had to nuke my install again and follow the guide again for Mullvad wireguard to work.