From: Luca Montecchiani <luca.montecchiani@teamfab.it>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk, davem@redhat.com
Subject: [PATCH] Re: 2.2.18pre21 - IP kernel level autoconfiguration
Date: Mon, 20 Nov 2000 18:03:04 +0100 [thread overview]
Message-ID: <3A195948.C864BB8E@teamfab.it> (raw)
In-Reply-To: <H00000650001a074.0974474275.dublin.innovates.com@MHS> <3A154F7A.6F0F435D@teamfab.it>
Luca Montecchiani wrote:
:
> Anyway I'll do more investigation about my problem to get bootp
> work with dhcp compiled into kernel next week
With the 2.2.18pre22 kernel and also pre21 last time I checked
if you compile the kernel with DHCP and BOOTP, it's impossible
to use bootp, you need to recompile the kernel without dhcp.
The problem (bug) is that dhcp code is _always_ executed also in
the case of bootp, breaking the procedure :(
I love to have dhcp and bootp compiled into kernel, so I can
chose my preferred protocol with the ip=XXXX option.
I don't like this _goto_ patch against 2.2.18pre22, but work :
--- ipconfig.c.old Mon Nov 20 17:01:16 2000
+++ ipconfig.c Mon Nov 20 17:34:01 2000
@@ -842,6 +842,8 @@
u32 server_id = INADDR_NONE;
int mt = 0;
+ if ( !(ic_proto_enabled & IC_USE_DHCP) ) goto nodhcp;
+
ext = &b->exten[4];
while (ext < end && *ext != 0xff) {
u8 *opt = ext++;
@@ -896,6 +898,7 @@
#endif /* IPCONFIG_DHCP */
+nodhcp:
ext = &b->exten[4];
while (ext < end && *ext != 0xff) {
u8 *opt = ext++;
ciao,
luca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-20 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 15:17 Re: 2.2.18pre21 - IP kernel level autoconfiguration chip
2000-11-17 15:32 ` Luca Montecchiani
2000-11-20 17:03 ` Luca Montecchiani [this message]
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=3A195948.C864BB8E@teamfab.it \
--to=luca.montecchiani@teamfab.it \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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