Remote VPN to Wired to Wireless Routing Question (obviously!)

  • Thread starter Thread starter tha_shadiest_one
  • Start date Start date
T

tha_shadiest_one

I'm sure someone can answer this question pretty quickly, so thanks in
advance to whoever that persons happens to be. Here is the deal...

My server at home has two interfaces. One wired (172.16.204.123), one
wireless (192.168.0.1). Through the wired connection I connect to my
company via VPN and am able to get to machines on the remote network
fine. From work, I can get back to my server at home just fine, but I
would like to also be able to get back to a specific machine on my
wireless network from work. How can I best configure RRAS to
accomplish this? I was thinking that I should be able to multi-home
my Wired adapter and setup a static route from that 2nd IP on the
wired adapter over to the IP of my target machine on the wireless
network, but I am not sure how to go about setting that up properly.
HELP!

A quick 'n' dirty diagram.


OFFICE NETWORK
172.16.4.0
|
|
|
|
|
VPN
|
|
|
|
HOME SERVER
172.16.204.123
(Wired Adapter)
192.168.0.1
(Wireless Adapter)
^
^
^
^
^
^
^
Destination Computer
192.168.0.2

Thanks!

shady1
 
An ordinary VPN connection is a client-server connection. The server only
sets up a host route back to the client. It does not route traffic for
machines behind the client.

To route for clients behind the RRAS server you will need to set up a
router to router VPN connection. This uses demand-dial interfaces to which
you can attach static routes to link subnets. Initially, look at the Help
files for router to router VPN.
 
Bill, yeah, i forgot to mention that I have a VPN appliance here that
creates the connection, so this would not be a roadblock.
 
Have you tried just enabling the server as an IP router in RRAS? You
would need a static route on the router at work to route traffic for
192.168.0.0 to the VPN endpoint.
 
Haven't tried that. Since the network at work already routes
172.16.204.0 over to my house I wanted to work with that rather than
call in our consultant to reconfigure the FW. Not to mention that at
that point my VPN appliance wouldn't know what to do with a
192.168.0.0 address.
 
Back
Top