Metadata socket and net2str() error

Internal Affaires internalaffaires at hotmail.com
Sun Jul 7 22:40:45 CEST 2002


Hello there,

I was hoping that maybe one of you guys could help me out with a problem I'm
experiencing with tinc1.0pre7.

First, I'll start with my configuration, after that I'll explain my problem.

Background
----------
This is a simple, client-server situation on a private network. Both
machines run the same Debian Woody 3.0 testing installation and both have
identical packages (deb files) installed for the kernel, tinc and related
stuff.


As the info below will show, "iwan" is the name of this vpn. On both
machines this net is automatically started through init.d.

Server (Debian Woody)
---------------------
    uname -a: Linux Server 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002
i586 unknown
    eth0: 217.x.x.22 (not relevant in this situation)
    eth1: 192.168.0.1/24
    tap0: 10.0.0.1/16 (vpn device)
    /etc/tinc/iwan/tinc.conf:
        Name = Server
        Device = /dev/tap0
        PrivateKeyFile = /etc/tinc/iwan/rsa_key.priv
        Interface = vpn
    /etc/tinc/iwan/tinc-up:
        #!/bin/sh
        ifconfig tap0 hw ether fe:fd:0:0:0:0
        ifconfig tap0 10.0.0.1 netmask 255.255.0.0
        ifconfig tap0 -arp
    /etc/tinc/iwan/hosts/Server: (on both machines)
        -----BEGIN RSA PUBLIC KEY-----
        ...
        -----END RSA PUBLIC KEY-----
        #Address = 217.x.x.22
        Address = 192.168.0.1
        Subnet = 10.0.0.0/16

Client (Debian Woody)
---------------------
    uname -a: Linux client 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002
i586 unknown
    eth0: 192.168.0.9/24
    tap0: 10.0.0.3/16 (vpn device)
    /etc/tinc/iwan/tinc.conf:
        ConnectTo = Server
        Name = Client
        Device = /dev/tap0
        PrivateKeyFile = /etc/tinc/iwan/rsa_key.priv
        Interface = vpn
    /etc/tinc/iwan/tinc-up:
        #!/bin/sh
        ifconfig tap0 hw ether fe:fd:0:0:0:0
        ifconfig tap0 10.0.0.3 netmask 255.255.0.0
        ifconfig tap0 -arp
    /etc/tinc/iwan/hosts/Client: (on both machines)
        -----BEGIN RSA PUBLIC KEY-----
        ...
        -----END RSA PUBLIC KEY-----
        Address = 192.168.0.9
        Subnet = 10.0.0.0/16

General
-------
For both machines I have added the following to /etc/modules:
    netlink_dev
    ethertap
and the following to /etc/modules.conf:
    alias char-major-36 netlink_dev
    alias tap0 ethertap
    options tap0 -o tap0 unit=0
    alias tap1 ethertap
    options tap1 -o tap1 unit=1

(No details, except for the public keys and my external IP, have been
*intentionally* ;) left out.)

Problem
-------
Suffice it to say that I cannot ping across the vpn. Pinging the regular eth
devices of either host works perfectly and pinging the respective local tap0
device works fine too, but pinging across the vpn doesn't.

Logs
----
It varies a bit, but on both the server and client I get this in the syslog:
(i.e., no other errors)

Jul  7 20:46:17 Client tinc.iwan[202]: tincd 1.0pre7 starting
Jul  7 20:46:17 Client tinc.iwan[202]: /dev/tap0 is a Linux ethertap device
Jul  7 20:46:18 Client tinc.iwan[202]: Ready
Jul  7 20:47:10 Client tinc.iwan[202]: Got fatal signal 11 (Segmentation
fault)
Jul  7 20:47:10 Client tinc.iwan[202]: Trying to re-execute in 5 seconds...
Jul  7 20:47:15 Client tinc.iwan[221]: tincd 1.0pre7 starting
Jul  7 20:47:15 Client tinc.iwan[221]: /dev/tap0 is a Linux ethertap device
Jul  7 20:47:15 Client tinc.iwan[221]: Ready
Jul  7 20:49:46 Client tinc.iwan[242]: Metadata socket error for Server
(192.168.0.1 port 655): Connection reset by peer

and:

Jul  7 20:47:10 Server tinc.iwan[909]: Metadata socket error for Client
(192.168.0.9 port 1025): Connection reset by peer
Jul  7 20:49:46 Server tinc.iwan[909]: net2str() was called with unknown
subnet type 134621912, exitting!

The errors about the metadata and net2str() are the most common ones.

Attempts
--------
I have attempted to leave out the subnet definitions in each of the host
files (on both machines), but that didn't help. Also, using "192.168.0.0/24"
as the subnet didn't work either. (You might say "of course not", but at
that point I was willing to try everything.) And of course I have Read The
Fine Manual as well as the examples section on the website over and over.

Conlusion
---------
I hope I have provided enough details... Any help would be greatly
appreciated, because I'm all out of 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