- When replying to UDP traffic such as SNMP, as a source address the router lets the IP stack determine the "best" routed VLAN interface address.
- This asymmetric behavior can in general lead to at the following undesirable results:
- An intermediate firewall may drop SNMP replies when their source IP address does not match the destination IP address of the original SNMP requests, leading to a perception that the S-Series did not reply at all.
- NetSight 3.x's Client/Server SNMP Redirect feature may not work properly, leading to problems in managing the router from NetSight.
- When replying to TCP traffic such as SSH, as a source address the router uses the original destination address (from the TCP socket binding) - which works fine.