› Forums › Network Management › Signal a BUG › CaptivePortal can not redirect to authen webpage
- This topic is empty.
-
AuthorPosts
-
March 20, 2013 at 1:02 pm #43609
jimmy
ParticipantHi
I have ploblem
When client fix external proxy in browser. It bypass captiveportal webpage.
Note:
I am not enable transparent proxy on zeroshell becase my firewall is slowMarch 20, 2013 at 1:03 pm #52704jimmy
ParticipantHi
I have ploblem
When client fix external proxy in browser. It bypass captiveportal authen webpage.
Note:
I am not enable transparent proxy on zeroshell becase my firewall is slowMarch 25, 2013 at 8:38 am #52705jimmy
ParticipantPlease help me.
My client set external proxy in web browser
Zeroshell can not redirect to Captive authen
March 25, 2013 at 11:59 am #52706redfive
ParticipantHi jimmy , on wich interface the CP is activated ? and wich eth is the wan interface ? Could you post the output of iptables -L FORWARD -v ?
byeMarch 25, 2013 at 2:32 pm #52707jimmy
Participantiptables -L FORWARD -v
Chain FORWARD (policy ACCEPT 273 packets, 17405 bytes)
pkts bytes target prot opt in out source destination152K 6611K ACCEPT icmp — * * 0.0.0.0/0 0.0.0.0/0
64995 4365K ACCEPT udp — * * 0.0.0.0/0 0.0.0.0/0 udp dpt:53
63160 8798K ACCEPT udp — * * 0.0.0.0/0 0.0.0.0/0 udp spt:53
0 0 ACCEPT udp — * * 0.0.0.0/0 0.0.0.0/0 udp dpt:67
0 0 ACCEPT udp — * * 0.0.0.0/0 0.0.0.0/0 udp spt:67
3419K 271M ACCEPT tcp — * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
5403K 6838M ACCEPT tcp — * * 0.0.0.0/0 0.0.0.0/0 tcp spt:80
521K 159M ACCEPT tcp — * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443
592K 439M ACCEPT tcp — * * 0.0.0.0/0 0.0.0.0/0 tcp spt:4430 0 ACCEPT tcp — * * 0.0.0.0/0 0.0.0.0/0 tcp spts:5xxxx:5xxxx
1173K 472M ACCEPT all — * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
11017 816K CapPort all — * * 0.0.0.0/0 0.0.0.0/0>
Now I use Default policy ACCEPT
March 25, 2013 at 2:45 pm #52708jimmy
ParticipantMy Zeroshell
Release 1.0.beta16
and I use Captive with Multi VLAN
March 25, 2013 at 7:36 pm #52709redfive
ParticipantYou should not have any rule that could interfer with the cp, and all of your rules, so written without specify input/output interfaces, are doing exactly that (since they are before the cp rule , the last in the forward chain). I’m almost sure that also the accounting doesn’t shows the real traffic about clients behind cp . With accept as defaul action , and no drop rule , your firewall is …”as” without firewall. If you don’t need firewall , remove all rules in the forward chain ( it will work better than now, with redirect and accounting), otherwise write more specific rules if you have other phisical/logical interfaces in addition to those where the cp is activated.
-
AuthorPosts
- You must be logged in to reply to this topic.