What/why this event happens: Can't write to Linux tun/tap device (tun mode) /dev/net/tun: Input/output error

Bright Zhao startryst at gmail.com
Fri May 26 03:33:35 CEST 2017


Should I change to this in order to avoid the issue?

0 * * * * echo Subnet = 54.169.128.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp
0 * * * * echo Subnet = 54.169.0.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp
1 * * * * /usr/sbin/tincd -n myvpn -k
2 * * * * /usr/sbin/tincd -n myvpn --debug=3

30 * * * * sed -i '/54.169.128.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp
30 * * * * sed -i '/54.169.0.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp
31 * * * * /usr/sbin/tincd -n myvpn -k
32 * * * * /usr/sbin/tincd -n myvpn --debug=3


> On 26 May 2017, at 9:30 AM, Bright Zhao <startryst at gmail.com> wrote:
> 
> Hi, All
> 
> Due to some routing rotation purpose, I use crontab to add below info:
> 
> 0 * * * * echo Subnet = 54.169.128.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp
> 0 * * * * echo Subnet = 54.169.0.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp
> 1 * * * * /usr/sbin/tincd -n myvpn -k
> 1 * * * * /usr/sbin/tincd -n myvpn --debug=3
> 
> 30 * * * * sed -i '/54.169.128.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp
> 30 * * * * sed -i '/54.169.0.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp
> 31 * * * * /usr/sbin/tincd -n myvpn -k
> 31 * * * * /usr/sbin/tincd -n myvpn --debug=3
> 
> 
> But after it get runs, the tinc log shows everything fine, but some how it get below error message, is it an accidental error, or is there anything wrong?
> 
> Can't write to Linux tun/tap device (tun mode) /dev/net/tun: Input/output error
> 
> 
> 



More information about the tinc mailing list