Ketil Froyn wrote:
Hi,
I have a computer with some network interfaces, and I am unable to
determine which physical interface gets assigned to which ethX during boot.
Specifically, my problem is that the firewire driver suddenly started
using eth1 instead of eth2 yesterday. It hadn't done thi
On Thu, 23 Feb 2006, Alex Nordstrom wrote:
> If, however, you use udev, or if using udev is an option for you, it
> would probably be easiest and most elegant to write a rule for the
> naming of the different components based on their characteristics (such
> as MAC address). Here is a good intro
Debian's /etc/network/interfaces configuration file supports checking
for charactaristics of an interface before bringing it up.
/usr/share/doc/ifupdown/examples/network-interfaces.gz has the skinny
on this.
-Peter
On Thu, Feb 23, 2006 at 12:01:14PM +0100, Ketil Froyn wrote:
>Hi,
>
>I ha
Ketil Froyn escribe:
> Warning: Interface name is `eth0' at line 1, can't be mapped reliably.
As far as I know this warning is not relevant, ifrename works for me
without a flaw.
Cordially, Ismael
--
mí, myself et moi http://lamediahostia.blogspot.com/
http://www.flickr.com/pho
On 2/23/06, Florian Kulzer <[EMAIL PROTECTED]> wrote:
If you do not want to switch to udev, maybe the package 'ifrename' canensure a deterministic naming of your network interfaces. I always hadproblems when using ethX (as Magnus has also pointed out in his mail)
which I avoided by assigning new na
Ketil Froyn wrote:
On 2/23/06, Magnus Therning <[EMAIL PROTECTED]> wrote:
My temporary solution was to change the pattern for one of the devices.
My problematic device is a rt2500-based PCI wireless card. I put the
following in a file in /etc/modprobe.d/ :
options rt2500 ifname=wlan%d
That r
El Jueves, 23 de Febrero de 2006 12:01, Ketil Froyn escribió:
> Hi,
>
> I have a computer with some network interfaces, and I am unable to
> determine which physical interface gets assigned to which ethX during boot.
>
> Specifically, my problem is that the firewire driver suddenly started using
>
On 2/23/06, Magnus Therning <[EMAIL PROTECTED]> wrote:
My temporary solution was to change the pattern for one of the devices.My problematic device is a rt2500-based PCI wireless card. I put thefollowing in a file in /etc/modprobe.d/ : options rt2500 ifname=wlan%d
That renamed my wireless to wlan0,
On 2/23/06, Alex Nordstrom <[EMAIL PROTECTED]> wrote:
Information on which version of Debian and which kernel you use would beuseful in answering this question. Whether or not you use udev wouldalso be relevant.Thanks for the quick reply! I use debian
3.1 with the 2.6.8-2 kernel. Thursday, 23 Febr
On Thu, Feb 23, 2006 at 12:01:14PM +0100, Ketil Froyn wrote:
>Hi,
>
>I have a computer with some network interfaces, and I am unable to
>determine which physical interface gets assigned to which ethX during
>boot.
I've just recently run into the same problem.
>Specifically, my problem is that the
Information on which version of Debian and which kernel you use would be
useful in answering this question. Whether or not you use udev would
also be relevant.
Thursday, 23 February 2006 19:01, Ketil Froyn wrote:
> Specifically, my problem is that the firewire driver suddenly started
> using eth
Hi,I have a computer with some network interfaces, and I am unable to determine which physical interface gets assigned to which ethX during boot.Specifically, my problem is that the firewire driver suddenly started using eth1 instead of eth2 yesterday. It hadn't done this before, and I had to chang
12 matches
Mail list logo
