Hi Thanks. No, there is no proxy in the middle in this testing case, I believe that's why the packets are received at port 443 on the server but then somehow dropped. Is there anything wrong with the iptables rules that might stop this? > It is a bit dangerous to use 443/tcp for vpn... It was recommended by the OpenVPN users list. > But you can set up 2 services on the same host... Yes, I could but that makes an administration problem to do with status logs and other stuff I think. ---------------------------------------- > Date: Tue, 6 Jul 2010 19:26:47 +0200 > From: swifty@xxxxxxxxxxx > To: webster_jack@xxxxxxxxxxx > CC: netfilter@xxxxxxxxxxxxxxx > Subject: Re: iptables not forwarding port 443 > > Hi, >> Hi >> It is a TCP connection. >> > I prefer UDP... :D > It is usually not filtered... > Maybe your problem is that a "proxy-in-the-middle" tries to set up an > https connection... > Or just simply drops the "unknown"/"not-https" packets... > It is a bit dangerous to use 443/tcp for vpn... >> I could set up the server on port 443 but there are existing clients with 1194 configurations so I had hoped instead to only use 443 when necessary and avoid resending out new client configurations. >> OpenVPN can only listne on 1 port. >> > But you can set up 2 services on the same host... > -- > To unsubscribe from this list: send the line "unsubscribe netfilter" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now-- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
