From: Patrick McHardy <kaber@trash.net>
To: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: linux-kernel@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: 2.6.13-rc2+ - problem with DHCP
Date: Sun, 02 Oct 2005 07:28:19 +0200 [thread overview]
Message-ID: <433F6FF3.1040706@trash.net> (raw)
In-Reply-To: <433F0228.6000304@gorzow.mm.pl>
Radoslaw Szkodzinski wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Patrick McHardy wrote:
> |
> | Are you sure? The patch was supposed to fix problems with DHCP clients
> | using regular UDP sockets for sending DHCP requests. Which client are
> | you using?
> |
>
> udhcpcd, version 0.9.9-pre (Gentoo ebuild
> net-misc/udhcp-0.9.9_pre20041216-r1, no crazy optimisations, stock init
> script, IP release disabled)
I can't reproduce the problem, it reliably works for me using pump,
dhclient or udhcpc. One thing I've noticed is that udhcpc 0.98
doesn't set the interface up itself and fails if it is down. Please
make sure that it is up in your tests.
> 2.6.13, 2.6.14-rc1 (up to the patch) both work fine.
> 2.6.14-rc2 and 2.6.14-rc3 do not. (they can't discover IP address)
> The window is between that commit and rc2.
> (about 180 changesets)
>
> I only suspect that patch, it could be something else but I highly doubt
> it. I'll check the current kernel with the patch backed out when I have
> to restart.
Thanks. You mentioned you're setting up your ruleset after DHCP, which
means the patch can't be responsible because the codepath is never
taken for DHCP queries, so you probably need to do a binary search
over the remaining 180 changesets.
next prev parent reply other threads:[~2005-10-02 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 16:40 2.6.13-rc2+ - problem with DHCP Radoslaw Szkodzinski
2005-10-01 17:58 ` Patrick McHardy
2005-10-01 18:05 ` Russell King
2005-10-01 21:39 ` Radoslaw Szkodzinski
2005-10-02 5:28 ` Patrick McHardy [this message]
2005-10-02 18:23 ` [SOLVED?] " Radoslaw Szkodzinski
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=433F6FF3.1040706@trash.net \
--to=kaber@trash.net \
--cc=astralstorm@gorzow.mm.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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