Re: [systemd-devel] Disabling 'Predictable Network Interface Names'

2017-03-07 Thread Lucas Ventura Carro
Hello Jan,

2017-03-07 9:59 GMT+01:00 Jan Synacek :
> check out the official Red Hat documentation [1] on how to disable the naming
scheme.

Doing first or third option *only* it is not working.

Hello Martin,

2017-03-07 10:01 GMT+01:00 Martin Pitt :
> Did you rebuild the initrd after that? Without that, it won't work indeed.

After rebuilding ramfs[1], it works :)
I forgot to ask in my first email if I was not doing any extra step which I
didn't know :)

Thanks both for fast replies,

  [1]: https://sites.google.com/site/syscookbook/rhel/rhel-kernel-rebuild

--
Lucas


2017-03-07 10:01 GMT+01:00 Martin Pitt :

> Hello Lucas,
>
> Lucas Ventura Carro [2017-03-07  9:25 +0100]:
> > (1) Creating a symlink
> > (2) Changing a kernel boot parameter
> >
> > But, using option (1) doesn't work, and I'm still having predictable
> names.
>
> Did you rebuild the initrd after that? Without that, it won't work indeed.
>
> Martin
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling 'Predictable Network Interface Names'

2017-03-07 Thread Jan Synacek
On Tue, Mar 7, 2017 at 9:25 AM, Lucas Ventura Carro
 wrote:
> Hello,
>
> I've recently installed a CentOS 7 minimal ISO[1], where I found the new
> Predictable Network Interface Naming strategy enabled.
>
> But in my current environment this naming strategy is not viable, and I'd
> like to get back to old _unpredictable_ strategy for all the interfaces. So
> according to documentation on how to disable[2] there are 2 options:
> (1) Creating a symlink
> (2) Changing a kernel boot parameter
>
> But, using option (1) doesn't work, and I'm still having predictable names.
> It is a CentOS 7 issue? Because '/etc/systemd/network' folder did not
> existed in this clean install, I had to create myself.
> Inspecting the '/lib/udev/rules.d/80-net-name-slot.rules' will disable
> predictable names only if kernel boot param is present.

Hi,

check out the official Red Hat documentation [1] on how to disable the
naming scheme. If what's described there doesn't work, please, file a
bug report.

[1] 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Disabling_Consistent_Network_Device_Naming.html

Cheers,
-- 
Jan Synacek
Software Engineer, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling 'Predictable Network Interface Names'

2017-03-07 Thread Martin Pitt
Hello Lucas,

Lucas Ventura Carro [2017-03-07  9:25 +0100]:
> (1) Creating a symlink
> (2) Changing a kernel boot parameter
> 
> But, using option (1) doesn't work, and I'm still having predictable names.

Did you rebuild the initrd after that? Without that, it won't work indeed.

Martin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] Disabling 'Predictable Network Interface Names'

2017-03-07 Thread Lucas Ventura Carro
Hello,

I've recently installed a CentOS 7 minimal ISO[1], where I found the new
Predictable Network Interface Naming strategy enabled.

But in my current environment this naming strategy is not viable, and I'd
like to get back to old _unpredictable_ strategy for all the interfaces. So
according to documentation on how to disable[2] there are 2 options:
(1) Creating a symlink
(2) Changing a kernel boot parameter

But, using option (1) doesn't work, and I'm still having predictable names.
It is a CentOS 7 issue? Because '/etc/systemd/network' folder did not
existed in this clean install, I had to create myself.
Inspecting the '/lib/udev/rules.d/80-net-name-slot.rules' will disable
predictable names only if kernel boot param is present.

Thanks!

  [1]:
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1611.iso
  [2]:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/#idontlikethishowdoidisablethis

--
Lucas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-14 Thread Sylvain Pasche

On 2016-11-14 20:47, Lennart Poettering wrote:

On Mon, 14.11.16 20:35, Sylvain Pasche (spas...@spasche.net) wrote:


On 2016-11-14 15:14, Lennart Poettering wrote:
>
> Hmm, I figure this would be much better, no:
>
>  ln -s /dev/null /etc/systemd/network/99-default.link
>
> Wouldn't that work to for you?

Hi,

Yes, that works for me and looks better indeed.

Do you want to update the wiki, or should this need more testing?


Updated.

Lennart


Perfect, thanks!

Cheers,
Sylvain
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-14 Thread Lennart Poettering
On Mon, 14.11.16 20:35, Sylvain Pasche (spas...@spasche.net) wrote:

> On 2016-11-14 15:14, Lennart Poettering wrote:
> > 
> > Hmm, I figure this would be much better, no:
> > 
> >  ln -s /dev/null /etc/systemd/network/99-default.link
> > 
> > Wouldn't that work to for you?
> 
> Hi,
> 
> Yes, that works for me and looks better indeed.
> 
> Do you want to update the wiki, or should this need more testing?

Updated.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-14 Thread Sylvain Pasche

On 2016-11-14 04:48, Andrei Borzenkov wrote:

14.11.2016 00:51, Sylvain Pasche пишет:

Hi,

On the Predictable Network Interface Names wiki page [1], one of the 
option for disabling predictable network interface names is to mask 
the 80-net-setup-link.rules udev rule.


This has a side effect of somewhat breaking systemd-network: 
net_setup_link builtin is not run and the ID_NET_DRIVER udev property 
is not set on the interface.
Consequently, the .network files that match against a driver (such as 
/usr/lib/systemd/network/80-container-ve.network) don't pick up the 
interface.


I encountered that issue when trying to use --network-veth with 
systemd-nspawn on the Fedora cloud image (where 
80-net-setup-link.rules is masked). In this case, network is not 
available in the container and it can be tricky to understand why.


So I would suggest to update that wiki page. Here's an alternative for 
udev:
  cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > 
/etc/udev/rules.d/80-net-setup-link.rules


yuck. Does net.ifnames=0 not work for you?


Hi,

Option 3 works, but the goal here was to find an alternative for option 
1.

Lennart found a better suggestion for that.

Cheers,
Sylvain
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-14 Thread Sylvain Pasche

On 2016-11-14 15:14, Lennart Poettering wrote:


Hmm, I figure this would be much better, no:

 ln -s /dev/null /etc/systemd/network/99-default.link

Wouldn't that work to for you?


Hi,

Yes, that works for me and looks better indeed.

Do you want to update the wiki, or should this need more testing?

Then I can open a ticket to update Fedora Cloud images.

Cheers,
Sylvain
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-14 Thread Lennart Poettering
On Sun, 13.11.16 22:51, Sylvain Pasche (spas...@spasche.net) wrote:

> Hi,
> 
> On the Predictable Network Interface Names wiki page [1], one of the option 
> for disabling predictable network interface names is to mask the 
> 80-net-setup-link.rules udev rule.
> 
> This has a side effect of somewhat breaking systemd-network: net_setup_link 
> builtin is not run and the ID_NET_DRIVER udev property is not set on the 
> interface.
> Consequently, the .network files that match against a driver (such as 
> /usr/lib/systemd/network/80-container-ve.network) don't pick up the interface.
> 
> I encountered that issue when trying to use --network-veth with 
> systemd-nspawn on the Fedora cloud image (where 80-net-setup-link.rules is 
> masked). In this case, network is not available in the container and it can 
> be tricky to understand why.
> 
> So I would suggest to update that wiki page. Here's an alternative for udev:
>   cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > 
> /etc/udev/rules.d/80-net-setup-link.rules

Hmm, I figure this would be much better, no:

 ln -s /dev/null /etc/systemd/network/99-default.link

Wouldn't that work to for you?

Lennart

-- 
Lennart Poettering, Red Hat

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-13 Thread Andrei Borzenkov
14.11.2016 00:51, Sylvain Pasche пишет:
> Hi,
> 
> On the Predictable Network Interface Names wiki page [1], one of the option 
> for disabling predictable network interface names is to mask the 
> 80-net-setup-link.rules udev rule.
> 
> This has a side effect of somewhat breaking systemd-network: net_setup_link 
> builtin is not run and the ID_NET_DRIVER udev property is not set on the 
> interface.
> Consequently, the .network files that match against a driver (such as 
> /usr/lib/systemd/network/80-container-ve.network) don't pick up the interface.
> 
> I encountered that issue when trying to use --network-veth with 
> systemd-nspawn on the Fedora cloud image (where 80-net-setup-link.rules is 
> masked). In this case, network is not available in the container and it can 
> be tricky to understand why.
> 
> So I would suggest to update that wiki page. Here's an alternative for udev:
>   cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > 
> /etc/udev/rules.d/80-net-setup-link.rules

yuck. Does net.ifnames=0 not work for you?

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] Disabling Predictable Network Interface Names by masking 80-net-setup-link.rules

2016-11-13 Thread Sylvain Pasche
Hi,

On the Predictable Network Interface Names wiki page [1], one of the option for 
disabling predictable network interface names is to mask the 
80-net-setup-link.rules udev rule.

This has a side effect of somewhat breaking systemd-network: net_setup_link 
builtin is not run and the ID_NET_DRIVER udev property is not set on the 
interface.
Consequently, the .network files that match against a driver (such as 
/usr/lib/systemd/network/80-container-ve.network) don't pick up the interface.

I encountered that issue when trying to use --network-veth with systemd-nspawn 
on the Fedora cloud image (where 80-net-setup-link.rules is masked). In this 
case, network is not available in the container and it can be tricky to 
understand why.

So I would suggest to update that wiki page. Here's an alternative for udev:
  cat /usr/lib/udev/rules.d/80-net-setup-link.rules | grep -v NAME= > 
/etc/udev/rules.d/80-net-setup-link.rules

Sylvain

[1] 
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel