The layout is simple:
- VyOS: 10.10.51.1/30, has DHCP server for 10.10.200.0/24
- Switch: 10.10.51.2/30, 10.10.200.1/24 -> router for that subnet and dhcp relay to VyOS
There are a few major issues right now.
1. We force the use of `shared-network`. This will make it impossible for VyOS to be a DHCP Server for a relay
2. We require too much information from the CLI to allow this setup to work
In the follow config, I've inserted comments to show what needs to happen:
```
### This line needs to be deleted. Otherwise isc-dhcp won't start up and complain about the 10.10.200.0/24 not existing on any interface
shared-network VPNSUBNET {
### The CLI won't let you create a line that looks like this, because there's no DHCP ranges or mappings. But to be a DHCP server for a relay, it needs to exist thusly, on the interface that's facing the device doing the relay.
subnet 10.10.51.0 netmask 255.255.255.0 { }
subnet 10.10.200.0 netmask 255.255.255.0 {
option domain-name-servers 10.3.1.254, 10.3.1.253;
option routers 10.10.200.1;
default-lease-time 86400;
max-lease-time 86400;
range 10.10.200.100 10.10.200.200;
}
### As the closing bracket, this line needs to be deleted.
}
```
When fixed, I think this should be backport candidate