› Forums › Network Management › ZeroShell › Https blocked !!?
- This topic is empty.
-
AuthorPosts
-
November 3, 2009 at 11:25 am #42009
sample31
MemberCan someone help me allow to open https trafic thru Zeroshell please?
Thanx
November 3, 2009 at 4:27 pm #49003ppalias
MemberCheck the firewall if there is any blocking rule on the forward chain.
November 4, 2009 at 1:25 pm #49004sample31
Member@ppalias wrote:
Check the firewall if there is any blocking rule on the forward chain.
Thanx for the reply.
I check my rules, but everything is open on all chains.
All http requests work fine, but when I make a https request (ie gmail.com), it doesn’t reach the destination.
Thanx
November 4, 2009 at 4:36 pm #49005giancagianca
ParticipantNat is configured?
Transarent proxy is enable?
If nat is disable and transparent proxy is enable only http is enable.Bye.
November 6, 2009 at 7:50 am #49006sample31
Member@giancagianca wrote:
Nat is configured?
Transarent proxy is enable?
If nat is disable and transparent proxy is enable only http is enable.Bye.
Thanx for the reply Giancagiance
Nat is correctly configured on ETH0
Transparent proxy is enable.
The captive portal allows users to connect to Internet, but any https request doesn’t work.
I tried to recompile havp with –enable-ssl-tunnel option, but without results.Thanx in advance for help
November 6, 2009 at 11:44 am #49007ppalias
MemberWhat is shown on the screen when someone tries to access an https page?
Show us the output of the following commands (in shell)iptables -L -v
iptables -t nat -L -vNovember 6, 2009 at 1:40 pm #49008sample31
MemberThanx for the help ppalias
Here are the results of iptables -L -v :
root@zeroshell root> iptables -L -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
61952 18M SYS_INPUT all — any any anywhere anywhere
0 0 SYS_HTTPS tcp — any any anywhere anywhere tcp dpt:http
2144 253K SYS_HTTPS tcp — any any anywhere anywhere tcp dpt:https
6089 353K SYS_SSH tcp — any any anywhere anywhere tcp dpt:ssh
23075 14M ACCEPT all — any any anywhere anywhereChain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
77 3964 ACCEPT all — any any anywhere anywhere
0 0 CapPort all — any any anywhere anywhereChain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
69380 27M SYS_OUTPUT all — any any anywhere anywhere
64802 26M ACCEPT all — any any anywhere anywhereChain CapPort (1 references)
pkts bytes target prot opt in out source destination
0 0 CapPortACL all — ETH00 any anywhere anywhereChain CapPortACL (1 references)
pkts bytes target prot opt in out source destination
0 0 CapPortFS all — any any anywhere anywhere
0 0 CapPortFC all — any any anywhere anywhere
0 0 CapPortWL all — any any anywhere anywhere
0 0 DROP all — any any anywhere anywhereChain CapPortFC (1 references)
pkts bytes target prot opt in out source destinationChain CapPortFS (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT udp — any any anywhere anywhere udp dpt:domain
0 0 ACCEPT udp — any any anywhere anywhere udp dpt:bootpsChain CapPortWL (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all — any any 192.168.0.81 anywhere MAC 00:19:DB:B4:20:5B
0 0 ACCEPT all — any any 192.168.0.80 anywhere MAC 00:0C:29:EE:12:50Chain NetBalancer (0 references)
pkts bytes target prot opt in out source destinationChain SYS_HTTPS (2 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all — lo any anywhere anywhere
2144 253K ACCEPT all — any any anywhere anywhereChain SYS_INPUT (1 references)
pkts bytes target prot opt in out source destination
3006 363K ACCEPT all — lo any anywhere anywhere
26821 2683K ACCEPT tcp — ETH00 any anywhere anywhere tcp dpts:12080:12083
0 0 DROP tcp — any any anywhere anywhere tcp dpts:12080:12083
523 120K ACCEPT udp — any any anywhere anywhere udp spt:domain state ESTABLISHED
94 122K ACCEPT tcp — any any anywhere anywhere tcp spt:http state ESTABLISHED
0 0 ACCEPT tcp — any any anywhere anywhere tcp spt:8245 state ESTABLISHED
200 15200 ACCEPT udp — any any anywhere anywhere udp spt:ntp state ESTABLISHED
31308 15M RETURN all — any any anywhere anywhereChain SYS_OUTPUT (1 references)
pkts bytes target prot opt in out source destination
3006 363K ACCEPT all — any lo anywhere anywhere
1259 90874 ACCEPT udp — any any anywhere anywhere udp dpt:domain
42 1987 ACCEPT tcp — any any anywhere anywhere tcp dpt:http
0 0 ACCEPT tcp — any any anywhere anywhere tcp dpt:8245
271 20596 ACCEPT udp — any any anywhere anywhere udp dpt:ntp
64802 26M RETURN all — any any anywhere anywhereChain SYS_SSH (1 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all — lo any anywhere anywhere
6089 353K ACCEPT all — any any 192.168.0.0/24 anywhere
0 0 DROP all — any any anywhere anywhere
And here are the results of iptables -t nat -L -v
root@zeroshell root> iptables -t nat -L -v
Chain PREROUTING (policy ACCEPT 5592 packets, 583K bytes)
pkts bytes target prot opt in out source destination
6570 638K CapPort all — any any anywhere anywhere
0 0 DNAT tcp — any any anywhere anywhere tcp dpt:8082 to:10.20.4.12:8082
0 0 Proxy tcp — any any anywhere anywhere tcp dpt:httpChain POSTROUTING (policy ACCEPT 1957 packets, 342K bytes)
pkts bytes target prot opt in out source destination
1959 342K SNATVS all — any any anywhere anywhere
2 107 MASQUERADE all — any ETH00 anywhere anywhereChain OUTPUT (policy ACCEPT 1931 packets, 340K bytes)
pkts bytes target prot opt in out source destinationChain CapPort (1 references)
pkts bytes target prot opt in out source destination
192 11052 CapPortHTTP tcp — ETH00 any anywhere anywhere tcp dpt:http
271 13020 CapPortHTTPS tcp — ETH00 any anywhere anywhere tcp dpt:https
0 0 CapPortGW tcp — ETH00 any anywhere anywhere tcp dpt:12080
517 30780 CapPortGW tcp — ETH00 any anywhere anywhere tcp dpt:12081Chain CapPortGW (2 references)
pkts bytes target prot opt in out source destination
517 30780 REDIRECT tcp — any any anywhere anywhereChain CapPortHTTP (1 references)
pkts bytes target prot opt in out source destination
150 9000 CapPortProxy all — any any 192.168.0.81 anywhere MAC 00:19:DB:B4:20:5B
39 1872 CapPortProxy all — any any 192.168.0.80 anywhere MAC 00:0C:29:EE:12:50
3 180 REDIRECT tcp — any any anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 10/min burst 15 mode srcip-dstport redir ports 12080
0 0 DROP tcp — any any anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN
0 0 REDIRECT tcp — any any anywhere anywhere redir ports 12080Chain CapPortHTTPS (1 references)
pkts bytes target prot opt in out source destination
1 60 ACCEPT all — any any 192.168.0.81 anywhere MAC 00:19:DB:B4:20:5B
255 12240 ACCEPT all — any any 192.168.0.80 anywhere MAC 00:0C:29:EE:12:50
6 288 REDIRECT tcp — any any anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN limit: avg 10/min burst 15 mode srcip-dstport redir ports 12081
0 0 DROP tcp — any any anywhere anywhere tcp flags:FIN,SYN,RST,ACK/SYN
0 0 REDIRECT tcp — any any anywhere anywhere redir ports 12081Chain CapPortProxy (2 references)
pkts bytes target prot opt in out source destination
189 10872 Proxy tcp — any any anywhere anywhere tcp dpt:http
0 0 ACCEPT all — any any anywhere anywhereChain Proxy (2 references)
pkts bytes target prot opt in out source destination
189 10872 REDIRECT tcp — ETH00 any anywhere anywhere redir ports 8080Chain SNATVS (1 references)
pkts bytes target prot opt in out source destinationUsers wait until the message “timeout exceeded” is shown.
Thanx for the help
November 8, 2009 at 2:39 pm #49009ppalias
MemberAre you trying to allow inbound connections from the internet to an internal https server? Or users from your inside network are trying to access an https webpage on the internet?
November 9, 2009 at 9:02 am #49010sample31
Member@ppalias wrote:
Are you trying to allow inbound connections from the internet to an internal https server? Or users from your inside network are trying to access an https webpage on the internet?
I just want users (from internal network) to have access to https (ie gmail.com…)
Thanx for the help
November 9, 2009 at 10:02 am #49011ppalias
MemberWhat are the network interfaces of your ZS? ETH00 is for the internet or the clients? What are the other interfaces for?
November 9, 2009 at 10:14 am #49012sample31
Member@ppalias wrote:
What are the network interfaces of your ZS? ETH00 is for the internet or the clients? What are the other interfaces for?
ETH0 is the Internal Network interface
ETH1 is the admin interface
ETH2 is the Internet interfaceThanx in advance for the help ppalias
November 9, 2009 at 9:11 pm #49013ppalias
MemberNAT is done on the internet interface, so turn it to ETH02
November 10, 2009 at 7:59 am #49014 -
AuthorPosts
- You must be logged in to reply to this topic.