Having an issue with DHCP Relay not working over an IPSec tunnel.
I've found a few previous posts and tried suggestions there to no avail.
This is only a temporary setup for a few months, so don't want to wasconte too much time on it, but would be nice to get working if possible. I'm currently using the DHCP server built-in to RouterOS on the "remote" site but would like to use the Windows 2008R2 DHCP server on the "main" site to serve the "remote" site via relay.
Setup is complicated by a bit of a "hack" I've had to do on the "remote" router to get the IPSec tunnel to come up, due to less than ideal config outside of my control.
Main site:
RB750 - PPPoE Client interface acts as gateway to Internet
Remote site:
RB750 - Ether1 interface acts as gateway configured as 192.168.0.250. This connects to another device which is 192.168.0.1 which then via NAT connects to the Internet.
To get the IPSec tunnel to come up, I have had to add the public IP address of the remote site into the RB750 as an additional IP address assigned to Ether1.
Default src-nat masquerade rule plus a src-nat rule of source 10.10.0.0/16 (remote site) destination 10.0.0.0/16 (one VLAN on main site) to 'accept'.
Tried also adding a src-nat rule of source <remote site public IP> destination 10.0.0.0/16 src-nat to-address 10.10.0.254, didn't work.
Any suggestions? As stated this is a temp setup only and will be redundant in a few months as this remote site will be replaced by another where a RB750GL will directly get a public IP via PPPoE client.