ZyWALL 110 Crash by routing traces

PeterUK
PeterUK Posts: 2,704  Guru Member
First Anniversary 10 Comments Friend Collector First Answer
edited April 2021 in Security
V4.62 have a Diagnostics Collect if needed.

So I was troubleshooting why my setup for DNS over VPN to local site to site was not working which too is a bug and then the crash happened!  

I have a USG40 and Zywall 110 setup with local site to site and VPN server on the USG40

USG40 LAN1 VLAN6 IP 192.168.255.243
VPN server role IP range 192.168.145.0/24
TuneltoZyWALL110v2
site to site local policy 192.168.145.0/24 remote policy 192.168.138.0/28


Zywall 110 LAN1 IP 192.168.255.202
TuneltoUSG40v2
site to site local policy 192.168.138.0/28 remote policy 192.168.145.0/24 

with a routing rule:
incoming = Tunnel
member = TuneltoUSG40v2
service = DNS_UDP
next hop
type = interface 
interface =  lan2
source network address translation = outgoing-interface

When a client connects to the VPN and gets IP 192.168.145.1 it does DNS to 192.168.138.2 which the setup should work and did work on a older firmware I set it up on. But if you run a  routing traces  for host 192.168.145.1 and do a nslookup on the client it crashes the Zywall 110. 

Comments

  • PeterUK
    PeterUK Posts: 2,704  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    So after tracking down the DNS problem I am no longer able to Crash the Zywall still have the Diagnostics Collect after a reboot if that helps.

    My DNS over VPN problem was down to a removed rule and I should of spotted that sooner the tunnel shows as up but the USG40 was missing a VLAN6 to ZyWALL service ESP. 

Security Highlight