[PacketFence-users] Customizing the FQDN of Captive Portal?

Greetings, The default FQDN of the captive portal that appears in users browsers is simply the FQDN of the PacketFence server. Is there a way change this? For example, let's say the FQDN of my PF server is "nac01.corp.example.com". How can I instead direct users to a more friendly name " registrat

Re: [PacketFence-users] Customizing the FQDN of Captive Portal?

I've got the same question! Is it possible to define multiple portal FQDNs which PacketFence listens to? Em qui, 24 de jan de 2019 às 10:34, Christian McDonald via PacketFence-users escreveu: > Greetings, > > The default FQDN of the captive portal that appears in users browsers is > simply the F

Re: [PacketFence-users] Customizing the FQDN of Captive Portal?

You can define additional FQDNs somewhere in the GUI. I believe when behind PacketFence DNS, these are automatically resolved to the PF server IP address. However, on your production network, you will need to configure A records on your own DNS servers. I'm specifically asking for a way define the

Re: [PacketFence-users] Customizing the FQDN of Captive Portal?

Hello Christian, The hostname and DNS that you can edit in the web admin are the one for the redirect on the portal. You would need to restart the httpd.portal and haproxy-portal services in order to take effect. Thanks, Ludovic Zammit lzam...@inverse.ca :: +1.514.

Re: [PacketFence-users] Customizing the FQDN of Captive Portal?

Hello Christian, it's hard coded in PacketFence (https://github.com/inverse-inc/packetfence/blob/devel/go/httpdispatcher/proxy.go#L232) but it shoudn't be complicate to add a configuration parameter for each network to define the fqdn of the portal. I will have a look to see if it's not too