--_0e8d4555-c271-4e2d-99ce-43ae4e9beafe_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Stop the firewall temporarily and see if it works.
service iptables stop
If you can see the webpage when the firewall is stopped, then you need to add a rule to iptables in order to let you access port 80/443, something like:
iptables -A INPUT -p tcp -i eth0 -j ACCEPT --dport 80
iptables -A INPUT -p tcp -i eth0 -j ACCEPT --dport 443
-A INPUT will append to the INPUT chain-p tcp specifies the packet is a TCP packet-i eth0 specifies the interface.-j ACCEPT If the packet matches it should be accepted--dport 80 Port number. 80 for HTTP, 443 for HTTPS
then run,iptables save
to save the changes.
If it doesn't work, post the content of your logs to the mailing list.
You can monitor the logs, and see if there's something strange there by opening a terminal and run:
tail -f /usr/local/pf/logs/packetfence.log
Then reproduce your issue, and watch the contents of packetfence.logand post that information here.
Regards,Alberto.
Date: Tue, 21 Feb 2012 12:36:08 -0500
Subject: [Packetfence-users] Captive Portal not working
Hello All,
I recently setup packetfence in an inline mode and everything seems to
be working fine. Under the admin/node page, clients are showing up and
I can give them access or not. My problem is, i have registration
enabled and everything all setup redirecting port 80/443 as default
but no matter what, I can't seem to get the captive portal page to
show up on a client machine. Trying to go to google.com and it times
out but if I change the users status on the node page to reg, it
works. Not sure if I am missing something here or not....any help is
appreciated.
Thanks.
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Packetfence-users mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--_0e8d4555-c271-4e2d-99ce-43ae4e9beafe_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Stop the firewall temporarily and see if it works.<div><br></div><div>service iptables stop</div><div><br></div><div>If you can see the webpage when the firewall is stopped, then you need to add a rule to iptables in order to let you access port 80/443, something like:</div><div><br></div><div>iptables -A INPUT -p tcp -i eth0 -j ACCEPT --dport 80 </div><div>iptables -A INPUT -p tcp -i eth0 -j ACCEPT --dport 443</div><div><br></div><div><div>-A INPUT</div><div> will append to the INPUT chain</div><div>-p tcp</div><div> specifies the packet is a TCP packet</div><div>-i eth0</div><div> specifies the interface.</div><div>-j ACCEPT</div><div> If the packet matches it should be accepted</div><div>--dport 80</div><div> Port number. 80 for HTTP, 443 for HTTPS</div></div><div><br></div><div>then run,</div><div>iptables save</div><div><br></div><div>to save the changes.</div><div><br></div><div>If it doesn't work, post the content of your logs to the mailing list.</div><div><br></div><div>You can monitor the logs, and see if there's something strange there by o<span style="font-size: 10pt; ">pening a terminal and run:</span></div><div><br></div><div>tail -f /usr/local/pf/logs/packetfence.log</div><div><br></div><div><span style="font-size: 10pt; "><br></span></div><div>Then reproduce your issue, and watch<span style="font-size: 10pt; "> the contents of packetfence.log</span></div><div><span style="font-size: 10pt; ">and post that information here.</span></div><div><span style="font-size: 10pt; "><br></span></div><div><span style="font-size: 10pt; "><br></span></div><div>Regards,</div><div>Alberto.</div><div><br></div><div><br><div><div id="SkyDrivePlaceholder"></div>> Date: Tue, 21 Feb 2012 12:36:08 -0500<br>> From: ***@gmail.com<br>> To: packetfence-***@lists.sourceforge.net<br>> Subject: [Packetfence-users] Captive Portal not working<br>> <br>> Hello All,<br>> <br>> I recently setup packetfence in an inline mode and everything seems to<br>> be working fine. Under the admin/node page, clients are showing up and<br>> I can give them access or not. My problem is, i have registration<br>> enabled and everything all setup redirecting port 80/443 as default<br>> but no matter what, I can't seem to get the captive portal page to<br>> show up on a client machine. Trying to go to google.com and it times<br>> out but if I change the users status on the node page to reg, it<br>> works. Not sure if I am missing something here or not....any help is<br>> appreciated.<br>> <br>> Thanks.<br>> <br>> ------------------------------------------------------------------------------<br>> Virtualization & Cloud Management Using Capacity Planning<br>> Cloud computing makes use of virtualization - but cloud computing <br>> also focuses on allowing computing to be delivered as a service.<br>> http://www.accelacomm.com/jaw/sfnl/114/51521223/<br>> _______________________________________________<br>> Packetfence-users mailing list<br>> Packetfence-***@lists.sourceforge.net<br>> https://lists.sourceforge.net/lists/listinfo/packetfence-users<br></div></div> </div></body>
</html>
--_0e8d4555-c271-4e2d-99ce-43ae4e9beafe_--