So everyone inside home network can reach the Internet thanks to NAT translation described in SOHO #004 and reach now their favorite Internet service by name thanks for SOHO #005.
Requirement- Basic Linux/Unix knowledge
- Service provider networking knowledge
|  Image Modified
|
Overview
In the previous article during the verification we assume to have one host connected to a subnetwork cascaded behind SOHO router@sdn6. However, we did not described how the host could get connectivity.
...
[ SOHO #006 ] - "Do you need an IP ?"
| Expand |
|---|
| title | Configure DHCPv4 serverinterface sdn6, gateway for 192.168.136.0/24 subnet |
|---|
|
First step, configure sdn6 and bind it to VRF inet. few considerations: - sdn6 has ipv4 192.168.136.1 manually configured
- sdn6 will act as gateway for all connected host in subnetwork 192.168.136.0/24
- In SOHO #004 , 192.168.136.0/24 NAT is already taken into account
| Code Block |
|---|
| language | bash |
|---|
| theme | Midnight |
|---|
| title | SOHO router DHCP server in VRF inet |
|---|
| conf t
interface sdn6
mtu 1500
vrf forwarding inet
ipv4 address 192.168.136.1 255.255.255.0
no shutdown
no log-link-change
exit
! |
|
| Expand |
|---|
| title | Configure DHCPv4 server |
|---|
|
Second step, configure a DHCPv4 server@ SOHO router | Code Block |
|---|
| language | bash |
|---|
| theme | Midnight |
|---|
| title | SOHO router DHCP server in VRF inet |
|---|
| conf t
server dhcp4 dh4-16
pool 192.168.136.3 192.168.136.254
gateway 192.168.136.1
netmask 255.255.255.0
dns-server 192.168.254.1
domain-name local
interface sdn6
vrf inet
exit
! |
In this case DHCPv4 will allocate IPv4 address: - from a pool going from 192.168.136.3 → 192.168.136.254
- All host will set their gateway to 192.168.136.1 (which is SOHO@sdn6)
- All connected host to sdn6 subnet will get an IP from pool within 192.168.136.0/24 subnet
- All hosts will also consider SOHO@192.168.254.1 as DNS server as we implemented in SOHO #005
- And we bind this DHCPv4 to interface sdn6 (without binding DHCP request coming from all interface belonging to VRF inet will be processed)
- lastly DHCPv4 server will act into VRF inet only
|
...
| Tip |
|---|
| title | RARE validated design: [ SOHO #005 ] - key take-away |
|---|
|
In this example the key take-away are: - DHCP is available for IPv4 and IPv6
- DHCP here is bind bound to an interface so rogue DHCP request coming from any router interface other than the speficied interface won't be honoured
- Feel free to explore all DHCP options propose by RARE/freeRouter
|
...