NetBSD Problem Report #6899
Received: (qmail 3044 invoked from network); 28 Jan 1999 11:03:30 -0000
Message-Id: <199901281103.MAA01534@lyssa.owl.de>
Date: Thu, 28 Jan 1999 12:03:20 +0100 (MET)
From: Matthias Scheler <tron@lyssa.owl.de>
Reply-To: tron@lyssa.owl.de
To: gnats-bugs@gnats.netbsd.org
Subject: Sending packets via IPIP interface doesn't work
X-Send-Pr-Version: 3.95
>Number: 6899
>Category: kern
>Synopsis: Sending packets via IPIP interface doesn't work
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 28 03:05:00 +0000 1999
>Closed-Date: Sat Apr 03 08:59:37 +0000 1999
>Last-Modified: Fri Dec 21 18:32:09 +0000 2012
>Originator: Matthias Scheler
>Release: 990125
>Organization:
Matthias Scheler http://home.owl.de/~tron/
>Environment:
System: NetBSD lyssa.owl.de 1.3I NetBSD 1.3I (LYSSA) #1: Mon Jan 25 11:20:08 MET 1999 tron@lyssa.owl.de:/src/sys/compile/LYSSA i386
>Description:
Sinc the IPIP tunneling protocol has been moved to a seperate network
interface sending packets doesn't work any more:
tron@lyssa:~tron#ifconfig ipip0 192.168.1.1 194.123.65.34
tron@lyssa:~tron#ping -c 1 xpb.core.owl.de
PING xpb.core.owl.de (194.123.65.34): 56 data bytes
ping: sendto: Message too long
^C
----xpb.core.owl.de PING Statistics----
1 packets transmitted, 0 packets received, 100.0% packet loss
At this point it should have found a route and setup a valid MTU but
it didn't. So I set the MMU manually:
tron@lyssa:~tron#ifconfig ipip0 mtu 1500
tron@lyssa:~tron#ping -c 1 xpb.core.owl.de
PING xpb.core.owl.de (194.123.65.34): 56 data bytes
----xpb.core.owl.de PING Statistics----
1 packets transmitted, 0 packets received, 100.0% packet loss
If I use "tcpdump" on the router I can see them arriving on the
ethernet interface:
tron@colwyn:~tron#tcpdump -i de0 -s 1500 -xx proto 4
tcpdump: listening on de0
12:00:27.115060 192.168.1.1 > xpb.core.owl.de: icmp: echo request (ipip)
4500 0068 50c1 0000 ff04 a927 c0a8 0101
0000 0000 4500 0054 50c0 0000 ff01 a5a1
c0a8 0101 c27b 4122 0800 fbd3 05e0 0000
4b43 b036 0ecf 0100 0809 0a0b 0c0d 0e0f
1011 1213 1415 1617 1819 1a1b 1c1d 1e1f
2021 2223 2425 2627 2829 2a2b 2c2d 2e2f
3031 3233 3435 3637
But they never make it to the outgoing PPP interface - at least I can't
see them with "tcpdump" neither there nor on the incoming PPP interface
of the remote router. I even disabled IPF to be sure that it doesn't eat
those packets.
>How-To-Repeat:
Try to send packets via an IPIP tunnel and try to trace there way with
"tcpdump".
>Fix:
Sorry, I don't now.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: thorpej
State-Changed-When: Mon Feb 1 23:21:07 PST 1999
State-Changed-Why:
Should be fixed in ip_ipip.c, 1.3. Please ACK.
State-Changed-From-To: feedback->closed
State-Changed-By: hwr
State-Changed-When: Sat Apr 3 00:59:37 PST 1999
State-Changed-Why:
Is fixed in ip_ipip.c, 1.4. Fix confirmed by submitter.
>Unformatted:
The passing of adresses from ifconfig to kernel is a mystery ...
ifconfig passes the addresses in a in_ifaddr struct, where the destination
is not in the contained ifaddr struct, but in a separate field.
Also adresses are passed to the kernel in one pass which means that it makes
no sense, to distinguish between SETIFADDR and SETIFDSTADDR calls to this
driver. The same applies to the gre driver.
The problem was, that the destination address was never passed to the driver.
It was passed to the routing code though, so that the if appeared up in
netstat -r, but wasn't really.
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.