ZyWALL 110 Crash by routing traces
Options
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
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.
0
Comments
-
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.0
Categories
- All Categories
- 393 Beta Program
- 2.1K Nebula
- 116 Nebula Ideas
- 78 Nebula Status and Incidents
- 5.1K Security
- 51 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 70 Switch Ideas
- 906 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 210 Service & License
- 332 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 880 Nebula FAQ
- 415 Security FAQ
- 220 Switch FAQ
- 195 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 63 Security Highlight