[solved] A lot of "reserved IP" traffic going out on WAN while Nexus is enabled
-
I get this notice: Nexus cannot be licensed on this system due to: unsupported virtualization.
And I get a lot of these in the logs:
I want it to stop.
Version 26.07-RC
-
@Bob.Dig is that a reject rule? I have not played with nexus yet, is that reserved46 a built in rule or one you created?
-
@johnpoz said in A lot of "reserved IP" traffic going out on WAN while Nexus is enabled:
is that reserved46 a built in rule or one you created?
The Alias is built-In, the reject-rule is on me.
I suspect, it is related to me running pfSense on Hyper-V and Nexus wrongly thinks, it is running on Azure.
-
@Bob.Dig I would never suggest a reject rule on wan - this is way to dos yourself ;)
If they hit a port/protocol on your IP - your just letting know your there even if they would normally get no response. Rejects are good on your lan side, hey don't bother doing a retrans - you aren't going to get there sort of thing. But never on the wan - unless your wanting to answer a traceroute port.
Still very odd that you would see such source traffic - very curious traffic. I mean why would you be seeing destinations to all those different addresses? Not only from the odd sources - but to those destinations, does your wan have those addresses? Why would your wan even think to look at traffic sent to a 169.254 address? And also 10.0.0.39??
The really weird ones are 192. to 169... How would that traffic even be generated?? How would something internally be wanting to talk to a 169 address? Those are outbound right..
-
@johnpoz said in A lot of "reserved IP" traffic going out on WAN while Nexus is enabled:
But never on the wan
You are right, although reject is only on outbound.
How would that traffic even be generated??
If I have to guess, Nexus is doing it and it is Azure related (which I am not on).
-
There shouldn't be any requests to the local Azure API on that platform. We'll work on fixing that.
-
@marcosm said in A lot of "reserved IP" traffic going out on WAN while Nexus is enabled:
We'll work on fixing that.
Great. There are a few connections to 169.254.169.254 over the day, even if Nexus is disabled.
-
This has been fixed with the latest repoc and Nexus package versions now available in 26.07:
https://redmine.pfsense.org/issues/17101 -
@marcosm Thanks, looking good so far with 26.07_3.
Privacy Policy · Cookie Policy