Re: Naming of network devices - how to improve it in buster

On Thu, 2017-07-27 at 10:05 +, Sam Morris wrote: > You'd have to use BindsTo=sys-subsystem-net-devices-blah.device. But  > BindsTo= and device units are a bit fiddly, see systemd/systemd/issues/4413>. I had a systemd enthusiast sitting beside me who recommended that. I

Re: Naming of network devices - how to improve it in buster

On Sat, 15 Jul 2017 22:44:46 +1000, Russell Stuart wrote: > On Sat, 2017-07-15 at 07:46 +0200, Tollef Fog Heen wrote: >> Doesn't something like: >> >> [Unit] >> Description=My hook for foo.link After=foo.link BindsTo=foo.link >> >> [Service] >> Type=oneshot ExecStart=/usr/local/sbin/whatever

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 19, 2017 at 10:53:34PM +0200, Guus Sliepen wrote: > rename mac/00:16:0a:26:99:c6/=en0 > auto en0 > iface en0 ... This should now work in ifupdown 0.8.22. -- Met vriendelijke groet / with kind regards, Guus Sliepen signature.asc Description: PGP signature

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 19, 2017 at 11:32:38PM +0200, Adam Borowski wrote: > Well, but on the way up, /eth0/=en0 or mac/.../=en0 will match logical > interface "en0", and on the way down, and subsequent manual ups, it will > match the kernel name "en0". Am I missing something? Yes, /eth0/=en0 will match

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 19, 2017 at 10:53:34PM +0200, Guus Sliepen wrote: > On Mon, Jul 17, 2017 at 06:22:14PM +0200, Guus Sliepen wrote: > > > > Thus, what about this: > > > auto mac/00:16:0a:26:99:c6/=en0 > > > iface en0 inet6 static > > > address 3:1415:9265:3589:7932:3846:2643:3832/64 > > > gateway

Re: Naming of network devices - how to improve it in buster

On Mon, Jul 17, 2017 at 06:22:14PM +0200, Guus Sliepen wrote: > > Thus, what about this: > > auto mac/00:16:0a:26:99:c6/=en0 > > iface en0 inet6 static > > address 3:1415:9265:3589:7932:3846:2643:3832/64 > > gateway 3:1415:9265:3589::1 > > rename > > > > With the rename command

Re: Naming of network devices - how to improve it in buster

On Mon, Jul 17, 2017 at 05:12:07AM +0200, Adam Borowski wrote: > > That's indeed an interesting issue. Currently, ifupdown doesn't rename > > interfaces. You could add a line like: > > > > post-up ip link set $IFACE name $LOGICAL > > > > Which will do what you want, except ifupdown doesn't

Re: Naming of network devices - how to improve it in buster

On Sun, Jul 16, 2017 at 01:54:27PM +0200, Guus Sliepen wrote: > On Sat, Jul 15, 2017 at 10:25:22PM -0300, Henrique de Moraes Holschuh wrote: > > It is indeed Very Cool, but it might not solve one little thing: > > iptables firewalling. > > > > Is that a way to trigger an ifrename using this, so

Re: Naming of network devices - how to improve it in buster

On Sun, 2017-07-16 at 13:54 +0200, Guus Sliepen wrote: > On Sat, Jul 15, 2017 at 10:25:22PM -0300, Henrique de Moraes Holschuh wrote: > > > > > This will match any interface that has MAC address 01:23:45:67:89:ab, > > > > and will use the "foo" stanzas to configure it. > > > > > > Awesome!  This

Re: Naming of network devices - how to improve it in buster

On Sat, Jul 15, 2017 at 10:25:22PM -0300, Henrique de Moraes Holschuh wrote: > > > This will match any interface that has MAC address 01:23:45:67:89:ab, > > > and will use the "foo" stanzas to configure it. > > > > Awesome! This sounds like the best solution so far. As Adam discovered, there

Re: Naming of network devices - how to improve it in buster

On Sat, 15 Jul 2017, Adam Borowski wrote: > > This will match any interface that has MAC address 01:23:45:67:89:ab, > > and will use the "foo" stanzas to configure it. > > Awesome! This sounds like the best solution so far. It is indeed Very Cool, but it might not solve one little thing:

Re: Naming of network devices - how to improve it in buster

On Sat, Jul 15, 2017 at 10:30:59PM +0200, Guus Sliepen wrote: > On Tue, Jul 11, 2017 at 06:04:29PM +0200, Guus Sliepen wrote: > > > This is not impossible to do. I actually have some code to make ifupdown > > use interface matching, I'm afraid I was too late in the stretch cycle > > to have a

Re: Naming of network devices - how to improve it in buster

On Tue, Jul 11, 2017 at 06:04:29PM +0200, Guus Sliepen wrote: > This is not impossible to do. I actually have some code to make ifupdown > use interface matching, I'm afraid I was too late in the stretch cycle > to have a well-tested implementation. I will try to add this early in > buster so it

Re: Naming of network devices - how to improve it in buster

On Sat, 2017-07-15 at 07:46 +0200, Tollef Fog Heen wrote: > Doesn't something like: > > [Unit] > Description=My hook for foo.link > After=foo.link > BindsTo=foo.link > > [Service] > Type=oneshot > ExecStart=/usr/local/sbin/whatever > RemainAfterExit=yes > > [Install] >

Re: Naming of network devices - how to improve it in buster

Hi there, On Fri, 14 Jul 2017 23:55:09 -0400, Anthony DeRobertis wrote: > On 07/11/2017 03:08 PM, Nikolaus Rath wrote: > > > > I wonder if anyone actually uses /dev/disk/by-path? > > It's useful for a quick "ls -l /dev/disk/by-path | grep 'sda$;" to figure > out which port a disk is plugged

Re: Naming of network devices - how to improve it in buster

On Sat, 2017-07-15 at 10:46 +0200, Marc Haber wrote: > On Thu, 13 Jul 2017 09:36:58 -0700, Josh Triplett > wrote: > >But if you run into a command that accepts filenames but for which > >bash-completion doesn't complete filenames, *please* report it as a > bug > >on the

Re: Naming of network devices - how to improve it in buster

]] Marc Haber > On Thu, 13 Jul 2017 19:37:52 +0200, Tollef Fog Heen > wrote: > >]] Marc Haber > >> My finger memory will still type tcpdump -i eth0 before the brain can > >> intervene ten years from now. > > > >In that particular case, I'll recommend you either leaving out the

Re: Naming of network devices - how to improve it in buster

On Thu, 13 Jul 2017 09:36:58 -0700, Josh Triplett wrote: >But if you run into a command that accepts filenames but for which >bash-completion doesn't complete filenames, *please* report it as a bug >on the package providing the bash completions for that command. To have it

Re: Naming of network devices - how to improve it in buster

On Thu, 13 Jul 2017 19:37:52 +0200, Tollef Fog Heen wrote: >]] Marc Haber >> My finger memory will still type tcpdump -i eth0 before the brain can >> intervene ten years from now. > >In that particular case, I'll recommend you either leaving out the -i >switch completely or just

Re: Naming of network devices - how to improve it in buster

]] Russell Stuart > As for *.link files, syntactically they like all systemd stuff are a > huge improvement on what came before them. But the old ugly udev rules > have one thing over them - they provide hooks for scripts to cover > cases they haven't thought of. Scripts seem to be an anathema

Re: Naming of network devices - how to improve it in buster

On 07/14/2017 08:01 PM, Russell Stuart wrote: (b) Those who enter the debian device names manually into config files, and have machines that network device names even though no one armed with a screw driver has been near the thing. These people would very much care. I was asking

Re: Naming of network devices - how to improve it in buster

On 07/11/2017 03:08 PM, Nikolaus Rath wrote: I wonder if anyone actually uses /dev/disk/by-path? It's useful for a quick "ls -l /dev/disk/by-path | grep 'sda$;" to figure out which port a disk is plugged into. I'm sure there are other ways, probably better ones... but that one is easy to

Re: Naming of network devices - how to improve it in buster

On Fri, 2017-07-14 at 18:31 -0700, Russ Allbery wrote: > I didn't think anyone was claiming they would, so I'm not sure why > you felt like it was necessary to say this. It's the same reason you feel like it was necessary to say this, I guess: On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery

Re: Naming of network devices - how to improve it in buster

Russell Stuart writes: > On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery wrote: >> Right, I'm completely happy with the current behavior.  I have no >> objections to the change.  I just also don't particularly care; I've >> stopped using ifupdown and am using *.link

Re: Naming of network devices - how to improve it in buster

On Fri, 2017-07-14 at 09:11 -0700, Russ Allbery wrote: > Right, I'm completely happy with the current behavior.  I have no > objections to the change.  I just also don't particularly care; I've > stopped using ifupdown and am using *.link units for network > configuration, which makes all of this

Re: Naming of network devices - how to improve it in buster

On Fri, 2017-07-14 at 11:20 -0300, Henrique de Moraes Holschuh wrote: > MOST PCI/PCIe NICs indeed use "ethX", etc.  But the naming scheme > really is device driver-specific, and the "default" name used by a > driver is considered part of the kernel stable ABI, and cannot be > changed on the kernel

Re: Naming of network devices - how to improve it in buster

On Fri, Jul 14, 2017 at 10:20 AM, Henrique de Moraes Holschuh wrote: > On Fri, 14 Jul 2017, Tom H wrote: >> The classic naming scheme for network interfaces applied by the kernel >> is to simply assign names beginning with "eth0", "eth1", ... to all >> interfaces as they are

Re: Naming of network devices - how to improve it in buster

Vincent Bernat writes: > ❦ 13 juillet 2017 13:55 -0700, Russ Allbery  : >> Yeah, we were using FAI, but I believe that's the basic mechanism we >> were using and then found a way to use it to generate the udev rule to >> do persistent naming. > This is a

Re: Naming of network devices - how to improve it in buster

On Fri, 14 Jul 2017, Tom H wrote: > > I've never seen the kernel vary the order it enumerates a PCI bus. It doesn't, the last time it changed was on 2.4->2.6. OTOH, *driver probe* ordering can and does change, especially when device probes are being done in parallel. It is best to not get bus

Re: Naming of network devices - how to improve it in buster

❦ 13 juillet 2017 13:55 -0700, Russ Allbery  : >>> The workaround was a bunch of bullshit in our install process to try to >>> figure out which NIC got the DHCP response and then pin that one to >>> eth0 for subsequent boots. (Which is basically what udev persistent >>> naming

Re: Naming of network devices - how to improve it in buster

On Thu, Jul 13, 2017 at 6:14 AM, Russell Stuart wrote: > On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: >> >> Stateless "/etc". >> >> Systems with multiple NICs where the order in which they're >> recognized by the kernel can vary. > > I asked for a person. You

Re: Naming of network devices - how to improve it in buster

On Thu, 2017-07-13 at 09:07 -0700, Russ Allbery wrote: > Er, I saw this all the time without udev persistent naming.  Every > time we rebooted one of our servers, the four onboard NICs (of which > we were only using one -- long story, but basically that's just what > the systems came with out of

Re: Naming of network devices - how to improve it in buster

Philipp Kern writes: > On 13.07.2017 18:07, Russ Allbery wrote: >> The workaround was a bunch of bullshit in our install process to try to >> figure out which NIC got the DHCP response and then pin that one to >> eth0 for subsequent boots. (Which is basically what udev

Re: Naming of network devices - how to improve it in buster

On 13.07.2017 18:07, Russ Allbery wrote: > The workaround was a bunch of bullshit in our install process to try to > figure out which NIC got the DHCP response and then pin that one to eth0 > for subsequent boots. (Which is basically what udev persistent naming > did.) At least when you netboot

Re: Naming of network devices - how to improve it in buster

Nikolaus Rath: > I wonder if anyone actually uses /dev/disk/by-path? We used it at work to filter guest LVM VGs out of libvirt hosts: # grep by-path /etc/lvm/lvm.conf filter = [ "r|^/dev/disk/by-path/ip-.*-iscsi|" ] Cheers! Alex signature.asc Description: PGP signature

Re: Naming of network devices - how to improve it in buster

]] Russell Stuart > It's not sysadmin's managing fleets of machines. They need persistent > names, but you rapidly go insane if the lan NIC isn't named "lan0" or > something regardless of the machine your platform is running on. So > you end up dropping your own customer files in

Re: Naming of network devices - how to improve it in buster

]] Marc Haber > My finger memory will still type tcpdump -i eth0 before the brain can > intervene ten years from now. In that particular case, I'll recommend you either leaving out the -i switch completely or just doing `-i any`. I find it's rare I care about what interface traffic happens on.

Re: Naming of network devices - how to improve it in buster

Adam Borowski wrote: > Alas, having "bash-completion" installed, while adding some > context-sensitive completion, also breaks filename completion. You can always press Alt-/ if you want to use filename completion unconditionally. But if you run into a command that accepts filenames but for

Re: Naming of network devices - how to improve it in buster

On Wed, 12 Jul 2017 18:47:18 +0200, Michael Biebl wrote: >Am 12.07.2017 um 17:35 schrieb Marc Haber: >> My finger memory will still type tcpdump -i eth0 before the brain can >> intervene ten years from now. > >thankfully tcpdump (and lots of other tools) have nice shell

Re: Naming of network devices - how to improve it in buster

Russell Stuart writes: > On Thu, 2017-07-13 at 11:21 +, Clinton Roy wrote: >> Unfortunately, others have (well, not the kernel, but PCI): >> >> https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924. >> html > If you plug new hardware devices in

Re: Naming of network devices - how to improve it in buster

On Thu, 2017-07-13 at 11:21 +, Clinton Roy wrote: > Unfortunately, others have (well, not the kernel, but PCI): > > https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924. > html If you plug new hardware devices in then of course things are going to change. The claim really is

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 12, 2017 at 06:47:18PM +0200, Michael Biebl wrote: > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > My finger memory will still type tcpdump -i eth0 before the brain can > > intervene ten years from now. > > thankfully tcpdump (and lots of other tools) have nice shell completion. >

Re: Naming of network devices - how to improve it in buster

On Thu, 13 Jul 2017 at 20:15 Russell Stuart wrote: > > I've never seen the kernel vary the order it enumerates a PCI bus. Unfortunately, others have (well, not the kernel, but PCI): https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924.html cheers,

Re: Naming of network devices - how to improve it in buster

On Thu, 2017-07-13 at 20:14 +1000, Russell Stuart wrote: > On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: > > Stateless "/etc". > > > > Systems with multiple NICs where the order in which they're > > recognized by the kernel can vary. > > I asked for a person.  I guess I really asking for a use

Re: Naming of network devices - how to improve it in buster

On Tue, 2017-07-11 at 17:05 +0200, Samuel Thibault wrote: > Simon McVittie, on mar. 11 juil. 2017 15:18:26 +0100, wrote: > > Network devices are (as far as I know) the only class of device managed by > > udev that is not backed by a device node, which means udev cannot provide > > multiple

Re: Naming of network devices - how to improve it in buster

On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: > Stateless "/etc". > > Systems with multiple NICs where the order in which they're > recognized by the kernel can vary. I asked for a person. I guess I really asking for a use case. "Stateless /etc" isn't either. I've never seen the kernel vary

Re: Naming of network devices - how to improve it in buster

On Thu, Jul 13, 2017 at 12:22 AM, Russell Stuart wrote: > > I still don't understand what use case the current scheme is aimed at. Stateless "/etc". Systems with multiple NICs where the order in which they're recognized by the kernel can vary.

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 12, 2017 at 07:16:16PM -0300, Henrique de Moraes Holschuh wrote: > > Indeed, the best solution would be to never rename the interfaces and > > simply create aliases / symlinks. Then again, I'm no kernel hacker so I > > have no idea if that would be feasible. > > ip link set dev eth0

Re: Naming of network devices - how to improve it in buster

On Wed, 2017-07-12 at 17:35 +0200, Marc Haber wrote: > I'd rather have breakage in this case than having to look for the > interface every fscking time I need to run tcpdump, or having to > adapt to an entirely new name schema like lanc0 and lanw0 to not > stomp in the kernel's name space when

Re: Naming of network devices - how to improve it in buster

On Wed, 12 Jul 2017, Michael Biebl wrote: > Am 12.07.2017 um 18:58 schrieb Matt Zagrabelny: > > On Wed, Jul 12, 2017 at 11:47 AM, Michael Biebl > > wrote: > > > > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > > My finger memory will still type

Re: Naming of network devices - how to improve it in buster

Am 12.07.2017 um 18:58 schrieb Matt Zagrabelny: > > > On Wed, Jul 12, 2017 at 11:47 AM, Michael Biebl > wrote: > > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > My finger memory will still type tcpdump -i eth0 before the brain can > >

Re: Naming of network devices - how to improve it in buster

On Wed, Jul 12, 2017 at 11:47 AM, Michael Biebl wrote: > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > My finger memory will still type tcpdump -i eth0 before the brain can > > intervene ten years from now. > > thankfully tcpdump (and lots of other tools) have nice shell

Re: Naming of network devices - how to improve it in buster

Am 12.07.2017 um 17:35 schrieb Marc Haber: > My finger memory will still type tcpdump -i eth0 before the brain can > intervene ten years from now. thankfully tcpdump (and lots of other tools) have nice shell completion. tcpdump -i works great her. -- Why is it that all of the instruments

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 15:20:41 +0200, Michael Biebl wrote: >Am 11.07.2017 um 12:14 schrieb Guus Sliepen: >> Ok, it should be clear now that the new way of naming interfaces is not >> ideal, but the older ways weren't either. Let's have a look at what we >> want: >> >> - A simple

Re: Naming of network devices - how to improve it in buster

Nikolaus Rath writes ("Re: Naming of network devices - how to improve it in buster"): > I wonder if anyone actually uses /dev/disk/by-path? $ grep path /etc/fstab /dev/disk/by-path/pci-:3b:00.0-platform-rtsx_pci_sdmmc.0-part1/media/sd autorw,user,noauto 0 0 $ ^ from my

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 15:20:41 +0200 Michael Biebl wrote: > Am 11.07.2017 um 12:14 schrieb Guus Sliepen: > > Ok, it should be clear now that the new way of naming interfaces is not > > ideal, but the older ways weren't either. Let's have a look at what we > > want: > > > > - A

Re: Naming of network devices - how to improve it in buster

On Jul 11 2017, Simon McVittie wrote: > On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote: >> I got to ask: Why? We do not have stable names for e.g. disks. Why do >> we need it for network devices? > > We do have stable names for disks: look in /dev/disk/by-* and you'll

Re: Naming of network devices - how to improve it in buster

On Tue, Jul 11, 2017 at 01:45:25PM +0200, Bjørn Mork wrote: > The remaining problem is to make ifupdown do device matching on other > (and hopefully more stable) attributes than the device name. This is not impossible to do. I actually have some code to make ifupdown use interface matching, I'm

Re: Naming of network devices - how to improve it in buster

On Tue, Jul 11, 2017 at 10:12 AM, Samuel Thibault wrote: > Matt Zagrabelny, on mar. 11 juil. 2017 09:53:58 -0500, wrote: > > Relatedly, network device name lengths are limited to the length of > some > > arbitrarily-sized struct field in the kernel ABI, > > > >

Re: Naming of network devices - how to improve it in buster

Matt Zagrabelny, on mar. 11 juil. 2017 09:53:58 -0500, wrote: > Relatedly, network device name lengths are limited to the length of some > arbitrarily-sized struct field in the kernel ABI, > > Feature request to bump the size of of interface names struct? Any reason to > not do so? One

Re: Naming of network devices - how to improve it in buster

Simon McVittie, on mar. 11 juil. 2017 15:18:26 +0100, wrote: > Network devices are (as far as I know) the only class of device managed by > udev that is not backed by a device node, which means udev cannot provide > multiple equivalent names for the same device, Couldn't that be what should be

Re: Naming of network devices - how to improve it in buster

On Jul 11 2017, Michael Biebl wrote: > Am 11.07.2017 um 12:14 schrieb Guus Sliepen: >> Ok, it should be clear now that the new way of naming interfaces is not >> ideal, but the older ways weren't either. Let's have a look at what we >> want: >> >> - A simple name for systems

Re: Naming of network devices - how to improve it in buster

On Tue, Jul 11, 2017 at 9:18 AM, Simon McVittie wrote: > On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote: > > I got to ask: Why? We do not have stable names for e.g. disks. Why do > > we need it for network devices? > > We do have stable names for disks: look in

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 at 13:45:25 +0200, Bjørn Mork wrote: > I got to ask: Why? We do not have stable names for e.g. disks. Why do > we need it for network devices? We do have stable names for disks: look in /dev/disk/by-* and you'll see a bewildering variety of ways to refer to the same disk or

Re: Naming of network devices - how to improve it in buster

Am 11.07.2017 um 12:14 schrieb Guus Sliepen: > Ok, it should be clear now that the new way of naming interfaces is not > ideal, but the older ways weren't either. Let's have a look at what we > want: > > - A simple name for systems with a single Ethernet and/or Wireless > interface (the simple

Re: Naming of network devices - how to improve it in buster

On Tue, 11 Jul 2017 12:14:59 +0200 Guus Sliepen wrote: > > So, what can we do to improve the situation and get the best of both > worlds? > systemd.link(5) describes a NamePolicy option for interface names. I would suggest to introduce a new policy "keep" to stick with the

Re: Naming of network devices - how to improve it in buster

Guus Sliepen writes: > Ok, it should be clear now that the new way of naming interfaces is not > ideal, but the older ways weren't either. Let's have a look at what we > want: > > - A simple name for systems with a single Ethernet and/or Wireless > interface (the simple