As mentioned in my previous post, we now have this setup working for email and SMS registrations (we don¹t want to use sponsored). However, we pointed clients to the IP address of the management interface on the PF server in order to test. This poses two problems. First, PF does not open the web ports (80/443) on the management interface so we have been stopping iptables every time we restart the packetfence service as a workaround. We don¹t want to do this in production. Second, after successfully completing a registration we get the message: ³Sorry! You hit the captive portal on the management interface. The management console is on port 1443.² The client has full network access, but this message would obviously be confusing to end users.
What is the best interface to use for a captive portal for a remote network? Can I just set up a registration vlan and turn off DHCP services? If so, what does the vlan use as the default gateway since there does not appear to be a place to configure one. Based on something I saw in another thread it looks like defining an interface as ³portal² is another possibility. How exactly would I configure a portal interface? Thanks, _______________________________________ Chris Mielke | Lead, ISS Network Systems Drake Technology Services (DTS) | Drake University E [email protected] ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
