From: Andrey Borzenkov <arvidjaar@mail.ru>
To: John Clark <jclark@metricsystems.com>, linux-kernel@vger.kernel.org
Subject: Re: Strange ethN numbering problem.
Date: Tue, 09 Jan 2007 07:06:15 +0300 [thread overview]
Message-ID: <20070109040616.ED8C460BE75@tzec.mtu.ru> (raw)
In-Reply-To: <45A2F218.8010608@metricsystems.com>
John Clark wrote:
> Bernd Eckenfels schrieb:
>> In article <45A2E19F.4070307@metricsystems.com> you wrote:
>>
>>> However, when the system comes up and attempt to do an ifconfig, the
>>> 'ethN' numbers
>>> have changed to a some what intermengled seriese starting with eth6...
>>> eth10.
>>>
>>
>> maybe a system startup script is renaming them (in order to give them
>> well known numbers)?
>>
>> What kind of distribution is that? is this a new problem? Have a look in
>> /etc/mactab.
>
> This is not a 'new' distribtution. In fact, the disk was used for a
> previous hardware box, of the same
> manufacturer and allegedly the same cpu mother board.
>
Then quite likely it remembered lower numbers for "old" interfaces and
starts renaming with next available.
> The kernel is 2.6.19.1 the at-that-moment current linux kernel.
>
> What should I look for in terms of interface renaming.
I guess in udev rules; look also if you have /etc/iftab. The best you can do
is asking in lists/groups dedicated to your distribution.
-andrey
> What is also sort
> of strange is that they all
> have the same 'mac' address vendor unique id... even though two
> interfaces are for an Intel
> ethernet chip, and the othe 4 are from the Marvel chip.
>
> Thanks
> John Clark
next prev parent reply other threads:[~2007-01-09 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 0:28 John Clark
2007-01-09 1:15 ` Bernd Eckenfels
2007-01-09 1:38 ` John Clark
2007-01-09 4:06 ` Andrey Borzenkov [this message]
2007-01-09 18:22 ` John Clark
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=20070109040616.ED8C460BE75@tzec.mtu.ru \
--to=arvidjaar@mail.ru \
--cc=jclark@metricsystems.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
all inboxes | Powered by JetHome®