@Phonix66 said in User called “internet”:

I suspect the ntopng package, I didn't login for a while and tried now to login with the "internet" user, but couldn't, nighter with my Administrator account.

The ntopng package does not create such a user. What made you suspect it?

[Edit: You can ignore this -- I just saw that you subsequently determined that it wasn't ntopng]

@stephenw10

That worked @stephenw10. I rebooted the computer and all is well.

Thanks for the assistance.

@stephenw10 said in Connecting to server on a seperate LAN from camera connected to NVR wifi LAN:

Is your NVR device there routing that traffic or NATing it?

If it's routing (a much better setup) then you need to have a static route and gateway in pfSense so it knows how to reach the 22.1.1.X subnet.

If it's NATing then you would need to setup some port forwards in the NVR and send traffic to that.

Are you really using 22.1.1.X there? That's a public subnet which may conflict with something you might want to access externally someday. Though it appears to belong to the DoD so.... 😉

Steve

A static route did the trick.
Thanl you.

@stephenw10

Now I'm really calmed down, thank you!

Hmm, well those P2s don't match so if one side tries to open a P2 with a /16 defined the other side will reject it.

You should see a bunch of errors in the logs for that though. And I wouldn't expect to see the P2s come up in the status.

Cron job @reboot the mount commands

Yes I was offered 24.11-RELEASE (arm64) after a short delay

All done - thanks again!

@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.