<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 15/06/12 13:43, Scott Howard wrote:
<blockquote
cite="mid:CACnPsNXSgpffBbgwO1VvjQrYziVkuzWXqPEA8nyUpntW9-a+sQ@mail.gmail.com"
type="cite">On Thu, Jun 14, 2012 at 8:35 PM, Damien Gardner Jnr <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:rendrag@rendrag.net" target="_blank">rendrag@rendrag.net</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">Isn't that standard
behaviour with any ISP with a (forced) proxy? All HTTP
requests come from the proxy IP, all other traffic comes
from the end user's IP?<span class="HOEnZb"><font
color="#888888"><br>
</font></span></div>
</blockquote>
<div><br>
Not at all. Any ISP doing a transparent proxy should be doing
"IP Spoofing" so that the connection still appears to come
from the client IP address. That's not to say that they all
do, but...<br>
<br>
That said, I would hope that the "authentication" is occurring
over HTTPS, and there's no reason any ISP should be running a
transparent proxy for SSL traffic.<br>
<br>
Scott<br>
</div>
</div>
</blockquote>
Last time i looked my clients were getting private address ranges
(10.*) using telstra business internet.<br>
Which was fine until it overlapped the private range their office
was using and broke the VPN.<br>
<br>
<br>
</body>
</html>