Captive Portal on Different Domain

[run('Jimbo');]

Hi, is it possible to run captive portal on a different domain/ip so that I'm not sharing my router domain?

Thanks

[run('Jimbo');]

Any pointers? 

Thanks

[dseven]

What do you mean by "sharing my router domain"?

You can specify a Hostname in the captive portal configuration, but clients must still be able to resolve that to the IP address that the capture portal service is listening on.

What problem are you trying to solve?

[run('Jimbo');]

I have vlans and for them to access the portal they are redirected to the router domain.. Is it possible to run the portal on a different domain so guests etc can't see the root domain...

Thanks

[dseven]

I'm still not sure what it is that you're trying to accomplish ... but you can put whatever hostname you want in the captive portal configuration, so long as the clients can resolve it to the IP address that the captive portal is listening on. You could use a host override in Unbound DNS with some fake hostname/domain.....

[run('Jimbo');]

Yeah the unbound DNS override is sort of what I mean but I wanted it to run on a different ip also so there is no way a user could get the ip for the router...

Thanks

[dseven]

The IP of the router is going to be the gateway for the clients. There is no way to hide that.

[run('Jimbo');]

I know that, that's why I was asking if I can run it on a different domain/IP

Thanks

[Patrick M. Hausen]

I know that, that's why I was asking if I can run it on a different domain/IP

But your clients will still have the router as their default GW, so they know the router IP, anyway.

[run('Jimbo');]

They are on vlans with there own subnets/gateways...

Thanks

[Patrick M. Hausen]

And each of these gateways is your router, isn't it?

[run('Jimbo');]

Course, but the firewall blocks all private networks so they can't ping the router...

Thanks

[dseven]

The IP address used for the captive portal is the same IP address used by clients as their gateway. You can't hide it.

[run('Jimbo');]

Ok, thanks

[dseven]

You could actually create a loopback interface, and give it any IP address you like, and use that (either directly or through a DNS host override) as the captive portal hostname... but I still don't really see any value in that, unless you think that hiding the fact that the captive portal is running on the firewall itself has some value......