Quote from: Monviech (Cedrik) on December 05, 2025, 05:32:48 PMMost likely the following option:
Firewall - Settings - Advanced - Automatic outbound NAT for Reflection
Deactivate it
Read this and learn if you need it:
https://docs.opnsense.org/manual/how-tos/nat_reflection.html
Quote from: DEC670airp414user on December 05, 2025, 03:38:19 PMi am not using this product. but i did sign up for it. i stayed with Opnsense Business edition geoblocking
anyways. my lite account says unlimited requests using the API access.
seems weird they would be blocking all of a sudden?
Quote from: viragomann on December 05, 2025, 03:24:16 PMDu solltest aber jede Seite auch so einstellen können, dass sie die Remote-ID gar nicht prüft.
Quote from: Kets_One on December 01, 2025, 08:25:00 PMThanks for the suggestion.
However, I don't have managed switches installed. All other networking equipment I have monitored for years without such behaviour.
Strangely nslookup of 94.16.122.152 resolves s7.vonderste.in.
Not known as a part of the ntp.pool, maybe just an NTP client.
Indeed this doesnt explain the source ip.
Update:
Just now a new request was made from 192.168.90.100:123 to a different destination ip: 217.144.138.234, which appears to be an NTP server: ntp2.wup-de.hosts.301-moved.de. Again i am unable to locate the source ip / host on my LAN. Maybe some WireShark is in order...