ethertap device: File descriptor in bad state

Glen BigSexy at empireenterprises.com
Mon Aug 27 23:46:59 CEST 2001


I've been running tincd on several machines without a problem.
I'm now setting up a new intel-type dual-processor machine, with a custom
compiled 2.4.9 linux kernel.

When I start the daemon: tincd -n vpn -dddddddddd
I get the following debug information in in /var/log/messages

	Aug 27 17:26:49 q tinc.vpn[971]: Process 972 (tinc-up) exited with non-zero
status 255
	Aug 27 17:26:49 q tinc.vpn[971]: Ready: listening on port 30001
	Aug 27 17:26:49 q tinc.vpn[971]: Trying to connect to 55.55.55.55
	Aug 27 17:26:49 q tinc.vpn[971]: Connected to 55.55.55.55 port 30001
	Aug 27 17:26:49 q tinc.vpn[971]: Error while reading from ethertap device:
File descriptor in bad state
	Aug 27 17:26:50 q last message repeated 19806 times


If I start tinc with the no detach option: tincd -n vpn -D -dddddddddd
I get this:

	SIOCSIFHWADDR: No such device
	SIOCSIFADDR: No such device
	vpn: unknown interface: No such device
	SIOCSIFNETMASK: No such device
	vpn: unknown interface: No such device

I have tinc configured to use the Universal Tun functionality; it is
installed and running as a module.
(I've also tried with tun compiled into the kernel)

The tinc-up is as follows:

ifconfig $NETNAME hw ether fe:fd:0:0:0:0
ifconfig $NETNAME 10.10.13.1 netmask 255.255.0.0 -arp


Any ideas??


-
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