Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
linux_router:network [2023-07-04 Tue wk27 19:38] – [Router Configuration Network Setup] 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 | # This file describes the network interfaces available on your system | ||
# and how to activate them. For more information, | # and how to activate them. For more information, | ||
- | | + | |
+ | | ||
+ | | ||
# The loopback network interface | # The loopback network interface | ||
auto lo | auto lo | ||
Line 25: | Line 27: | ||
# The WAN network interface | # 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) |
+ | # set up static | ||
+ | iface eno1:0 inet static | ||
address 192.168.5.2/ | address 192.168.5.2/ | ||
- | # broadcast 192.168.5.255 #is this require any more? | ||
# Then LAN networks are eno2 eno3 eno4 in bridged mode br1 | # Then LAN networks are eno2 eno3 eno4 in bridged mode br1 | ||
# on the 192.168.1.1 subnet | # on the 192.168.1.1 subnet | ||
- | auto br1 | + | auto br0 |
- | iface br1 inet static | + | iface br0 inet static |
bridge_ports eno2 eno3 eno4 | bridge_ports eno2 eno3 eno4 | ||
address 192.168.1.1/ | address 192.168.1.1/ | ||
- | | + | |
- | #netmask 255.255.255.0 #is this require any more? | + | |
- | # | + | |
- | dns-nameservers 192.168.1.1 | + | |
bridge_stp off # disable Spanning Tree Protocol | bridge_stp off # disable Spanning Tree Protocol | ||
#bridge_fd 9 # forwarding delay # use default? | #bridge_fd 9 # forwarding delay # use default? | ||
Line 66: | 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. | 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: | #hwaddress ether xx: | ||
+ | |||
+ | The " | ||
+ | |||
+ | 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? | ||
+ | |||
</ | </ | ||
++++ | ++++ |