Cable Forum - View Single Post

BBKing · 07-04-2005, 17:18

I've seen this crop up before - the VPN software initiates the connection via HTTP on port 80, which is intercepted by the proxy and the VPN terminator at the far end isn't intelligent enough to spot the difference between a proxy and client IP (mind you, neither are slashdot). Other VPN solutions that don't use port 80 at all are unaffected (including Cisco VPN, which we use at ntl, in fact).

Static IPs aren't available on cable - business get pseudo static IPs where your MAC is guaranteed the same address in the pool as long as that pool is allocated to your area, but obtaining the IP is done over DHCP (otherwise the UBR will reject the traffic).

07-04-2005, 17:18	#7
BBKing R.I.P. Join Date: Jun 2003 Location: London Services: 20Mb VM CM, Virgin TV Posts: 5,983	Re: VPN tunnel creation I've seen this crop up before - the VPN software initiates the connection via HTTP on port 80, which is intercepted by the proxy and the VPN terminator at the far end isn't intelligent enough to spot the difference between a proxy and client IP (mind you, neither are slashdot). Other VPN solutions that don't use port 80 at all are unaffected (including Cisco VPN, which we use at ntl, in fact). Static IPs aren't available on cable - business get pseudo static IPs where your MAC is guaranteed the same address in the pool as long as that pool is allocated to your area, but obtaining the IP is done over DHCP (otherwise the UBR will reject the traffic).