On 7 October 2010 16:23, Andy Smith <andy@bitfolk.com> wrote:

Hi Robert,

On Thu, Oct 07, 2010 at 04:13:50PM +0100, Robert Gauld wrote:
> Further to my earlier question today I have a netbook which connects over
> wireless to a pptp vpn on my vps's 3rd IP. When I try to connect to apache
> running on my vps's first IP address rather than appearing to come from my
> vps's 3rd IP it instead comes from the netbook's 'local' address. (Numbers
> below if this is not clear).

[...]

> Netbook:
> WLAN IP: x.x.x.x
> IP on VPN: 192.168.254.x
>
> VPS:
> Apache runs on y.y.y.73
> VPN runs on y.y.y.75
>
> Running a simple CGI to report the remote IP (from apache's perspective)
> reports 192.168.254.x where I'm after it being y.y.y.75

I'm guessing you are seeing this because the traffic that is hitting
your VPS is coming into the INPUT chain and not going through NAT,
as opposed to traffic for elsewhere which is being routed.

Aside from some gross hacks I'm not sure you would be able to fix
that, or why it matters. 192.168.254.x is just another network that
your VPS is on.

Cheers,
Andy

--
http://bitfolk.com/ -- No-nonsense VPS hosting

_______________________________________________
users mailing list
users@lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users