|
Tunnel config fails on synology
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Tuesday, 11 January 2011 17:25:20
Hi,
I tried to create a tunnel on my DS209 using Synology. Although the page is very instructive and the software installation runs fine the tunnel can not be created by AICCU unless there is already another tunnel defined using the DSM-GUI.
If no tunnel is defined in the gui /var/log/messages shows:
Jan 11 11:11:30 aiccu: [tun-start] Couldn't open device /dev/net/tun: No such device (19)
How can I create this device without starting a non-SIXXS tunnel first?
Thanks in Advance,
Hans
Tunnel config fails on synology
Jan 11 11:11:30 aiccu: [tun-start] Couldn't open device /dev/net/tun: No such device (19)
You need to load the 'tun' module (Tun/Tap driver) first. Then that device will be available and you then AICCU can use it.
Tunnel config fails on synology
Shadow Hawkins on Tuesday, 11 January 2011 20:44:43
Works perfectly, thanks. Should the wiki be updated with this information?
Tunnel config fails on !1Yank(9raspberry pi
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 03 September 2012 19:30:51
Hello, I have arch linux running on a
Tunnel config fails on raspberry pi
Shadow Hawkins on Monday, 03 September 2012 21:21:07
Hello,
I tried to start aiccu on a raspberry pi with arch linux. I get the same error:
[root@alarmpi aiccu]# /usr/sbin/aiccu start
sock_getline() : "200 SixXS TIC Service on nlams04.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/3.2.27-1-ARCH+"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1346698532"
sock_printf() : "starttls"
sock_getline() : "400 This service is not SSL enabled (yet)"
TIC Server does not support TLS but TLS is not required, continuing
sock_printf() : "username xxxxxxx"
sock_getline() : "200 TBO1-SIXXS choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 xxxxxxxxx"
sock_printf() : "authenticate md5 xxxxxxxxxxxxxxxxxx"
sock_getline() : "200 Successfully logged in using md5 as XXXXX (xxxx xxxxx)"
sock_printf() : "tunnel list"
sock_getline() : "201 Listing tunnels"
sock_getline() : "Txxxxx xxxxxxx ayiya dedus01"
sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
sock_printf() : "tunnel show Txxxxxxx"
sock_getline() : "201 Showing tunnel information for Txxxxx"
sock_getline() : "TunnelId: Txxxxxxx"
sock_getline() : "Type: ayiya"
sock_getline() : "IPv6 Endpoint: xxxxxxx"
sock_getline() : "IPv6 POP: xxxxxx"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: xxxxx"
sock_getline() : "POP Id: xxxxxx"
sock_getline() : "IPv4 Endpoint: ayiya"
sock_getline() : "IPv4 POP: xxxxx"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "Password: xxxxxx"
sock_getline() : "Heartbeat_Interval: 60"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for Txxxxx
sock_printf() : "QUIT Better Off Dead"
Tunnel Information for Txxxxxx:
POP Id : dedus01
IPv6 Local : xxxxxxx/64
IPv6 Remote : xxxxxxx/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
[tun-start] Couldn't open device /dev/net/tun: No such device (19)
[root@alarmpi aiccu]# ls -l /dev/net/tun
crw-rw-rw- 1 root root 10, 200 Jan 1 1970 /dev/net/tun
[root@alarmpi aiccu]# lsmod | grep tun
[root@alarmpi aiccu]# lsmod | grep tun
So maybe the tunnel module is already in the kernel? However, aiccu seems to be unable to open the device. Any Idea what I could do?
Thanx!
Thijs
Tunnel config fails on raspberry pi
Check for the following:
bliss:~# cat /var/log/dmesg|grep "tun:"
[ 18.398964] tun: Universal TUN/TAP device driver, 1.6
[ 18.404036] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
or a "dmesg | grep tun:" should reveal that also. If that is there, then you have the module, otherwise you do not.
It can also be that your device minor/major is wrong.... though 10,200 is generally the correct one.
Seems you are running "Linux/3.2.27-1-ARCH+", check if there is either a /boot/config-.... that matches that and check that tun is enabled, eg:
bliss:/boot# cat config-3.2.0-3-amd64 |grep CONFIG_TUN
CONFIG_TUN=m
some kernels compile it as /proc/config or /proc/config.gz thus those are other places to look for it.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 11 January 2011 17:26:01
Posting is only allowed when you are