[Vtun-Users] vtund stops working
Status: Inactive
Brought to you by:
mtbishop
From: Tom D. <to...@ip...> - 2003-06-18 11:30:22
|
hello list I've got a wierd problem with vtun, maybe someone can give me a hint :p vtund suddenly stops working for an unknown reason. I have 2 machines , A and B looks like this for the client A : fw# ps aux | grep vtund root 494 0.0 0.2 1868 96 ?? Is 27Apr03 0:00.01 vtund: waiting for connections on port 5000 (vtund) root 62780 0.0 1.6 2384 960 ?? S< Thu02PM 8:04.98 vtund: lyon tun tun1 (vtund) root 76557 0.0 1.9 2448 1172 ?? I<s Tue12PM 84:43.47 vtund: tom tun tun2 (vtund) fw# ifconfig tun2 tun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 inet6 fe80::200:e8ff:feee:c2ce%tun2 prefixlen 64 scopeid 0x7 inet 192.168.1.1 --> 10.0.2.1 netmask 0xffffff00 Opened by PID 76557 fw# sockstat -4cl | grep 5000 root vtund 76557 4 tcp4 193.251.xx.xx:4200 81.49.xx.xx:5000 root vtund 62780 5 tcp4 193.251.xx.xx:5000 212.180.xx.xx:52810 root vtund 494 4 tcp4 *:5000 *:* looks like this for the server B > ps aux | grep vtund root 261 0.0 0.4 2704 1016 ?? S<s 9:20PM 0:00.25 vtund: poleymieux tun tun2 (vtund) root 263 0.0 0.3 2124 836 ?? Is 9:20PM 0:00.00 vtund: waiting for connections on port 5000 (vtund) > ifconfig tun1 tun1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 inet 10.0.2.1 --> 192.168.1.1 netmask 0xff000000 > sockstat -4cl | grep 5000 root vtund 263 4 tcp4 *:5000 *:* root vtund 261 4 tcp4 81.49.xx.xx:1039 213.245.xx.xx:5000 what i dont get is : why does the client think he is still connected when he in fact isn't ? if i dont kill 76557 on the client and restart vtund, my VPN will no longer work. both clients are running freebsd version 4.8-STABLE , but the client is running version 2.5 . server is running version 2.6 No IP's have been changed. Thanks , Tom |