You may also need to add modprobe tun
to the top of your tinc-up. I also found that I needed to add the default route for the bridge interface. here is my tinc-up, perhaps it may help you. this is on Ubuntu don...@donaldtincvm:/etc/tinc/vpn$ cat tinc-up #!/bin/sh modprobe tun ifconfig vpn 0.0.0.0 ifconfig vpn up ifconfig eth0 0.0.0.0 ifconfig eth0 up brctl addbr bridge brctl addif bridge vpn brctl addif bridge eth0 ifconfig bridge 192.168.2.11 netmask 255.255.0.0 route add default gw 192.168.2.1 bridge ifconfig bridge up On Thu, Feb 11, 2010 at 5:00 AM, Guus Sliepen <[email protected]> wrote: > On Thu, Feb 11, 2010 at 10:55:33AM +0100, Ramses II wrote: > > > Both Tinc Server starts and both connects but it tell me the next error > when > > I try to execute the tinc-up script: > > > > r...@vpn-01:/etc/tinc# ./tinc-up > > ifconfig: SIOCSIFADDR: No such device > > interface vpn does not exist! > > ifconfig: SIOCGIFFLAGS: No such device > > r...@vpn-01:/etc/tinc# > > > > The tinc-up script contain this: > > > > #!/bin/sh > > > > ifconfig vpn 0.0.0.0 > > brctl addif br-lan vpn > > ifconfig vpn up > > Your virtual network interface may have another name than "vpn". Replace > vpn > with $INTERFACE in the scripts, so that it will automatically use the right > name. I'll update the example. > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen <[email protected]> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAktz1SIACgkQAxLow12M2nsFtgCfb3bXv+y2Ll3YfExGtG0u2m+V > GdQAniVHgw7KtkLSf6DXXZr+1iOhZN3z > =lnt6 > -----END PGP SIGNATURE----- > > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
