i assume you use hotspot captive portal on the central router while the remote sites only handle connection, right?
in this configuration, you need to setup like this:
- create a bridge on core router, set ip address, dhcp and hotspot to this bridge. make sure the hotspot is working on this bridge, you may use direct conenct on ethernet interface assigned to the bridge to test it.
- create ppp profile with bridge assigned to this bridge, like this:
/ppp profile
add bridge=name-of-your-bridge change-tcp-mss=yes name=name-of-the-ppp-profile use-encryption=yes
- assign above profile to a user.
- setup & enable openvpn server.
- on the remote sites, apply step 1-2 on each routers.
- assign the wlan interface to the bridge.
- create openvpn client with profile as above.
- connect the vpn, make sure the link is active. you may optionally set dhcp-client on the the bridge just to verify that it can obtain ip from the central router.
- setup wlan configuration (ssid, password etc.) and verify the ssid appear on the wifi scan list.
now you can connect to the wlan ssid. you'll obtained ip address from central router & captive portal login page will appear.
this actually connect/extend the bridge between central router and remote sites.
note that for this config to work, you must have a layer 2 domain connected between your wifi client to central router. if you want to use different captive portal per each location, make different bridge and hotspot on the central router.
alternatively you can use capsman on the central router and link all the access points to capsman controller. i've wrote how to do this on separate post on wireless section.
if you want to use local dhcp server on each remote sites, the captive portal hotspot must be located on that remote router too. captive portal does not work on layer 3 because the ip & mac address of the router will be registered as client, not the ip & mac address of the client device.
so if you want to use centralize hotspot captive portal, the client and the hotspot controller must be connected in layer 2 (mac address of the client must be visible to the controller. so the dhcp almo must be centralized on the central router where the hotspot resides.
if you want to use local dhcp, the hotspot controller must be located on the remote device also. the uplink from the controller then can be routed to the vpn link.
make sure you set ap isolation (disable client to client forwarding) when using this setup to reduce broadcast packet over the vpn link.