mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Bill Nottingham <notting@redhat.com>
Cc: jt@hpl.hp.com, linux-kernel@vger.kernel.org, jgarzik@pobox.com,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] All my Pcmcia cards are 'eth0'
Date: Thu, 20 Nov 2003 19:40:58 -0800	[thread overview]
Message-ID: <20031120194058.4961ea1b.rddunlap@osdl.org> (raw)
In-Reply-To: <20031121032819.GA2120@devserv.devel.redhat.com>

On Thu, 20 Nov 2003 22:28:19 -0500 Bill Nottingham <notting@redhat.com> wrote:

| Jean Tourrilhes (jt@bougret.hpl.hp.com) said: 
| > 	One of the main problem is that they are all assigned 'eth0',
| > and therefore all configured with the same IP address. This is really
| > pathetic.
| > 
| > 	The usual answer is : you should use 'nameif' :
| > http://www.xenotime.net/linux/doc/network-interface-names.txt
| > 	Well, of course, nobody ever bothered to try it, so it doesn't
| > work. No comments.
| 
| Well, no offense, but I'd think comments are necessary about no
| one bothering to try it and it not working. I've had an orinoco_cs
| device 'bob' using nameif for a while.

Jean, have you given me any feedback on that small howto and it
not working?  If so, I've missed it and I apologize for that.

I use that method both at home and at work all the time,
with no problems, but I haven't tried it with PCMCIA cards, so
that's something that might need some work, as you have discovered.

home:
[rddunlap@midway rddunlap]$ ifconfig
ethmain   Link encap:Ethernet  HWaddr 00:07:E9:09:09:A8
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:134362 errors:0 dropped:0 overruns:0 frame:0
          TX packets:166363 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:72537067 (69.1 Mb)  TX bytes:22872312 (21.8 Mb)
          Interrupt:11 Base address:0xde80 Memory:ff9a0000-0

work:
[rddunlap@gargoyle rddunlap]$ /sbin/ifconfig
ethmain   Link encap:Ethernet  HWaddr 00:02:55:1A:35:D4
          inet addr:172.20.1.49  Bcast:172.20.255.255  Mask:255.255.0.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17339 errors:0 dropped:0 overruns:0 frame:0
          TX packets:777 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1668859 (1.5 Mb)  TX bytes:103545 (101.1 Kb)
          Interrupt:16 Base address:0x7000


| There are some situations where you have to jump through hoops
| because it can't atomically swap two device names (i.e.,
| eth0 <-> eth1, but the code itself seems to work ok in use here...

--
~Randy

  reply	other threads:[~2003-11-21  3:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  3:13 Jean Tourrilhes
2003-11-21  3:28 ` Bill Nottingham
2003-11-21  3:40   ` Randy.Dunlap [this message]
2003-11-21 17:22     ` Jean Tourrilhes
     [not found] <Ua09.2Wt.17@gated-at.bofh.it>
     [not found] ` <Uajn.3lb.7@gated-at.bofh.it>
2003-11-21  5:14   ` Andi Kleen
2003-11-21  5:18     ` Bill Nottingham
2003-11-21 19:11 Jean Tourrilhes

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=20031120194058.4961ea1b.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notting@redhat.com \
    /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®