Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux_router:ipoe [2022-12-29 Thu wk52 16:23] – [ISP IPoE DHCP Setup Notes] baumkplinux_router:ipoe [2023-04-30 Sun wk17 17:43] (current) – external edit 127.0.0.1
Line 1: Line 1:
 {{tag>linux router bridged modem ISP IPoE mtu dns dhcp}} {{tag>linux router bridged modem ISP IPoE mtu dns dhcp}}
- =====ISP IPoE DHCP Setup Notes=====+=====ISP IPoE DHCP Setup Notes=====
 Notes on Setting up a Linux router for IPoE DHCP instead of PPPoE. Notes on Setting up a Linux router for IPoE DHCP instead of PPPoE.
  
Line 34: Line 34:
 So the networkd builtin dhcpd would seem to be functional.  So the networkd builtin dhcpd would seem to be functional. 
  
-The ''networkctl status eno1''++++-| +The ''networkctl status eno1'' 
-<code>2: eno1                                                                      +++++-|<code>2: eno1                                                                      
                      Link File: /usr/lib/systemd/network/99-default.link                      Link File: /usr/lib/systemd/network/99-default.link
                   Network File: /run/systemd/network/10-netplan-eno1.network                   Network File: /run/systemd/network/10-netplan-eno1.network
Line 61: Line 61:
                                 8.8.4.4                                 8.8.4.4
                DHCP4 Client ID: IAID:0xb6220feb/DUID                DHCP4 Client ID: IAID:0xb6220feb/DUID
-             DHCP6 Client DUID: DUID-EN/Vendor:0000ab112278b955a63a0f690000</code>+             DHCP6 Client DUID: DUID-EN/Vendor:0000ab112278b955a63a0f690000</code>++++
  
-===dhclient=== +====dhclient==== 
-The following dhclient commands are used to manual control dhcp connections.  Note however this does not work with the built-in systemd-networkd dhcpd functionality (see man systemd-networkd, networkctl and systemd.netdev). ++++TLDR:|+The following dhclient commands are used to manual control dhcp connections.  Note however this does not work with the built-in systemd-networkd dhcpd functionality (see man systemd-networkd, networkctl and systemd.netdev).  
 +++++tldr:|
   *To remove existing connected dhcp leased connections on eno1: ''sudo dhclient -r eno1'', note this also seems to remove static IP addresses.   *To remove existing connected dhcp leased connections on eno1: ''sudo dhclient -r eno1'', note this also seems to remove static IP addresses.
   *It is under stop the ''-x'' removes the local dhcp connection, but does not contact the upstream DHCP serve to remove lease, e.g. ''sudo dhclient -x eno1''    *It is under stop the ''-x'' removes the local dhcp connection, but does not contact the upstream DHCP serve to remove lease, e.g. ''sudo dhclient -x eno1'' 
   *To manual request a dhcp lease connection on eno1: ''sudo dhclient -4 eno1'' , the ''-4'' flag restricts operation to IPv4.    *To manual request a dhcp lease connection on eno1: ''sudo dhclient -4 eno1'' , the ''-4'' flag restricts operation to IPv4. 
-++++ 
  
 ===dhclient@.service=== ===dhclient@.service===
-''sudo vim /etc/systemd/system/dhclient@.service'' ++++ dhclient@.service|+ 
 +''sudo vim /etc/systemd/system/dhclient@.service''
 <code> <code>
 [Unit] [Unit]
Line 95: Line 96:
 ++++ ++++
  
-===Firewall Modifications===+====Firewall Modifications====
 When using pppoe a separate device is created that can be used to filter against.  When using IPoE with dhcp same device reference is shared by the IPoE WAN link and the modem LAN web page link.  My modem is setup at 192.168.5.1. The fire wall needs to be modified to consider this shared device instead of separate one. Other than changing the $wan reference from ppp1 to eno1 the postrouting to the modem needs to be made IP range specific. ++++ e.g.| When using pppoe a separate device is created that can be used to filter against.  When using IPoE with dhcp same device reference is shared by the IPoE WAN link and the modem LAN web page link.  My modem is setup at 192.168.5.1. The fire wall needs to be modified to consider this shared device instead of separate one. Other than changing the $wan reference from ppp1 to eno1 the postrouting to the modem needs to be made IP range specific. ++++ e.g.|
 <code> <code>
     ip saddr 192.168.1.0/24 ip daddr 192.168.5.0/24 oifname "eno1" counter packets 68 bytes 4080 snat to 192.168.5.2     ip saddr 192.168.1.0/24 ip daddr 192.168.5.0/24 oifname "eno1" counter packets 68 bytes 4080 snat to 192.168.5.2
     ip saddr 192.168.6.0/24 ip daddr 192.168.5.0/24 oifname "eno1" counter packets 0 bytes 0 snat to 192.168.5.2     ip saddr 192.168.6.0/24 ip daddr 192.168.5.0/24 oifname "eno1" counter packets 0 bytes 0 snat to 192.168.5.2
- 
 </code> ++++ </code> ++++
- 
- 
  
  
  
  <-  linux_router:ppp|Prev page ^ linux_router:start|Start page ^ linux_router:netfilter|Next page ->  <-  linux_router:ppp|Prev page ^ linux_router:start|Start page ^ linux_router:netfilter|Next page ->