permission bug

Got a problem with Viscosity or need help? Ask here!

xuwenhui

Posts: 1
Joined: Wed Dec 02, 2009 3:43 pm

Post by xuwenhui » Wed Dec 02, 2009 9:15 pm
Connect VPN server can not ping to the IP obtained from the server
Code: Select all
Wed Dec  2 17:48:36 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Dec  2 17:48:36 2009: LZO compression initialized
Wed Dec  2 17:48:36 2009: Attempting to establish TCP connection with xxx.xxx.xxx.xxx:443 [nonblock]
Wed Dec  2 17:48:37 2009: TCP connection established with xxx.xxx.xxx.xxx:443
Wed Dec  2 17:48:37 2009: TCPv4_CLIENT link local: [undef]
Wed Dec  2 17:48:37 2009: TCPv4_CLIENT link remote: xxx.xxx.xxx.xxx:443
Wed Dec  2 17:48:43 2009: [server] Peer Connection Initiated with xxx.xxx.xxx.xxx:443
Wed Dec  2 17:48:46 2009: TUN/TAP device /dev/tun0 opened
Wed Dec  2 17:48:46 2009: /sbin/ifconfig tun0 delete
Wed Dec  2 17:48:46 2009: NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
Wed Dec  2 17:48:46 2009: /sbin/ifconfig tun0 10.10.10.10 10.10.10.9 mtu 1500 netmask 255.255.255.255 up
Wed Dec  2 17:48:46 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1544 10.10.10.10 10.10.10.9 init
Wed Dec  2 17:48:46 2009: WARNING: potential route subnet conflict between local LAN [10.10.10.0/255.255.255.0] and remote VPN [10.10.10.0/255.255.255.0]
Wed Dec  2 17:48:46 2009: Initialization Sequence Completed
About 5 minutes or so, the program will find ping unreasonable, re-connect, the log is as follows;
Code: Select all
Wed Dec  2 17:54:45 2009: [server] Inactivity timeout (--ping-restart), restarting
Wed Dec  2 17:54:45 2009: /Applications/Viscosity.app/Contents/Resources/dnsdown.py tun0 1500 1544 10.10.10.10 10.10.10.9 restart
Wed Dec  2 17:54:45 2009: SIGUSR1[soft,ping-restart] received, process restarting
Wed Dec  2 17:54:45 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Dec  2 17:54:45 2009: Re-using SSL/TLS context
Wed Dec  2 17:54:45 2009: LZO compression initialized
Wed Dec  2 17:54:45 2009: Attempting to establish TCP connection with xxx.xxx.xxx.xxx:443 [nonblock]
Wed Dec  2 17:54:46 2009: TCP connection established with xxx.xxx.xxx.xxx:443
Wed Dec  2 17:54:46 2009: TCPv4_CLIENT link local: [undef]
Wed Dec  2 17:54:46 2009: TCPv4_CLIENT link remote: xxx.xxx.xxx.xxx:443
Wed Dec  2 17:54:51 2009: [server] Peer Connection Initiated with xxx.xxx.xxx.xxx:443
Wed Dec  2 17:54:53 2009: Preserving previous TUN/TAP instance: tun0
Wed Dec  2 17:54:53 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tun0 1500 1544 10.10.10.10 10.10.10.9 restart
Wed Dec  2 17:54:53 2009: Initialization Sequence Completed
At this point the normal communication skills and the server

However, at the first connection, manual execute "sudo /sbin/ifconfig tun0 10.10.10.10 10.10.10.9 mtu 1500 netmask 255.255.255.255 up", server can be a normal communication. If you do not add the prefix "sudo", Will be prompted to permission errors. how to solve? Can execute commands manually every time?

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Dec 07, 2009 7:25 pm
Hi xuwenhui,

This line is what is causing the problem for you:
Code: Select all
WARNING: potential route subnet conflict between local LAN [10.10.10.0/255.255.255.0] and remote VPN [10.10.10.0/255.255.255.0]
Basically the IP range of your local network is the name as your remote VPN network. You can try ticking the "Reset network interfaces on disconnect" option under Preferences->Advanced to see if that resolves the problem for you. Otherwise you're best changing the IP range of either your local network or the remote network to avoid the clash.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1