Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dual WAN, replies leave via incorrect interface

Hello, I am running XG 17.5 and I set up DNAT rule for packets coming to secondary WAN. It works, except case where source address is from WAN1 subnet. Replies to these packets are NATed correctly to WAN2 address, but are routed out via WAN1 interface instead of WAN2.

Is it a bug or expected behavior and is there a way to fix it?

 

Example: XG WAN1 address is 1.1.1.1, WAN2 address is 2.2.2.2. DNAT rule 2.2.2.2 to 192.168.1.50

packet is src 1.1.1.5, dst 2.2.2.2. Reply is src 2.2.2.2 dst 1.1.1.5, but it leaves XG on WAN1 interface, instead of WAN2.

 



This thread was automatically locked due to age.
Parents
  • I am attaching tcpdump capture to make it more clear. Problem is, that packet arrives on Port4, but reply leaves on Port2 with address of Port4

     

    18:57:54.312962 Port4, IN: IP 1.1.1.5.58206 > 2.2.2.2.500: isakmp: parent_sa ikev2_init
    18:57:54.313435 Port1.26, OUT: IP 1.1.1.5.58206 > 192.168.1.50.500: isakmp: parent_sa ikev2_init

    18:57:54.314053 Port1.26, IN: IP 192.168.1.50.500 > 1.1.1.5.58206: isakmp: parent_sa ikev2_init[]
    18:57:54.314480 Port2, OUT: IP 2.2.2.2.500 > 1.1.1.5.58206: isakmp: parent_sa ikev2_init[]

     

    Here is example of working connection, where source (5.5.5.5) is not in XG routing table.

     

    20:29:17.155236 Port4, IN: IP 5.5.5.5.54196 > 2.2.2.2.500: isakmp: parent_sa ikev2_init
    20:29:17.157140 Port1.26, OUT: IP 5.5.5.5.54196 > 192.168.1.50.500: isakmp: parent_sa ikev2_init

    20:29:17.212375 Port1.26, IN: IP 192.168.1.50.500 > 5.5.5.5.54196: isakmp: parent_sa ikev2_init[]
    20:29:17.213311 Port4, OUT: IP 2.2.2.2.500 > 5.5.5.5.54196: isakmp: parent_sa ikev2_init[]

Reply
  • I am attaching tcpdump capture to make it more clear. Problem is, that packet arrives on Port4, but reply leaves on Port2 with address of Port4

     

    18:57:54.312962 Port4, IN: IP 1.1.1.5.58206 > 2.2.2.2.500: isakmp: parent_sa ikev2_init
    18:57:54.313435 Port1.26, OUT: IP 1.1.1.5.58206 > 192.168.1.50.500: isakmp: parent_sa ikev2_init

    18:57:54.314053 Port1.26, IN: IP 192.168.1.50.500 > 1.1.1.5.58206: isakmp: parent_sa ikev2_init[]
    18:57:54.314480 Port2, OUT: IP 2.2.2.2.500 > 1.1.1.5.58206: isakmp: parent_sa ikev2_init[]

     

    Here is example of working connection, where source (5.5.5.5) is not in XG routing table.

     

    20:29:17.155236 Port4, IN: IP 5.5.5.5.54196 > 2.2.2.2.500: isakmp: parent_sa ikev2_init
    20:29:17.157140 Port1.26, OUT: IP 5.5.5.5.54196 > 192.168.1.50.500: isakmp: parent_sa ikev2_init

    20:29:17.212375 Port1.26, IN: IP 192.168.1.50.500 > 5.5.5.5.54196: isakmp: parent_sa ikev2_init[]
    20:29:17.213311 Port4, OUT: IP 2.2.2.2.500 > 5.5.5.5.54196: isakmp: parent_sa ikev2_init[]

Children