Comments
-
Thanks @"james.carson" The IP address is correct according to the traffic log. There is a possibility the traffic is being sent to the wrong interface if something stripped the VLAN tag. I'm curious why the interface is reported as "firebox". I noticed something else that might be of interest. Syslog traffic that is…
-
I realize this is an old post. Gary, do you remember the resolution for this? I'm having a very similar issue with an AP trying to send syslog data back to the controller. Most of the time the syslog traffic correctly passes through from my management VLAN to the controller, and every once in a while I get a IP spoofing…
-
I did see that in the manual as well, but wasn't sure what their definition of inbound traffic is. Also, the second part of that paragraph says: "You cannot disable these features for specified IP addresses, specified Firebox interfaces, or different time periods." Which made me think trusted and optional interfaces should…
-
I just discovered that the global setting, "Enable configuration of policies for traffic generated by the Firebox" has some influence to the source ip for wg-logging, at least on two of my T35s. Enabled -> Use the IP from the external interface (Traffic not getting to log server at remote site) Disabled -> Use a Private IP…
-
Thanks for getting back to me Bruce VLAN2 10.51.0.1/24 VLAN60 10.51.60.1/24 Log server is 192.168.41.55 (connected via BOVPN) with a route of 192.168.41.0/24 <-> 10.51.0.0/16 The management VLAN currently has a couple switches and an AP. Currently the source IP for wg-logging is the IP of the external interface. I have no…
-
Thanks for the responses. It sounds like I will need to keep the QoS feature turned on from the global settings. I now see under the advanced interface settings the option to prioritize traffic based on QoS. I have left the marking method set to preserve. The office with the XTM 25 is sending all voice traffic to our main…