From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Patrick McHardy <kaber@trash.net>
Cc: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>,
linux-kernel@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: 2.6.13-rc2+ - problem with DHCP
Date: Sat, 1 Oct 2005 19:05:31 +0100 [thread overview]
Message-ID: <20051001180530.GB11254@flint.arm.linux.org.uk> (raw)
In-Reply-To: <433ECE42.2070400@trash.net>
On Sat, Oct 01, 2005 at 07:58:26PM +0200, Patrick McHardy wrote:
> Radoslaw Szkodzinski wrote:
> >These kernels just do not get the IP from DHCP.
> >I think the problem is caused by Mercurial tree changeset 8919 (more
> >likely) or 8918.
> >
> >At least the last tested working one is:
> >changeset: 8917:07c96175a75e
> >user: Patrick McHardy <kaber@trash.net>
> >date: Tue Sep 13 21:00:14 2005 +0011
> >summary: [NETFILTER]: Simplify netbios helper
> >
> >Probably the culprit is:
> >changeset: 8919:61b9c3185973
> >user: Patrick McHardy <kaber@trash.net>
> >date: Tue Sep 13 21:00:55 2005 +0011
> >summary: [NETFILTER]: Fix DHCP + MASQUERADE problem
>
> 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?
I tried booting 2.6.14-rc2 on my firewall last Wednesday and it failed
to get its IP address via bootp. I did not see any packets being
transmitted from the machine.
I was going to do some investigation this weekend until I also found
that it would mean that PCMCIA on the box would be busted, which,
unfortunately, means it's useless to run a later kernel. Hence the
investigation is shelved until I've sorted out PCMCIA userland.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-10-01 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 16:40 Radoslaw Szkodzinski
2005-10-01 17:58 ` Patrick McHardy
2005-10-01 18:05 ` Russell King [this message]
2005-10-01 21:39 ` Radoslaw Szkodzinski
2005-10-02 5:28 ` Patrick McHardy
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=20051001180530.GB11254@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=astralstorm@gorzow.mm.pl \
--cc=kaber@trash.net \
--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
Powered by JetHome