Re: Ethernet device names change Bullseye => Bookworm. How to assign unchanging name to device?

20.06.23, 08:36 +0200, Rick Thomas: I've been upgrading my machines Bullseye => Bookworm recently. In a few of these upgrades, the name of the ethernet device changed. (E.g. enP2p32s15f0 => enP2p0s15f0) This required changes to /etc/network/interfaces in order to start up th

Ethernet device names change Bullseye => Bookworm. How to assign unchanging name to device?

I've been upgrading my machines Bullseye => Bookworm recently. In a few of these upgrades, the name of the ethernet device changed. (E.g. enP2p32s15f0 => enP2p0s15f0) This required changes to /etc/network/interfaces in order to start up the interface. This is only a minor in

Re: how to find out ethernet device name

On Wed, Apr 18, 2018 at 08:31:14AM +, Curt wrote: > On 2018-04-17, Don Armstrong wrote: > > sudo ip link; > > Do you need sudo for that (would I get something else here if I was > root)? No, you don't. Don is probably just used to the years of needing sudo or an explicit path to ifconfig.

Re: how to find out ethernet device name

uary/016755.html No, but you can setup your own naming scheme, matching on whatever you see fit, including the MAC address. Say I wanted to name my ethernet device net0, then you could setup something like $ cat /etc/systemd/network/70-net.link [Match] MACAddress=3D00:11:22:33:44:55:66 [Link] Name=3

Re: how to find out ethernet device name

Ben Caradoc-Davies wrote: > On 18/04/18 09:46, Don Armstrong wrote: >> On Tue, 17 Apr 2018, Long Wind wrote: >>> we used to call them eth0, eth1 ...now we use new names >>> i have a ethernet card in stretchhow to find out its name? Thanks! >> sudo ip link; >> will show you what the available interf

Re: how to find out ethernet device name

On 2018-04-17, Don Armstrong wrote: > On Tue, 17 Apr 2018, Long Wind wrote: >> we used to call them eth0, eth1 ...now we use new names >> i have a ethernet card in stretchhow to find out its name? Thanks! > > sudo ip link; Do you need sudo for that (would I get something else here if I was root)?

Re: how to find out ethernet device name

On 18/04/18 09:46, Don Armstrong wrote: On Tue, 17 Apr 2018, Long Wind wrote: we used to call them eth0, eth1 ...now we use new names i have a ethernet card in stretchhow to find out its name? Thanks! sudo ip link; will show you what the available interface names are. And if you want the old

Re: how to find out ethernet device name

On Tue, 17 Apr 2018, Long Wind wrote: > we used to call them eth0, eth1 ...now we use new names > i have a ethernet card in stretchhow to find out its name? Thanks! sudo ip link; will show you what the available interface names are. -- Don Armstrong https://www.donarmstron

Re: ethernet device assignments

On 29/04/12 15:18, paiva...@gmail.com wrote: Tony van der Hoff writes: > In trying to track down some networking problems, I swapped the > ethernet adapter in my server. Since re-booting, it has been assigned > the moniker eth2 rather than eth1 (the motherbaord device is eth0). >

Re: ethernet device assignments

Tony van der Hoff writes: > In trying to track down some networking problems, I swapped the > ethernet adapter in my server. Since re-booting, it has been assigned > the moniker eth2 rather than eth1 (the motherbaord device is eth0). > > So, how do I reset the second adapter to become eth1 ag

Re: ethernet device assignments

On Sun, 29 Apr 2012 14:36:03 +0100, Tony van der Hoff wrote: > In trying to track down some networking problems, I swapped the ethernet > adapter in my server. Since re-booting, it has been assigned the moniker > eth2 rather than eth1 (the motherbaord device is eth0). > > So, how do I reset the s

Re: ethernet device assignments

Am Sonntag, 29. April 2012 schrieb Tony van der Hoff: > In trying to track down some networking problems, I swapped the ethernet > adapter in my server. Since re-booting, it has been assigned the moniker > eth2 rather than eth1 (the motherbaord device is eth0). > > So, how do I reset the second ad

Re: ethernet device assignments

On 29/04/12 15:00, Jochen Spieker wrote: Tony van der Hoff: So, how do I reset the second adapter to become eth1 again? Edit /etc/udev/rules.d/70-persistent-net.rules or just remove it and reboot. J. Great, thanks very much... -- Tony van der Hoff| mailto:t...@vanderhoff.org Bucki

Re: ethernet device assignments

Tony van der Hoff: > > So, how do I reset the second adapter to become eth1 again? Edit /etc/udev/rules.d/70-persistent-net.rules or just remove it and reboot. J. -- Watching television is more hip than actually speaking to anyone. [Agree] [Disagree]

ethernet device assignments

In trying to track down some networking problems, I swapped the ethernet adapter in my server. Since re-booting, it has been assigned the moniker eth2 rather than eth1 (the motherbaord device is eth0). So, how do I reset the second adapter to become eth1 again? -- Tony van der Hoff| ma

Re: Meaningful names; was Re (3): dreaded ethernet device renaming

On 04/01/2011 12:18 PM, peasth...@shaw.ca wrote: [snip] Names such as eth0 and eth0.absent still do not solve the problem of identifying external hot swappable devices. Plug in three Linksys USB adapters yielding eth3, eth4 and eth5. Which eth is which? Meaningful names work. For example Links

Meaningful names; was Re (3): dreaded ethernet device renaming

Brian, From: bri...@aracnet.com Date: Thu, 31 Mar 2011 19:39:14 -0700 > ... tacked the new eth onto the end, so eth0 ended up being renamed eth3. The old Ethernet device remained in the rules file with the name eth0 and the new device was assigned the name eth3? So the new device was j

Re: [SOLVED] dreaded ethernet device renaming

On Thu, 31 Mar 2011 20:06:51 -0400 (EDT) Stephen Powell wrote: > On Thu, 31 Mar 2011 10:34:32 -0400 (EDT), bri...@aracnet.com wrote: > > > > Thanks to everyone who responded ! > > > > That explains everything. I changed motherboards out from under the > > system. So it appended the new eth to

Re: Re (2): dreaded ethernet device renaming

On Thu, 31 Mar 2011 09:32:18 -0800 peasth...@shaw.ca wrote: > From: bri...@aracnet.com > Date: Thu, 31 Mar 2011 07:34:32 -0700 > > It seems to me that this is a really ugly user trap, even if it's a > > trap you get into replacing the old motherboard. > > In the Linux world, udev is really a beau

[SOLVED] dreaded ethernet device renaming

On Thu, 31 Mar 2011 10:34:32 -0400 (EDT), bri...@aracnet.com wrote: > > Thanks to everyone who responded ! > > That explains everything. I changed motherboards out from under the > system. So it appended the new eth to the old ones. > > It seems to me that this is a really ugly user trap, even

Re (2): dreaded ethernet device renaming

From: bri...@aracnet.com Date: Thu, 31 Mar 2011 07:34:32 -0700 > It seems to me that this is a really ugly user trap, even if it's a > trap you get into replacing the old motherboard. In the Linux world, udev is really a beautiful way of handling contemporary peripheral devices. eth0, eth1 .

Re: dreaded ethernet device renaming

On Thu, 31 Mar 2011 07:00:05 -0400 (EDT) Stephen Powell wrote: > On Thu, 31 Mar 2011 04:37:57 -0400 (EDT), David Goodenough wrote: > > have a look at /etc/udev/rules.d/70-persistent-net.rules. This file > > tries to make sure that network adapters are always named in the > > same way in whatever

Re: dreaded ethernet device renaming

On Thu, 31 Mar 2011 04:37:57 -0400 (EDT), David Goodenough wrote: > have a look at /etc/udev/rules.d/70-persistent-net.rules. This file > tries to make sure that network adapters are always named in the same > way in whatever order they are started. The problem comes when you replace a > network

Re: dreaded ethernet device renaming

On Thursday 31 March 2011, bri...@aracnet.com wrote: > I mean really, why does the system still do stupid sh*t like this. > > renamed network interface eth0 to eth3 > > Why oh why ! It was already eth0, what possible reason could it have > to go rename it. > > oh and by the way, just to be ma

Re: dreaded ethernet device renaming

On Wed, Mar 30, 2011 at 9:23 PM, wrote: > I mean really, why does the system still do stupid sh*t like this. > >  renamed network interface eth0 to eth3 > > Why oh why !  It was already eth0, what possible reason could it have > to go rename it. > > oh and by the way, just to be maximally annoyin

dreaded ethernet device renaming

I mean really, why does the system still do stupid sh*t like this. renamed network interface eth0 to eth3 Why oh why ! It was already eth0, what possible reason could it have to go rename it. oh and by the way, just to be maximally annoying, it most certainly decieds to name it something else

Re: The same hardware different ethernet device names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Dec 04, 2006 at 10:16:18AM +0100, Marcin Giedz wrote: > Hello, > > I've got several Intel server platforms on every platform I > upgraded BIOS to the latest version and installed Debian Etch. On five > of them I have two ethernet interf

The same hardware different ethernet device names

Hello, I've got several Intel server platforms on every platform I upgraded BIOS to the latest version and installed Debian Etch. On five of them I have two ethernet interfaces eth0/eth1 but ONLY one has eth1 eth2 actually eth2/eth1 - this order. debian:~# cat /proc/net/dev Inter-| Re

Re: Promiscuous mode for ethernet device

Kevin Coyner, 2002-Dec-10 17:31 -0500: > > On Tue, Dec 10, 2002 at 01:47:41PM -0500, sean finney wrote.. > > > heya, > > > > iirc promiscuous mode means to listen to all traffic on the network > > as opposed to only traffic addressed to the mac address of your ethernet > > card. this is re

Re: Promiscuous mode for ethernet device

On Tue, Dec 10, 2002 at 05:31:32PM -0500, Kevin Coyner wrote: > One question that I've been meaning to ask and this seems to be close to > being on-topic: If you're running a sniffer in promiscuous mode on a > network that is linked together via a switch (as opposed to a hub), will > you still be

Re: Promiscuous mode for ethernet device

On Tue, Dec 10, 2002 at 05:31:32PM -0500, Kevin Coyner wrote: > > On Tue, Dec 10, 2002 at 01:47:41PM -0500, sean finney wrote.. > > > heya, > > > > iirc promiscuous mode means to listen to all traffic on the network > > as opposed to only traffic addressed to the mac address of your ethernet

Re: Promiscuous mode for ethernet device

Kevin Coyner said: > One question that I've been meaning to ask and this seems to be close to > being on-topic: If you're running a sniffer in promiscuous mode on a > network that is linked together via a switch (as opposed to a hub), will > you still be able to passively capture all packets from

Re: Promiscuous mode for ethernet device

On Tue, Dec 10, 2002 at 01:47:41PM -0500, sean finney wrote.. > heya, > > iirc promiscuous mode means to listen to all traffic on the network > as opposed to only traffic addressed to the mac address of your ethernet > card. this is real useful for passively sniffing packets on your > netw

Re: Promiscuous mode for ethernet device

On Tue, Dec 10, 2002 at 09:27:11PM +0100, A. Loonstra wrote: > I have been using tcpdump but that was only to debug software which > wasn't working properly. Still I think it's weird that it did happen > upon shutdown. I've been checking the scripts which are called during > shutdown but couldn'

Re: Promiscuous mode for ethernet device

sean finney wrote: heya, as for why you were going in and out of that mode -- were you using any packet filtering/processing application like tcpdump or dsniff? iptables might do that as well, but i can't say off the top of my head for sure. sean I have been using tcpdump but that was only t

Re: Promiscuous mode for ethernet device

heya, iirc promiscuous mode means to listen to all traffic on the network as opposed to only traffic addressed to the mac address of your ethernet card. this is real useful for passively sniffing packets on your network when you don't want to / can't run it on one of the machines in question.

Re: Promiscuous mode for ethernet device

A. Loonstra said: > What the F^%&*( what does this mean??? It was quite useless to put the > machine into promiscuous mode since it was shutting down.. Or was the > DHCPD daemon doing something? you have any network monitoring software installed? e.g. arp tracker, network sniffer, snort, or some

Promiscuous mode for ethernet device

After succesfully upgrading a debian potato server to woody I was left with an upgraded system which only needed a reboot to get kernel 2.4.18 running. But since everything was done remotely I waited until I was standing in front of the machine to do the reboot. I'm glad I did!!! When shutting

Re: How does Ethernet device know address of transfer buffer

High, On Wed, 7 Nov 2001 [EMAIL PROTECTED] wrote: > Hi, > > I can successfully install the 3c905 Ethernet driver, > but I don’t know why it works. This proves I don’t know > what is going on. I hope that someone can offer some > light. > > I use install parameters “irq=11" and I don’t set an

How does Ethernet device know address of transfer buffer

Hi, I can successfully install the 3c905 Ethernet driver, but I don’t know why it works. This proves I don’t know what is going on. I hope that someone can offer some light. I use install parameters “irq=11" and I don’t set an io address. If I try fill in the address e.g. “io=0x220" I receiv

Re: Ethernet device

On Sat, Jun 23, 2001 at 07:27:27PM -0300, Juan wrote: > Hi Kent, > > Thanks for answer. > > > > > iface lo inet loopback > > > iface eth0 inte static > > >address 192.168.66.1 > > >netmask 255.255.255.0 > > > >iface eth0 inte static > > > >should be inet > Sorry. It was

Re: Ethernet device

On Sat, Jun 23, 2001 at 06:32:55PM -0300, Juan wrote: > > > > >Configure the network interface in /etc/network/interfaces. See > >manpage interfaces(5) for the syntax. > > I think that I miss something. > Is rtl8139.o module for eth0 configured within /etc/network/interfaces? > > iface lo inet l

Re: Ethernet device

Configure the network interface in /etc/network/interfaces. See manpage interfaces(5) for the syntax. I think that I miss something. Is rtl8139.o module for eth0 configured within /etc/network/interfaces? iface lo inet loopback iface eth0 inte static address 192.168.66.1 netmask 255.255.

Re: Ethernet device

; > - I updated /etc/hosts and /etc/networks. > - ifconfig eth0 192.168.66.1 > - ping 192.168.66.1 or other IP within my lan is working > > Bu when I restart my machine, the Ethernet is not working anymore. > How can I configure to activate my Ethernet device at start? > > T

Re: Ethernet device

; How can I configure to activate my Ethernet device at start? > After you have edited /etc/network/interfaces you don't have to reboot. Just run - # /etc/init.d/networking restart to restart the network. kent -- From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke

Re: Ethernet device

Juan <[EMAIL PROTECTED]> writes: > Bu when I restart my machine, the Ethernet is not working anymore. > How can I configure to activate my Ethernet device at start? Configure the network interface in /etc/network/interfaces. See manpage interfaces(5) for the syntax. hth,

Ethernet device

Hi, - I updated /etc/hosts and /etc/networks. - ifconfig eth0 192.168.66.1 - ping 192.168.66.1 or other IP within my lan is working Bu when I restart my machine, the Ethernet is not working anymore. How can I configure to activate my Ethernet device at start? TIA, Juan.

Re: Burn in an ethernet device

Danny Pansters wrote: > You shouldn't use append unless you need to get a second eth card working > (and even so, I'm pretty sure it's only needed for pre-2.2.x kernels). The > eth0 should than become the card with the lowest hardware address, the other > would become eth1. Unless you have an ISA

Re: Burn in an ethernet device

Hi Adrian, On Tue, 05 Sep 2000, Adrian Nims wrote: > I recompiled the kernel, I introduced an "append" line in lilo.conf in > order to burn in an ethernet device. At reboot, the sistem (debian) see the > ethernet board as eth0, everything seems OK but after boot, when i

Burn in an ethernet device

I recompiled the kernel, I introduced an "append" line in lilo.conf in order to burn in an ethernet device. At reboot, the sistem (debian) see the ethernet board as eth0, everything seems OK but after boot, when i say "ifconfig" it appears to me only the loopback device. Wha