|
|
On Fri, 03 Oct 2003 I wrote: > [tunnel down, only restart of TAP driver helps] > > It happened again with beta 8 -- but by examining the routing table > while the tunnel was still down, I think I found it: No, I didn't :( It remained up for 14 hours, and then it was the same again. Cross-referencing with other logs, I spotted something I hadn't noticed before. At approximately the same time as the tunnel was lost, the firewall spontaneously rebooted for some reason (I only noticed because the message sequence numbers restarted from 1, and for some reason the first message, which says it rebooted, was missing - maybe it didn't send that to the syslog machine because the firewall hadn't completed booting yet). Going back in the firewall logs, I noticed that this had happened before, and on at least one of those occasions - but not all - the tunnel was also lost. Checking the system event log, I saw that the physical network adapter went "cable unplugged" for a short while at the same time; not unexpected during the firewall's reboot. This looked like I was on track of something, but trying to recreate the same conditions by physically unplugging the cable on another OpenVPN setup (with identical settings, except for the port number) caused no problems: when I plugged the cable back in a couple of minutes later, the tunnel was re-established. I repeated this a couple of times, leaving it unplugged for different lengths of time, tried to create traffic while it was disconnected etc.: each time the tunnel came back without having to restart anything. Disabling and re-enabling the physical network adapter didn't change anything either: the tunnel comes back each time. Another [brand & type of] firewall is due to arrive later today or tomorrow. I'm going to replace it and see if it makes a difference. ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |