thr3ads.net - tinc - Connection established, but no data transfer... [Jan 2002]

If this information is useful, please help other people find it:
Share via:

Gerard W. Patterson

2002-Jan-18 19:26 UTC

Connection established, but no data transfer...

Hello!

I am attempting to get tinc running between two machines and would
appreciate any guidance one could lend.  I have read through all of the
documentation and feel that I am close but missing something silly.


First Machine: (gerry)

$tincd --version
tinc version 1.0-cvs (built Jan 17 2002 16:13:13, protocol 11)
Copyright (C) 1998-2001 Ivo Timmermans, Guus Sliepen and others.
See the AUTHORS file for a complete list.

tinc comes with ABSOLUTELY NO WARRANTY.  This is free software,
and you are welcome to redistribute it under certain conditions;
see the file COPYING for details.


This is tinc-pre5 compiled from CVS, with the --kernel-source pointed at my
kerenl source.


$uname -a
Linux gerry 2.4.16-win4lin+xfs #1 Thu Dec 13 14:36:06 MST 2001 i686 unknown

$ifconfig
eth0      Link encap:Ethernet  HWaddr 00:01:03:D2:85:CC  
          inet addr:10.89.4.25  Bcast:10.89.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25007 errors:0 dropped:0 overruns:1 frame:0
          TX packets:4426 errors:0 dropped:0 overruns:0 carrier:121
          collisions:3 txqueuelen:100 
          RX bytes:6136607 (5.8 Mb)  TX bytes:530890 (518.4 Kb)
          Interrupt:9 Base address:0xd000 

eth1      Link encap:Ethernet  HWaddr 00:04:75:83:6B:5F  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19341 errors:0 dropped:0 overruns:0 frame:0
          TX packets:331 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:4752576 (4.5 Mb)  TX bytes:47554 (46.4 Kb)
          Interrupt:9 Base address:0xb400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:222 errors:0 dropped:0 overruns:0 frame:0
          TX packets:222 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:37640 (36.7 Kb)  TX bytes:37640 (36.7 Kb)

testvpn   Link encap:Ethernet  HWaddr FE:FD:00:00:00:00  
          inet addr:10.89.4.25  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:211 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:20678 (20.1 Kb)

$route -n 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.1.30.0       0.0.0.0         255.255.255.255 UH    0      0        0 eth0
10.89.2.126     0.0.0.0         255.255.255.255 UH    0      0        0 testvpn
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.89.0.0       0.0.0.0         255.255.0.0     U     0      0        0 eth0
10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 testvpn
0.0.0.0         10.89.4.1       0.0.0.0         UG    0      0        0 eth0

$cat /etc/tinc/testvpn/tinc.conf
Name=gerry
PrivateKeyFile=/etc/tinc/testvpn/rsa_key.priv
TapDevice=/devfs/misc/net/tun

$cat /etc/tinc/testvpn/tinc-up
#!/bin/sh
ifconfig $NETNAME hw ether fe:fd:00:00:00:00
ifconfig $NETNAME 10.89.4.25 netmask 255.0.0.0
ifconfig $NETNAME -arp

$cat /etc/tinc/testvpn/hosts/gerry
Address=192.168.1.1
Subnet=10.89.4.0/24
-----BEGIN RSA PUBLIC KEY-----
...(omitted)
-----END RSA PUBLIC KEY-----

$cat /etc/tinc/testvpn/hosts/penguin26
Address=192.168.1.2
Subnet=10.89.2.0/24
-----BEGIN RSA PUBLIC KEY-----
...(omitted)
-----END RSA PUBLIC KEY-----

Second Machine: (penguin26)
$uname -a Linux penguin126.computalog.com 2.2.18-5cmdksmp #1 SMP Thu Mar 8
14:14:46 MST 2001 i686 unknown

$ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:01:03:BC:2B:92  
          inet addr:10.89.2.126  Bcast:10.89.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:338992 errors:0 dropped:0 overruns:1 frame:0
          TX packets:15682 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0xec00 

eth1      Link encap:Ethernet  HWaddr 00:50:DA:B4:59:EE  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:79667 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6118 errors:0 dropped:0 overruns:0 carrier:2347
          collisions:0 txqueuelen:100 
          Interrupt:5 Base address:0xe080 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:4664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4664 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

tap0      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00  
          inet addr:10.89.2.126  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING NOARP PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:308 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58737 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          Interrupt:5 

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.89.4.25      0.0.0.0         255.255.255.255 UH    0      0        0 tap0
10.89.2.126     0.0.0.0         255.255.255.255 UH    0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 tap0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 eth0

$ cat /etc/tinc/testvpn/tinc.conf 
Name = penguin26
ConnectTo = gerry
TapDevice = /dev/tap0
PrivateKeyFile = /etc/tinc/testvpn/rsa_key.priv

The host files are the same on this machine.

When I try to ping from the first machine (gerry) to the second machine
(penguin26) I get this in the log files from (gerry)
Jan 18 10:52:42 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:43 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:43 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:44 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:44 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:45 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:45 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:46 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:46 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:47 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:47 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:48 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:48 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:49 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:49 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:50 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:50 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:51 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device
Jan 18 10:52:51 gerry tinc.testvpn[1597]: Sending packet of 98 bytes to
penguin26 (192.168.1.2)
Jan 18 10:52:52 gerry tinc.testvpn[1597]: Read packet of 98 bytes from Linux
tun/tap device

When I do a tcpdump on testvpn (the tun device) I can see the echo requests (no
echo replys though!!)

When I do a tcpdump on eth1 I can see upd packets on the proper port leaving as
well.


On the other system (penguin26) I see nothing really happening in the logs:
Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: tincd 1.0-cvs (Jan 17 2002
16:41:42) starting, debug level 10
Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: /dev/tap0 is a Linux ethertap
device
Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: Executing script tinc-up
Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: Ready: listening on port 655
Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Trying to connect to gerry
(192.168.1.1)
Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Connected to 192.168.1.1 port
655
Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Connection with gerry
(192.168.1.1) activated
Jan 18 10:51:23 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:51:30 penguin126 last message repeated 5 times
Jan 18 10:53:48 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:53:53 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:54:01 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:54:06 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:54:10 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 10:54:45 penguin126 last message repeated 5 times
Jan 18 10:55:00 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 11:00:00 penguin126 last message repeated 7 times
Jan 18 11:05:00 penguin126 last message repeated 4 times
Jan 18 11:07:03 penguin126 last message repeated 4 times
Jan 18 11:07:38 penguin126 last message repeated 3 times
Jan 18 11:10:01 penguin126 tinc.testvpn[27958]: Cannot route packet: unknown
type ffbf
Jan 18 11:10:03 penguin126 last message repeated 3 times


So my question is what is the: "Cannot route packet: unknown type
ffbf"
error message about?

I hope I have provided enough information (I know I stated the hostname as
penguin26 for the config file but the actual hostname is penguin126, but
that should be ok.)

Any help would be greatly appreciated.

Regards,

  Gerry


-- 
Gerard W. Patterson, B.Sc           |   Computalog Wireline Services
Software Engineering                |   Precision Drilling TSG, Inc.
<gerry.patterson@computalog.com>    |   
Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://tinc.nl.linux.org/

Guus Sliepen

2002-Jan-19 18:38 UTC

head link

Connection established, but no data transfer...

On Fri, Jan 18, 2002 at 11:26:47AM -0700, Gerard W. Patterson wrote:
> I am attempting to get tinc running between two machines and would
> appreciate any guidance one could lend.  I have read through all of the
> documentation and feel that I am close but missing something silly.
[...]> So my question is what is the: "Cannot route packet: unknown type
ffbf"
> error message about?
It means it got a packet from the ethertap device which doesn't have
ipv4, ipv6 or arp for its Ethernet type. This means either tinc thinks
it's an ethertap device while in fact it's another kind of device, or
something is wrong in device.c from CVS. I'll check that out and mail
you if I fixed it or if there's another problem.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus@sliepen.warande.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :
http://brouwer.uvt.nl/pipermail/tinc/attachments/20020119/baa4def3/attachment.pgp

Guus Sliepen

2002-Jan-20 16:26 UTC

head link

Connection established, but no data transfer...

On Fri, Jan 18, 2002 at 11:26:47AM -0700, Gerard W. Patterson wrote:
> Second Machine: (penguin26)
> $uname -a Linux penguin126.computalog.com 2.2.18-5cmdksmp #1 SMP Thu Mar 8
14:14:46 MST 2001 i686 unknown
[...]> tap0      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00  
>           inet addr:10.89.2.126  Bcast:10.255.255.255  Mask:255.0.0.0
>           UP BROADCAST RUNNING NOARP PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:308 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:58737 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           Interrupt:5 
Why is tap0 in promiscuous mode?
> On the other system (penguin26) I see nothing really happening in the logs:
> Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: tincd 1.0-cvs (Jan 17 2002
16:41:42) starting, debug level 10
> Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: /dev/tap0 is a Linux
ethertap device
> Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: Executing script tinc-up
> Jan 18 10:51:06 penguin126 tinc.testvpn[27958]: Ready: listening on port
655
> Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Trying to connect to gerry
(192.168.1.1)
> Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Connected to 192.168.1.1
port 655
> Jan 18 10:51:11 penguin126 tinc.testvpn[27958]: Connection with gerry
(192.168.1.1) activated
> Jan 18 10:51:23 penguin126 tinc.testvpn[27958]: Cannot route packet:
unknown type ffbf
> Jan 18 10:51:30 penguin126 last message repeated 5 times[...]

It looks like syslog didn't log all messages to the log you cut&pasted.
Check /etc/syslog.conf and make sure *.* is logged to a file. Some
distributions let syslog split up the log messages by severity and write
them to different files, very annoying.
> I hope I have provided enough information (I know I stated the hostname as
> penguin26 for the config file but the actual hostname is penguin126, but
> that should be ok.)
Could you also show me the logs of the first machine at the moment tincd
starts?

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus@sliepen.warande.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :
http://brouwer.uvt.nl/pipermail/tinc/attachments/20020120/7da636bd/attachment.pgp

Maybe Matching Threads

Search for more maybe matching threads

tinc - Jan 2002 - Connection established, but no data transfer...

Connection established, but no data transfer...

Connection established, but no data transfer...

Connection established, but no data transfer...

Maybe Matching Threads