search for: myownvpnip

...eturn 1 } + { MSG="multiple TapDevice entries not allowed!"; return 1; } echo $DEV | grep -q -x -E '/dev/tap[[:digit:]]+' || - { MSG="TapDevice should be in form /dev/tapX!"; return 1 } + { MSG="TapDevice should be in form /dev/tapX!"; return 1; } # MyOwnVPNIP/MyVirtualIP syntax validation [ -z "$VPN" ] && \ - { MSG="MyOwnVPNIP/MyVirtualIP required!"; return 1 } + { MSG="MyOwnVPNIP/MyVirtualIP required!"; return 1; } [ $(echo $VPN | wc -l) -gt 1 ] && \ - { MSG="multiple MyOwnVPNIP/MyVirtualIP...

Hi, Although Im dutch too, Ill write this in english. I got a similar problem then the one on the helpforum. Ill paste my setup first server tincd.conf ---- ListenPort = 8089 MyOwnVPNIP = 192.168.100.1/24 #VpnMask = 255.255.255.0 TapDevice = /dev/tap0 Passphrases=/usr/local/etc/tinc/passphrases server tapdev ---- tap0 Link encap:Ethernet HWaddr FE:FD:C0:A8:6F:01 inet addr:192.168.100.1 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING NOAR...

...ful if you'd subscribe to the tinc developpers mailing list. It's not high volume, but it eases communication. There's a problem with tinc's boot scripts (at least the debian one, but that's fixed now). The netmask of the tap devices should be larger than the one specified with MyOwnVPNIP, because it must accept packets that are destined for other subnets. We have a new directive that goes into tinc.conf, VpnMask. Suppose our TOTAL vpn is 10.1.x.x/16, and our own subnet is 10.1.1.x/24, this should go into tinc.conf: MyOwnVPNIP = 10.1.1.1/24 VpnMask = 255.255.0.0 Ivo asked me to in...

...nnel from machine A to B on two different physical networks, but I can't seem to get there. Just to get things figured out I've got two machines on the same physical network, mach A: 192.168.0.1, mach B: 192.168.0.3. bcast is 192.168.0.255. Machine A /etc/tinc/tinc.conf ListenPort=655 MyOwnVPNIP=10.0.0.1/24 Passphrases=/etc/tinc/passphrases TapDevice=/dev/tap0 VpnMask=255.0.0.0 Machine A ifconfig ifconfig tap0 10.0.0.1 broadcast 10.255.255.255 netmask 255.0.0.0 Machine B /etc/tinc/tinc.conf ConnectTo=192.168.0.1 MyOwnVPNIP=10.0.0.2/24 Passphrases=/etc/tinc/passphrases TapDevice=/d...

...conf" ERROR1=0 ERROR2=0 [ -f $CFG ] || { MSG="$CFG does not exist!"; return 1; } # load TINCD config DEV="$(grep -i -e '^[[:space:]]*TapDevice' $CFG | sed 's/[[:space:]]//g; s/^.*=//g')" VPN="$(grep -i -e '^[[:space:]]*(MyOwnVPNIP|MyVirtualIP)' -E $CFG | sed 's/[[:space:]]//g; s/^.*=//g')" IFM="$(grep -i -e '^[[:space:]]*VPNMask' $CFG | sed 's/[[:space:]]//g; s/^.*=//g')" # TapDevice syntax validation [ -z "$DEV" ] && \ { MSG="TapDevice requi...

...respectively. ConnectPort = 655 # Listen on which port #ListenPort = 655 # Accept incoming connections AllowConnect = no # My own VPN IP # You may use the /nn notation to indicate the number of bits used for # the mask, /8 is equivalent to the netmask 255.0.0.0 (the first 8 # bits are set to 1). MyOwnVPNIP = 192.168.9.99/24 # Directory where tinc will look for passphrases Passphrases = /etc/tinc/passphrases # Which local file? # Default is /dev/tap0 TapDevice = /dev/tap0 # Number of seconds of inactivity tinc will wait before sending a probe # to the other end PingTimeout=120 IndirectData = yes...

G'day, I've just downloaded the tinc-1.0pre3 and compiled it - it seems to work fine. I tried your tinc start script in the redhat directory, first adding the MyOwnVPNIP = 10.1.3.1/16 VpnMask = 255.255.0.0 to my tinc.conf file as suggested. But now when TINC is invoked, tinc exits with the following error. [root@platypus tinc-1.0pre3]# /usr/local/sbin/tincd -n wurley.vpn Failed to read `/usr/local/etc/tinc/wurley.vpn/tinc.conf': No such file or directory [ro...

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

Hello all, I've been playing with tinc to setup a wan between two offices of the company that I work for. I'm partially there but having a slight problem. tinc comes up between the 2 machines (both 2.2.14 debian woody machines), and I can ping from the vpn machine at office a, and get a response from office b. However, if I ping any other machine across the wan I can't get a