-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David W. Hodgins escreveu:
> On Fri, 20 May 2022 13:57:28 -0400, Doug Laidlaw
> <laidlaws@hotkey.net.au> wrote:
>
>> On 5/5/22 06:14, David W. Hodgins wrote:
>>> As network manager doesn't support bridging (drakx tools do)
>>> and bridging is required for things like xen, I've personally
>>> switched to systemd-networkd which supports both ipv6 and
>>> bridging, but requires manually creating/editing the config
>>> files.
>>>
>> There is a tutorial for setting up systemd-networkd (on Ubuntu)
>> at :
>>
>> https://hesamyan.medium.com/switching-from-networkmanager-to-systemd-
networkd-dcbda0b15056
>>
>>
>>
>>
I just found it, and haven't tried it yet. Ubuntu is not as heavily
>> customized as Linux Mint, meaning that I don't have to run
>> scripts intended for Mint alone.
>
> Since I only have one ethernet card in my system, I've added
> net.ifnames=0 to the kernel cmdline. That way my nic is eth0 rather
> then enp7s0.
>
> I've set my router's lan address is 192.168.10.11 and use a /16
> instead of the normal /24.
>
> I had problems getting static for ipv4 with dynamic for ipv6
> working, so I have dynamic for both and the static for ipv4.
>
> On my rpi 4b where I don't run xen ...
>
> $ cat /etc/systemd/network/10-eth0.network [Match] Name=eth0
>
> [Network] Description=LAN_NIC DNS=::1 DNS=192.168.10.2
> DNS=192.168.10.101 DNS=8.8.8.8 Domains=rp4.hodgins.homeip.net
> DHCP=no LLMNR=false IPv6AcceptRA=yes
>
> [Address] Address=192.168.10.101/16
>
> [Route] Gateway=192.168.10.11
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0
> BOOTPROTO=static IPADDR=192.168.10.101 NETMASK=255.255.0.0
> GATEWAY=192.168.10.11 ONBOOT=yes METRIC=5 MII_NOT_SUPPORTED=yes
> USERCTL=yes DNS1=192.168.10.2 DNS1=192.168.10.101 RESOLV_MODS=no
> LINK_DETECTION_DELAY=1 IPV6INIT=yes IPV6TO4INIT=no ACCOUNTING=no
> NM_CONTROLLED=no NOZEROCONF=yes PERSISTENT_DHCLIENT=yes
>
> On my main system, where I also need bridging for xen ...
>
> $ cat /etc/systemd/network/eth0.network [Match] Name=e*
>
> [Network] Bridge=xenbr
>
> $ cat /etc/systemd/network/xenbr.netdev [NetDev] Name=xenbr
> Kind=bridge
>
> $ cat /etc/systemd/network/xenbr.network [Match] Name=xenbr
>
> [Network] Description=LAN_NIC DNS=::1 DNS=127.0.0.1 DNS=8.8.8.8
> Domains=x3.hodgins.homeip.net DHCP=yes LLMNR=false
> IPv6AcceptRA=yes
>
> [Address] Address=192.168.10.2/16
>
> [Route] Gateway=192.168.10.11
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0
> BOOTPROTO=dhcp ONBOOT=yes
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-xenbr DEVICE=xenbr
> BOOTPROTO=dhcp ONBOOT=yes

These weird net names have already bored me a lot until someone
passes me the following text:

You basically have three options:

1 - You disable the assignment of fixed names, so that the
unpredictable kernel names are used again. For this, simply mask
udev's .link file for the default policy: ln -s /dev/null
/etc/systemd/network/99-default.link

2 - You create your own manual naming scheme, for example by naming
your interfaces "internet0", "dmz0" or "lan0". For that create your
own .link files in /etc/systemd/network/, that choose an explicit name
or a better naming scheme for one, some, or all of your interfaces.
See systemd.link(5) for more information.

3 - You pass the net.ifnames=0 on the kernel command line.

- --
Abraços
Gilberto F da Silva
Mageia release 9 (Official) for x86_64
Kernel: 6.4.9-desktop-2.mga9
Desktop: KDE
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCZPHi5gAKCRAnG6Ba0yEb
DnyWAJ4lzHnwkcgOvpLFd46FDfHNvV9ZJACcDhtApFUjwZ4MTuEDcpGE/PpNP+8=
=Bn2W
-----END PGP SIGNATURE-----