From: "Ian S. Nelson" <nelsonis@earthlink.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Quad ethernet card getting assigned different channels every install
Date: Tue, 03 Dec 2002 07:16:07 -0700 [thread overview]
Message-ID: <3DECBCA7.2010502@earthlink.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The kernel is 2.4.18, from Redhat. I've looked at some of the code and I
think this might actually be a hardware bug. I'm helping setup a 3 port
firewall, I'm remote so I haven't been hands on, the guy has a quad
ethernet card in it. Between kernel installs eth0, eth1, eth2, and eth3
seem to change which socket on the card they are.
Anyone seen anything like this before? The hardware didn't change and
to my knowledge no BIOS changes have happened. I'd assume that the PCI
bus would be enumerated the same each time and that the kernel, barring
changes to PCI device discovery, would give the same ethernet channel to
the same socket each time. It boots consistently when we figure out
what port is what.
In this particular case it's potentially a big security concern, if we
swapped the DMZ and protected zones and didn't notice then his network
might be exposed.
thanks,
Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE97LykV28blwDT2YMRAribAJ9N/kevyPK2ALbZqplzRnW2pp/mEACfe/cN
ug4c/2WZtGH7g5MzPBkU0xs=
=wykB
-----END PGP SIGNATURE-----
next reply other threads:[~2002-12-03 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 14:16 Ian S. Nelson [this message]
2002-12-03 14:41 ` Quad ethernet card getting assigned different channels every install Nuno Silva
2002-12-03 15:34 ` device driver modules Salman
[not found] ` <01cd01c29afc$1dab5900$61a1ba40@Henrique>
2002-12-03 21:58 ` Salman
2002-12-03 20:26 ` Quad ethernet card getting assigned different channels every install bill davidsen
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=3DECBCA7.2010502@earthlink.net \
--to=nelsonis@earthlink.net \
--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;
as well as URLs for NNTP newsgroup(s).