Local-Address

This scenario shows how to configure a DHCP relay agent to forward DHCP requests. By default, the local-address option uses a custom local IP as source address for upstream traffic.

../../../../_images/local.svg

Test DHCP Relay With Local-Address

Description

This example shows how to configure the local-address option. This command can be used to set the source address for upstream traffic.

Scenario

Step 1: Set the following configuration in DUT0:

set interfaces dummy dum0 address 1.1.1.1/32
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24
set interfaces ethernet eth1 vif 200 address 20.0.0.2/24
set service dhcp-relay INS downstream-interface eth1.200
set service dhcp-relay INS local-address 1.1.1.1
set service dhcp-relay INS server 10.0.0.1
set service dhcp-relay INS upstream-interface eth0.100
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1:

set interfaces ethernet eth0 vif 100 address 10.0.0.1/24
set interfaces ethernet eth0 vif 100 traffic policy in LOGGER
set protocols static route 0.0.0.0/0 next-hop 10.0.0.2
set service dhcp-server shared-network dummy subnet 10.0.0.1/32
set service dhcp-server shared-network remote subnet 20.0.0.0/24 start 20.0.0.50 stop 20.0.0.50
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
set traffic policy LOGGER rule 1 log prefix DHCP_
set traffic policy LOGGER rule 1 selector UDP
set traffic selector UDP rule 1 destination port 67
set traffic selector UDP rule 1 protocol udp

Step 3: Set the following configuration in DUT2:

set interfaces ethernet eth0 vif 200 address dhcp
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 4: Ping IP address 10.0.0.1 from DUT0:

admin@DUT0$ ping 10.0.0.1 count 1 size 56 timeout 1
Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.242 ms

--- 10.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.242/0.242/0.242/0.000 ms

Step 5: Run command interfaces ethernet show at DUT2 and check if output contains the following tokens:

20.0.0.50
Show output
---------------------------------------------------------------------
  Name             IP Address           Admin  Oper  Vrf  Description
---------------------------------------------------------------------
    eth0  fe80::dcad:beff:feef:6c20/64  up     up
eth0.200  20.0.0.50/24                  up     up
          fe80::dcad:beff:feef:6c20/64
    eth1                                down   down

Step 6: Run command system journal show | cat at DUT1 and check if output matches the following regular expressions:

SRC=1.1.1.1 DST=10.0.0.1
Show output
Dec 03 12:57:33.285604 osdx systemd-journald[1705]: Runtime Journal (/run/log/journal/7b9b4b4f707a49f795f87bcc6955a259) is 1.3M, max 9.7M, 8.4M free.
Dec 03 12:57:33.287813 osdx systemd-journald[1705]: Received client request to rotate journal, rotating.
Dec 03 12:57:33.287871 osdx systemd-journald[1705]: Vacuuming done, freed 0B of archived journals from /run/log/journal/7b9b4b4f707a49f795f87bcc6955a259.
Dec 03 12:57:33.295822 osdx OSDxCLI[1924]: User 'admin' executed a new command: 'system journal clear'.
Dec 03 12:57:33.748805 osdx osdx-coredump[22026]: Deleting all coredumps in /opt/vyatta/etc/config/coredump...
Dec 03 12:57:33.758287 osdx OSDxCLI[1924]: User 'admin' executed a new command: 'system coredump delete all'.
Dec 03 12:57:35.370114 osdx OSDxCLI[1924]: User 'admin' entered the configuration menu.
Dec 03 12:57:35.447314 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set interfaces eth0.100 address 10.0.0.1/24'.
Dec 03 12:57:35.534260 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set service dhcp-server shared-network dummy subnet 10.0.0.1/32'.
Dec 03 12:57:35.605195 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set service dhcp-server shared-network remote subnet 20.0.0.0/24 start 20.0.0.50 stop 20.0.0.50'.
Dec 03 12:57:35.702025 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set protocols static route 0.0.0.0/0 next-hop 10.0.0.2'.
Dec 03 12:57:35.774095 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set traffic policy LOGGER rule 1 log prefix DHCP_'.
Dec 03 12:57:35.852342 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set traffic policy LOGGER rule 1 selector UDP'.
Dec 03 12:57:35.913320 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set traffic selector UDP rule 1 protocol udp'.
Dec 03 12:57:35.999128 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set traffic selector UDP rule 1 destination port 67'.
Dec 03 12:57:36.058096 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'set interfaces eth0.100 traffic policy in LOGGER'.
Dec 03 12:57:36.166606 osdx OSDxCLI[1924]: User 'admin' added a new cfg line: 'show working'.
Dec 03 12:57:36.331831 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0
Dec 03 12:57:36.359052 osdx (udev-worker)[22115]: Network interface NamePolicy= disabled on kernel command line.
Dec 03 12:57:37.020109 osdx systemd[1]: Started dhcpd@main.service - "DHCP Server Service instance main".
Dec 03 12:57:37.022292 osdx cfgd[1418]: [1924]Completed change to active configuration
Dec 03 12:57:37.024292 osdx dhcpd[22166]: Wrote 0 leases to leases file.
Dec 03 12:57:37.053020 osdx OSDxCLI[1924]: User 'admin' committed the configuration.
Dec 03 12:57:37.070643 osdx OSDxCLI[1924]: User 'admin' left the configuration menu.
Dec 03 12:57:37.115394 osdx dhcpd[22166]:
Dec 03 12:57:37.115405 osdx dhcpd[22166]: No subnet declaration for eth0 (no IPv4 addresses).
Dec 03 12:57:37.115408 osdx dhcpd[22166]: ** Ignoring requests on eth0.  If this is not what
Dec 03 12:57:37.115411 osdx dhcpd[22166]:    you want, please write a subnet declaration
Dec 03 12:57:37.115414 osdx dhcpd[22166]:    in your dhcpd.conf file for the network segment
Dec 03 12:57:37.115417 osdx dhcpd[22166]:    to which interface eth0 is attached. **
Dec 03 12:57:37.115420 osdx dhcpd[22166]:
Dec 03 12:57:37.127963 osdx dhcpd[22166]: Server starting service.
Dec 03 12:57:37.765195 osdx kernel: [DHCP_-1] ACCEPT IN=eth0.100 OUT= MAC=de:ad:be:ef:6c:10:de:ad:be:ef:6c:00:08:00:45:00:01:48 SRC=1.1.1.1 DST=10.0.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=8133 DF PROTO=UDP SPT=67 DPT=67 LEN=308
Dec 03 12:57:37.765316 osdx dhcpd[22166]: DHCPDISCOVER from de:ad:be:ef:6c:20 via 20.0.0.2
Dec 03 12:57:38.765631 osdx dhcpd[22166]: DHCPOFFER on 20.0.0.50 to de:ad:be:ef:6c:20 (osdx) via 20.0.0.2
Dec 03 12:57:38.766362 osdx kernel: [DHCP_-1] ACCEPT IN=eth0.100 OUT= MAC=de:ad:be:ef:6c:10:de:ad:be:ef:6c:00:08:00:45:00:01:48 SRC=1.1.1.1 DST=10.0.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=8365 DF PROTO=UDP SPT=67 DPT=67 LEN=308
Dec 03 12:57:38.766436 osdx dhcpd[22166]: DHCPREQUEST for 20.0.0.50 (10.0.0.1) from de:ad:be:ef:6c:20 (osdx) via 20.0.0.2
Dec 03 12:57:38.777670 osdx dhcpd[22166]: DHCPACK on 20.0.0.50 to de:ad:be:ef:6c:20 (osdx) via 20.0.0.2