Huh. So somehow, after the upgrade to 4.0.2 I do not have a firewall rule
to allow 443 or 80 on the input-management-if chain. In 4.0.1 I have this:
ACCEPT tcp -- anywhere anywhere tcp dpt:https
Adding a rule to iptables.conf to allow https traffic lets it work fine.
On Fri, Jul 19, 2013 at 10:49 AM, Fletcher Haynes <[email protected]>wrote:
> So after my upgrade to 4.0.2, I can no longer get the gaming-registration
> url to work. If I try to access it while on the registration VLAN (replace
> captive-portal with gaming-registration) it works fine. I have it
> configured properly in pf.conf.
>
> Any help would be greatly appreciated...
>
> --
> Fletcher Haynes <[email protected]>
> Systems Administrator/Network Services Consultant
> Willamette Integrated Technology Services
> Willamette University, Salem, OR
> Phone: 503.370.6016
>
--
Fletcher Haynes <[email protected]>
Systems Administrator/Network Services Consultant
Willamette Integrated Technology Services
Willamette University, Salem, OR
Phone: 503.370.6016
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
