On Saturday, 06-07-2024 at 14:51 David Christensen wrote:
On 7/5/24 19:06, Max Nikulin wrote:
On 7/5/24 21:14, George at Clug wrote:
Thank you for your replies.
The underlying issue appears to be that my old-school Linux console
network administration skills have been rendered obsolete by systemd
and
NetworkManager. I typically install Xfce when installing Debian,
and
the panel NetworkManager Applet has made it too easy to "monkey see,
monkey do" without understanding the details.
What I really need is a good book
Thanks for that question about books.
A 'book' ? What is a 'book' ??
I recall mother reading from such things when I was a child.
(so hard to keep a straight face and not be laughing as I try to
pretend that 'books' are old school, but sadly it is not far from the
truth. My children know not the age before 'the Internet and Google
were how to find knowledge', the idea of going to a library to
research though 'books' seem so foreign to them. Soon asking an AI
system for the answer will be the way, and Google and Internet
searching, will be thought of as historic research techniques.)
or document that explains the design
and implementation of networking with systemd and Network Manager on
modern Debian GNU/Linux systems. Recommendations?
Sadly I have not found any documentation (or books) for any thing
Linux. It seems to be a 'piecing together of random statements' from
comments and howtos on the Internet, and much personal
experimentation.
The closest to any systematic learning method I have seen would be Red
Hat certifications. Not that I have even done any.
As far as general networking books, CISCO certification books have
been useful to me, but I am not a good reader, and they are lengthy.
For Internet doco, see pages like
https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/configuring-virtual-machine-network-connections_configuring-and-managing-virtualization
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-bridge-using-nmcli-commands_configuring-a-network-
bridge
https://www.ibm.com/docs/en/linux-on-systems?topic=choices-kvm-default-nat-based-networking
https://wiki.libvirt.org/page/Libvirtd_and_dnsmasq
https://wiki.libvirt.org/page/Networking
David
If it helps, two things I have done is;
1) Set manual IP address in Network Manager so that it is managing the networking on my behalf. Particularly if I use a GUI, of which my
favourite for VMs is XFCE as it is lightweight and works well with
spice (that is not a Dune reference, btw). Network Manager can even do
bridges, though I have had issues on initial power on.
2) I have had success, uninstalling Network Manager and then
configuring /etc/network/interfaces.
Below are two examples from my own 'play' test environments.
Over time I have used bridging many times, so my VMs can be on the
same network as my other PCs, servers, etc. Bridges are not necessary
when all VMs are test VMs in their own private network running in the
same Hypervisor. Some times I have set up a route from my PCs' own
network to the Hypervisor's provided network for its VMs.
/etc/hosts
/etc/resolv.conf (Generated by NetworkManager, if
installed)
/etc/network/interfaces
Examples for Static IP addresses.
# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug enp1s0
iface enp1s0 inet static
address 192.168.100.101/24
gateway 192.168.100.1
# dns-* options are implemented by the resolvconf package, if
installed
dns-nameservers 192.168.100.1
dns-search tstenv.net
# cat /etc/resolv.conf
search tstenv.net
nameserver 192.168.100.1
$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug enp1s0
auto enp1s0
iface enp1s0 inet manual
iface enp1s0 inet6 manual
# bridge
auto brRed
iface brRed inet static
address 192.168.100.103/24
gateway 192.168.100.1
network 192.168.100.0
broadcast 192.168.100.255
bridge_ports enp1s0
bridge_stp off
bridge_fd 0
bridge_maxwait 0
# dns-* options are implemented by the resolvconf package, if
installed
dns-nameservers 192.168.100.1
dns-search tstenv.net
# bridge allow auto conf for ipv6
iface brRed inet6 auto
accept_ra 1
<html>
<head>
<style type="text/css">
body,p,td,div,span{
font-size:13px; font-family:Arial, Helvetica, sans-serif;
};
body p{
margin:0px;
}
</style>
</head>
<body>On Saturday, 06-07-2024 at 14:51 David Christensen wrote:<br>
> On 7/5/24 19:06, Max Nikulin wrote:<br>
> <snip><br>
> <br>
> On 7/5/24 21:14, George at Clug wrote:<br>
> <snip><br>
> <br>
> <br>
> Thank you for your replies.<br>
> <br>
> <br>
> The underlying issue appears to be that my old-school Linux console <br> > network administration skills have been rendered obsolete by systemd and <br>
> NetworkManager. I typically install Xfce when installing Debian, and <br>
> the panel NetworkManager Applet has made it too easy to "monkey see, <br> > monkey do" without understanding the details.<br>
> <br>
> <br>
> What I really need is a good book<br>
Thanks for that question about books. <br>
A 'book' ? What is a 'book' ??<br>
I recall mother reading from such things when I was a child.<br>
(so hard to keep a straight face and not be laughing as I try to pretend that 'books' are old school, but sadly it is not far from the truth. My children know not the age before 'the Internet and Google were how to find knowledge', the idea of going to a
library to research though 'books' seem so foreign to them. Soon asking an AI system for the answer will be the way, and Google and Internet searching, will be thought of as historic research techniques.)<br>
> or document that explains the design <br>
> and implementation of networking with systemd and Network Manager on <br> > modern Debian GNU/Linux systems. Recommendations?<br>
Sadly I have not found any documentation (or books) for any thing Linux. It seems to be a 'piecing together of random statements' from comments and howtos on the Internet, and much personal experimentation.<br>
The closest to any systematic learning method I have seen would be Red Hat certifications. Not that I have even done any.<br>
As far as general networking books, CISCO certification books have been useful to me, but I am not a good reader, and they are lengthy.<br>
For Internet doco, see pages like <br>
<a href="
https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface" target="_blank" class="normal-link">
https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface</a><br>
<a href="
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/configuring-virtual-machine-network-connections_configuring-and-managing-virtualization" target="_blank" class="normal-link">
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/configuring-virtual-machine-network-connections_configuring-and-managing-virtualization</a><br>
<a href="
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-bridge-using-nmcli-commands_configuring-a-
network-bridge" target="_blank" class="normal-link">
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/configuring-a-network-bridge_configuring-and-managing-networking#configuring-a-network-
bridge-using-nmcli-commands_configuring-a-network-bridge</a><br>
<a href="
https://www.ibm.com/docs/en/linux-on-systems?topic=choices-kvm-default-nat-based-networking" target="_blank" class="normal-link">
https://www.ibm.com/docs/en/linux-on-systems?topic=choices-kvm-default-nat-based-networking</a><br>
<a href="
https://wiki.libvirt.org/page/Libvirtd_and_dnsmasq" target="_blank" class="normal-link">
https://wiki.libvirt.org/page/Libvirtd_and_dnsmasq</a><br>
<a href="
https://wiki.libvirt.org/page/Networking" target="_blank" class="normal-link">
https://wiki.libvirt.org/page/Networking</a><br>
> <br>
> <br>
> David<br>
> <br>
> <br>
If it helps, two things I have done is;<br>
1) Set manual IP address in Network Manager so that it is managing the networking on my behalf. Particularly if I use a GUI, of which my favourite for VMs is XFCE as it is lightweight and works well with spice (that is not a Dune reference, btw). Network
Manager can even do bridges, though I have had issues on initial power on.<br>
2) I have had success, uninstalling Network Manager and then configuring /etc/network/interfaces. <br>
Below are two examples from my own 'play' test environments. <br>
Over time I have used bridging many times, so my VMs can be on the same network as my other PCs, servers, etc. Bridges are not necessary when all VMs are test VMs in their own private network running in the same Hypervisor. Some times I have
set up a route from my PCs' own network to the Hypervisor's provided network for its VMs.<br>
/etc/hosts <br>
/etc/resolv.conf (Generated by NetworkManager, if installed)<br>
/etc/network/interfaces<br>
Examples for Static IP addresses.<br>
# cat /etc/network/interfaces<br>
# This file describes the network interfaces available on your system<br>
# and how to activate them. For more information, see interfaces(5).<br>
source /etc/network/interfaces.d/*<br>
# The loopback network interface<br>
auto lo<br>
iface lo inet loopback<br>
# The primary network interface<br>
allow-hotplug enp1s0<br>
iface enp1s0 inet static<br>
address 192.168.100.101/24<br> gateway 192.168.100.1<br>
# dns-* options are implemented by the resolvconf package, if installed<br>
dns-nameservers 192.168.100.1<br> dns-search tstenv.net<br>
# cat /etc/resolv.conf<br>
search tstenv.net<br>
nameserver 192.168.100.1<br>
$ cat /etc/network/interfaces<br>
# This file describes the network interfaces available on your system<br>
# and how to activate them. For more information, see interfaces(5).<br>
source /etc/network/interfaces.d/*<br>
# The loopback network interface<br>
auto lo<br>
iface lo inet loopback<br>
# The primary network interface<br>
#allow-hotplug enp1s0<br>
auto enp1s0<br>
iface enp1s0 inet manual<br>
iface enp1s0 inet6 manual<br>
# bridge<br>
auto brRed<br>
iface brRed inet static<br>
address 192.168.100.103/24<br> gateway 192.168.100.1<br> network 192.168.100.0<br> broadcast 192.168.100.255<br> bridge_ports enp1s0<br> bridge_stp off<br> bridge_fd 0<br> bridge_maxwait 0<br> # dns-* options are implemented by the resolvconf package, if installed<br>
dns-nameservers 192.168.100.1<br> dns-search tstenv.net<br>
# bridge allow auto conf for ipv6<br>
iface brRed inet6 auto<br> accept_ra 1</body></html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)