Questions about multiple Tinc daemons

Denny Fox dennyf at microtime.sbwireless.net
Fri Dec 27 03:10:15 CET 2002


Ok, I was not starting tincd with the -n parameter. I have fixed that
in my /etc/init.d/tinc script. I did a symlink from /usr/local/etc to
/etc and /usr/local/var to /var to fix the path issues with the static
version. Now I'm getting /var/run/tinc.<network>.pid type pid files,
one for each vpn, like you describe.

Thanks for the tip!

I'm using port 655 for tap0 and 656 for tap1. The two vpns start and
stop cleanly now.

Now, another question.

Is it proper to use the same network number for tap0 and tap1 in the
/etc/tinc/{network}/tinc-up scripts?

for vpn1 in tinc-up:
#!/bin/sh
ifconfig tap0 hw ether fe:fd:0:0:0:0
ifconfig tap0 192.168.1.250 netmask 255.255.0.0
ifconfig tap0 mtu 1400
ifconfig tap0 -arp

for vpn2 in tinc-up
#!/bin/sh
ifconfig tap1 hw ether fe:fd:0:0:0:0
ifconfig tap1 192.168.1.250 netmask 255.255.0.0
ifconfig tap1 mtu 1400
ifconfig tap1 -arp

The tap0 connection works, but the tap1 connection won't ping, even
though it says its connected. No firewall blocking errors.

Thanks,

Denny

>
> Hmm, there should be a /var/run/tinc.<network>.pid (or something.
> Definately not in /usr/local/var.)  Did you start tincd with -n
> <network>?  (Might be an error in the init script...)
>
>
> 	Ivo
>

Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://tinc.nl.linux.org/




More information about the Tinc mailing list