From: Eric Lammerts <eric@lammerts.org>
To: kernel list <linux-kernel@vger.kernel.org>, gregkh@suse.de
Subject: 2.6.30: tun losing ip
Date: Sun, 14 Jun 2009 01:18:28 -0400 [thread overview]
Message-ID: <4A348824.1030503@lammerts.org> (raw)
Hi,
I'm having problems with openvpn clients on 2.6.30. I get stuff like this:
TUN/TAP device tun0 opened
TUN/TAP TX queue length set to 100
/sbin/ifconfig tun0 10.2.222.50 pointopoint 10.2.222.49 mtu 1500
/sbin/route add -net 10.2.222.0 netmask 255.255.255.0 gw 10.2.222.49
SIOCADDRT: No such process
There is something strange going on with tun devices:
# tunctl -t tun1; ifconfig tun1 1.2.3.4; ifconfig tun1; sleep 1; ifconfig
tun1
Set 'tun1' persistent and owned by uid 0
tun1 Link encap:Ethernet HWaddr 1E:EF:79:F2:D9:67
inet addr:1.2.3.4 Bcast:1.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
tun1 Link encap:Ethernet HWaddr 1E:EF:79:F2:D9:67
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
First you see the ip, then you don't...
I traced it back to this commit:
$ git-bisect bad
05f54c13cd0c33694eec39a265475c5d6cf223cf is first bad commit
commit 05f54c13cd0c33694eec39a265475c5d6cf223cf
Author: Hugh Dickins <hugh@veritas.com>
Date: Thu Apr 16 21:55:29 2009 +0100
Revert "kobject: don't block for each kobject_uevent".
If I take 2.6.30 and revert that commit, the problem goes away.
Eric
next reply other threads:[~2009-06-14 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 5:18 Eric Lammerts [this message]
2009-06-14 9:28 ` 2.6.30: tun losing ip Hugh Dickins
2009-06-14 18:36 ` Eric Lammerts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A348824.1030503@lammerts.org \
--to=eric@lammerts.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox