It would seem that your problem is that your server routing traffic to the
wrong gateway.
I'm not completely familiar with VPN software, but I've seen some VPN
clients ( Microsoft Windows and Cisco ) that have an option to route all
traffic through the default gateway of the remote VPN, which should solve
your problem if I understand properly.
On Mon, May 13, 2013 at 10:42 PM, Andrew Leslie <alesl...@gmail.com> wrote:
> The issue with cellular internet is that it's NAT behind NAT so you'll
> never get a true public IP.
>
> (Sorry for the duplicate Paul, forgot to cc the list.)
> On May 13, 2013 10:15 PM, "Paul Spicer" <ephram.pont...@gmail.com> wrote:
>
> > I suppose you are missing something. This remote site is running off of a
> > cellular hot-spot. As such, it won't work with a DDNS provider because it
> > has no static inbound address. (We tried that... Every time it
> > re-registered to dyndns, it was a different address...
> >
> >
> > On Mon, May 13, 2013 at 9:33 PM, Robert Mckennon <robmcken...@gmail.com
> > >wrote:
> >
> > > Paul, perhaps I'm missing something, but wouldn't Dynamic DNS solve the
> > > problem? It automatically updates DNS when ever your public IP address
> > > changes, and there are numerous free DDNS providers out there.
> > >
> > > Rob
> > >
> > >
> > > On Mon, May 13, 2013 at 5:25 PM, Paul Spicer <ephram.pont...@gmail.com
> > >wrote:
> > >
> > >> Alright, I'm not entirely sure what the best way to word this is, but
> > I'm
> > >> going to take a stab at it...
> > >>
> > >> What I'm trying to find out is how to set up a Linux server to act as
> a
> > >> proxy / redirect machine for a specific server.
> > >>
> > >> Here's the scenario: We have a remote site (192.168.100.0) connected
> to
> > >> our
> > >> local network (192.168.1.0) through OpenVPN. At that site, we have a
> > >> server
> > >> (192.168.100.10). Locally, we can connect and communicate with this
> > server
> > >> with no problems. Thing is, that remote site doesn't have a static
> > public
> > >> IP address. Our thoughts: use one of the static IPs available to us
> > >> locally
> > >> and forward traffic to the remote server, thus allowing outside
> access.
> > >> Problem is, while OpenVPN will forward the internet traffic to that
> > server
> > >> just fine, that remote server is trying to send it's reply to the
> public
> > >> address that made the request (and not through the VPN tunnel).
> > >>
> > >> My thought was to set up a server on our local network that would do
> > >> nothing but act as a proxy for the remote server. The public address
> > will
> > >> forward to this proxy and all traffic will route to the remote server,
> > >> appearing to originate from the local network. The remote server will
> > >> reply
> > >> as it should and the proxy will feed the information back to the
> > >> requesting
> > >> public address.
> > >>
> > >> A crude diagram of what I'm trying to accomplish:
> > >> (internet)---[Local network]---[proxy/redirect]---{VPN}---[remote
> > server]
> > >>
> > >> I can not find any how-tos or tutorials explaining how to do what I
> > want.
> > >> I
> > >> found numerous proxy tutorials as well as tutorials on how to redirect
> > >> traffic, but nothing combining the two into one convenient server.
> > >>
> > >> So, does anyone have any idea what I'm trying to accomplish and have
> any
> > >> suggestions?
> > >>
> > >
> > >
> >
>
