OpenWrt Forum Archive

Topic: VTUN on Kamikaze

The content of this topic has been archived on 4 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I am testing OpenWRT Kamikaze on the Meraki router, and are trying to get the VTUN/TUN ipkg package working.
Are there any known "issues" using VTUN on MIPS / OpenWRT ?

I have turned off compression, encryption and configured an simple tcp VPN against an (working) version 2.6 VTUN server on an Debian Sarge host, but the Meraki/VTUN refuse to open up the link... If I try to connect from another Debian sarge installation to the same host, it just works....?

Clues are very welcome! smile

When the Meraki connects, the connection is teared down right away, and the only thing I get in the logs are:
2007-03-26 23:09:40    Daemon.Info 192.168.1.1 vtund[2520]: Use SSL-aware challenge/response
2007-03-26 23:09:41    Daemon.Info 192.168.1.1 vtund[2520]: Session gateway1 [192.168.1.100:3676] opened
2007-03-26 23:09:41    Daemon.Info 192.168.1.1 vtund[2520]: Session gateway1 closed

Using the following vtund.conf on the HOST: started with vtund -s -f /etc/vtund.conf
options {
        port 51010;
        timeout 30;
        ifconfig /sbin/ifconfig;
        route /sbin/route;
        ip /sbin/ip;
        }

default {
        speed 0;
        encr no;
        proto tcp;
        type tun;
        keepalive yes;
        multi killold;
        persist yes;
        }

gateway1 {
up {
        ifconfig "%% 172.16.1.2 pointopoint 172.16.1.1 mtu 1450";
};
down {
        ifconfig "%% down";
};
}


And on the client:  started with vtund -f /etc/vtund.conf gateway1 192.168.1.1
options {
        port 51010;
        timeout 30;
        ifconfig /sbin/ifconfig;
        route /sbin/route;
        ip /sbin/ip;
        }

default {
        speed 0;
        encr no;
        proto tcp;
        type tun;
        keepalive yes;
        multi killold;
        persist yes;
        }

gateway1 {
up {
        ifconfig "%% 172.16.1.1 pointopoint 172.16.1.2 mtu 1450";
};
down {
        ifconfig "%% down";
};
}

Ahh, solved mý own problem:

2007-03-26 23:57:58    Daemon.Error    192.168.1.100    Jan  4 23:41:49 vtund[3462]: Can't allocate tun device . No such file or directory(2)<000>

And that was fixed by, on the Meraki board:
mkdir /dev/net
mknod /dev/net/tun c 10 200

Perhaps the tun ipkg package should create this device when installed in an upcomming release? smile

xyz123 wrote:

Perhaps the tun ipkg package should create this device when installed in an upcomming release? smile

Oddly enough, I have always seen this working, and I've always seen this device, in both WR and KK.  Are you still seeing it?

The discussion might have continued from here.