Differences

This shows you the differences between two versions of the page.

--- linux_router:network [2022-12-29 Thu wk52 16:05] – [ipv6 Hurricane Electric Setup notes] baumkp
+++ linux_router:network [2023-07-08 Sat wk27 10:13] (current) – [Debian / Ubuntu Network - Interface Setup] baumkp
@@ Line 19: / Line 19: @@
   # 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/*
+  source /etc/network/interfaces.d/*
   # The loopback network interface
   auto lo
@@ Line 25: / Line 27: @@
   # The WAN network interface
-  auto eno1
+  auto eno1 eno1:0
-  iface eno1 inet static
+  iface eno1 inet dhcp
-    # set up ip address to access modem web page on WAN NIC
+  # dhcp for IP/DHCP WAN (static? for PPPOE)
-    address 192.168.5.2
+  # set up static ip address to access modem web page on WAN NIC
-    netmask 255.255.255.0
+  iface eno1:0 inet static
-    broadcast 192.168.5.255
+    address 192.168.5.2/24
   # Then LAN networks are eno2 eno3 eno4 in bridged mode br1
   # on the 192.168.1.1 subnet
-  auto br1
+  auto br0
-  iface br1 inet static
+  iface br0 inet static
     bridge_ports eno2 eno3 eno4
-    address 192.168.1.1
+    address 192.168.1.1/24
-    network 192.168.1.0
+    dns-nameservers 192.168.1.14 192.168.1.2 9.9.9.9
-    netmask 255.255.255.0
-    broadcast 192.168.1.255
-    dns-nameservers 192.168.1.1
     bridge_stp off  # disable Spanning Tree Protocol
-    bridge_fd 9  # forwarding delay
+    #bridge_fd 9  # forwarding delay  # use default?
-    bridge_hello 5
+    #bridge_hello 5  # use default?
-    bridge_maxage 60
+    #bridge_maxage 60  # use default?
 </code>
 ++++
@@ Line 67: / Line 66: @@
 Each Ethernet hardware connection has its own defined unique MAC number, no need to define another. If Ethernet bonding were being used there maybe a need to use this stanza.
   #hwaddress ether xx:xx:xx:xx:xx:xx
-</code>
-++++
+The "modern" way to specify static ip address as address 192.168.1.0/24'' this automatically assigns the network, netmask and broadcast addresses.
+The old fashion way was to manual assign as follows:
+address 192.168.1.32
+network 192.168.1.0
+netmask 255.255.255.0
+broadcast 192.168.1.255
+Perhaps this is still required in special cases?
+</code>
+++++
+Note:
+  *Use ''ip a'' and ''ip r'' to analyse current network configuration
+  *Use ''sudo journalctl -xeu networking'' to check any errors on networking
+References:
+  *[[https://wiki.debian.org/NetworkConfiguration|NetworkConfiguration]] see section on Bridging
+  *[[https://manpages.debian.org/bookworm/bridge-utils/bridge-utils-interfaces.5.en.html|/ bookworm / bridge-utils / bridge-utils-interfaces(5)]]
 =====Network - Netplan Setup=====
@@ Line 107: / Line 120: @@
   ethernets:
     eno1: #start for pppoe and setup modem IP access
-      dhcp4: no
+      dhcp4: yes # yes for dhcp, no for pppoe
-      dhcp6: no
+      dhcp6: yes # yes for dhcp, no for pppoe or not required
       addresses:
          - [192.168.5.2/24] #Access to the modem web interface
@@ Line 143: / Line 156: @@
       mode: sit
       remote: 216.218.142.50
-      local: 112.213.222.38
+      local: 207.7.254.238
       addresses:
          - "2001:470:1f2c:10d::2/64"
@@ Line 162: / Line 175: @@
 It is important that the network/interfaces method is disable or strange difficult to diagnose network affect may happen.
 Basically ensure that all items in file /etc/network/interfaces are commented out. For example:
-++++''sudo vim /etc/netplan/network.yaml''|
+++++''sudo vim /etc/network/interfaces''|
 <code>
 # This file describes the network interfaces available on your system
@@ Line 247: / Line 260: @@
 </code> ++++
 Currently Ubuntu (20.04) defaults to netplan.io, where as Debian 10 does not. So in Debian the ''/etc/network/interfaces'' need to be disabled, if using netplan. Where as in Ubuntu the auto configuration needs to be disabled.
+I am using Debian 12 now and am moving back to /etc/network/interfaces for network configuration.  As the DHCP and DNS server now run in a VM/Docker containers, this simplifies settings on the main router functions.
 I wrote 2 scripts to switch between configuration:
 ++++ ''vim tononrouter.sh'' |
 <code>
-systemctl disable bind9
+#systemctl disable bind9
-systemctl disable isc-dhcp-server
+#systemctl disable isc-dhcp-server
-mv /etc/netplan/50-cloud-init.yaml.old /etc/netplan/50-cloud-init.yaml
+#systemctl disable nftables
-mv /etc/netplan/network.yaml /etc/netplan/network.yaml.old
+#systemctl disable pppoe
+#mv /etc/netplan/50-cloud-init.yaml.old /etc/netplan/50-cloud-init.yaml
+#mv /etc/netplan/network.yaml /etc/netplan/network.yaml.old
+ln -sf /etc/nftables.conf.orig /etc/nftables.conf
+#ln -sf /etc/nftables.conf.router /etc/nftables.conf
+ln -sf /etc/network/interfaces.orig /etc/network/interfaces
+#ln -sf /etc/network/interfaces.router /etc/network/interfaces
 </code> ++++
@@ Line 261: / Line 282: @@
 ++++ ''vim torouter.sh'' |
 <code>
-systemctl enable bind9
+#systemctl enable bind9
-systemctl enable isc-dhcp-server
+#systemctl enable isc-dhcp-server
-mv /etc/netplan/50-cloud-init.yaml /etc/netplan/50-cloud-init.yaml.old
+#systemctl enable nftables
-mv /etc/netplan/network.yaml.old /etc/netplan/network.yaml
+#systemctl enable pppoe
+#mv /etc/netplan/50-cloud-init.yaml  /etc/netplan/50-cloud-init.yaml.old
+#mv /etc/netplan/network.yaml.old  /etc/netplan/network.yaml
+#mv /etc/netplan/50-cloud-init.yaml.old /etc/netplan/50-cloud-init.yaml
+#mv /etc/netplan/network.yaml /etc/netplan/network.yaml.old
+#ln -sf /etc/nftables.conf.orig /etc/nftables.conf
+ln -sf /etc/nftables.conf.router /etc/nftables.conf
+#ln -sf /etc/network/interfaces.orig /etc/network/interfaces
+ln -sf /etc/network/interfaces.router /etc/network/interfaces
 </code> ++++
 Use ''sudo bash tonrouter.sh'' to move to non router configuration.