Joss
2004-06-23 10:52:52 UTC
Problem is that the Sonicwall (SOHO3) freezes/hangs within minutes of being
rebooted.
Configuration is ADSL router with static WAN IP *.*.*.9. No port forwarding.
No firewall/filter active.
Sonicwall configured to perform NAT, has WAN IP *.*.*.11 (255.255.255.248),
LAN IP 192.168.*.110.
Two PCs on LAN connect to Sonicwall by switch. IPs are 192.168.*.10 and 11.
Manually configured. No DHCP on router or Sonicwall. Firmware is 6.6.0.2
(latest)(could be the problem?!). The unit was being used in our main office
but has been replaced with a TZ170 and moved to a remote unit where it is
supposed to provide site to site VPN. It was working faultlessly before,
though I have not had the opportunity to take it back to the old office and
retry it there.
After rebooting the Sonicwall, all works as it should. Internet browsing,
site to site VPN and access to Sonicwall by GlobalVPN. After several minutes
(between 1 and 20 approx.), the Sonicwall hangs. It cannot be accessed
through LAN or VPN interfaces. Internet browsing not possible. Lights on
Sonicwall are normal. LAN activity light shows attempts to access Sonicwall.
Only option is to power-off and restart.
Have tried disconnecting LAN side of Sonicwall to rule out problem from LAN.
Removed switch and had one PC connected to LAN side of Sonicwall by
crossover cable.
Disabled site to site VPN.
Ran syslog on PC to check for error message in log immediately before freeze
but found nothing. (Although it may have frozen before the message could get
to the log)
It appears that the problem only occurs when the WANlink is active.
Have tried changing MTU on both Sonicwalls to 1500 (is now 1400) and
changing 'allow fragment'. Originally, it was 1396 (or thereabouts). I'm not
convinced that changing this makes any difference, although wishful thinking
initially led me to believe that it did. Pinging direct to the internet
indicates max MTU of 1500, though maybe packets are getting fragmented at
times? How could I investigate this further?
My gut instinct is that it is some kind of packet or overflow problem. The
config looks solid. Any assistance or ideas would be appreciated.
thanks,
Jo
rebooted.
Configuration is ADSL router with static WAN IP *.*.*.9. No port forwarding.
No firewall/filter active.
Sonicwall configured to perform NAT, has WAN IP *.*.*.11 (255.255.255.248),
LAN IP 192.168.*.110.
Two PCs on LAN connect to Sonicwall by switch. IPs are 192.168.*.10 and 11.
Manually configured. No DHCP on router or Sonicwall. Firmware is 6.6.0.2
(latest)(could be the problem?!). The unit was being used in our main office
but has been replaced with a TZ170 and moved to a remote unit where it is
supposed to provide site to site VPN. It was working faultlessly before,
though I have not had the opportunity to take it back to the old office and
retry it there.
After rebooting the Sonicwall, all works as it should. Internet browsing,
site to site VPN and access to Sonicwall by GlobalVPN. After several minutes
(between 1 and 20 approx.), the Sonicwall hangs. It cannot be accessed
through LAN or VPN interfaces. Internet browsing not possible. Lights on
Sonicwall are normal. LAN activity light shows attempts to access Sonicwall.
Only option is to power-off and restart.
Have tried disconnecting LAN side of Sonicwall to rule out problem from LAN.
Removed switch and had one PC connected to LAN side of Sonicwall by
crossover cable.
Disabled site to site VPN.
Ran syslog on PC to check for error message in log immediately before freeze
but found nothing. (Although it may have frozen before the message could get
to the log)
It appears that the problem only occurs when the WANlink is active.
Have tried changing MTU on both Sonicwalls to 1500 (is now 1400) and
changing 'allow fragment'. Originally, it was 1396 (or thereabouts). I'm not
convinced that changing this makes any difference, although wishful thinking
initially led me to believe that it did. Pinging direct to the internet
indicates max MTU of 1500, though maybe packets are getting fragmented at
times? How could I investigate this further?
My gut instinct is that it is some kind of packet or overflow problem. The
config looks solid. Any assistance or ideas would be appreciated.
thanks,
Jo