IPSEC VPN site to site tunel established bewtween 50H and 100H, traffic gets cought on NAT

Options
MitjaS3NEXT
MitjaS3NEXT Posts: 19 image  Freshman Member
First Comment Friend Collector Third Anniversary
in USG FLEX H Series

I have a IPSEC VPN site to site tunel established bewtween 50H and 100H device.
50H - has 192.168.65.0/24
100H - has 192.168.75.0/24 and 192.168.1.0/24
When I try to establish a connection from 50H (192.168.65.102) to for example 192.168.75.23 it gets caught in the NAT rule. (but the NAT rule is intended for WAN to LAN traffic not for IPSEC traffic between site to site subnets)
Why is this happening? What can I do to get clear traffic?
Never got something similar on the legace 50 and 100 devices…

Accepted Solution

  • PeterUK
    PeterUK Posts: 4,502 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    Answer ✓

    This might be caused by NAT rule for External IP set to any ?

All Replies

  • PeterUK
    PeterUK Posts: 4,502 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    Answer ✓

    This might be caused by NAT rule for External IP set to any ?

  • Zyxel_Tina
    Zyxel_Tina Posts: 855 image  Zyxel Employee
    Zyxel Certified Network Administrator - Security Zyxel Certified Network Administrator - Switch 100 Answers 500 Comments

    Hi @MitjaS3NEXT,

    To better understand the issue, could you please provide more information on how you found that the traffic is being caught by the NAT rule? For example, are you seeing this behavior in logs or a specific page? A screenshot of what you are observing would be very helpful for us to clarify the situation.

    Additionally, to further investigate, we would need to review the device configuration. Please help to enable Zyxel Support Access and share your org/site names with us so we can check this in more detail.

    With this information, we will be able to better identify the cause and provide appropriate suggestions.

    Zyxel Tina

  • MitjaS3NEXT
    MitjaS3NEXT Posts: 19 image  Freshman Member
    First Comment Friend Collector Third Anniversary

    @PeterUK question was the solution, we had External IP set to any, which caused that also the VPN traffic got cought in the rules.

Categories

Security Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）