Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm having a bit of trouble routing my traffic through my VPN server. Basically I have a pfSense setup that works amazingly well for everything it's currently doing. However, now, I have need to set up a PPTP VPN. I've got the basic setup and login working fine. When I check my IP it says I'm on the remote network, etc. However, I can't seem to figure out how to properly route traffic to the internal network.

My current setup is as follows:

HOME SETUP
Trendnet Router:  192.168.1.1
1 MAC (192.168.1.101)
1 PC(192.168.1.148)

<------INTERNET------>

WORK SETUP
pfSense Firewall:  192.168.1.1
7 PC
3 Linux
all on 192.168.1.0 subnet

PFSENSE PPTP SETTINGS
Server Address: 192.168.2.1
Remote Address Range: 192.168.2.192/28
Require 128-bit Encryption:  True

As I said, I can connect to the PFSENSE VPN just fine and I'll receive an IP of 192.168.2.192 (or above). However I need to figure out what kind of rules I need in order to route traffic to the machines on the 192.168.1.0 WORK subnet so that they show up in network neighborhood, etc (and so that I can eventually VNC to them). I've added a rule to allow ALL traffic from the PPTP interface in, but I'm not sure where to go from here. Any assistance is most appreciated.

share|improve this question

1 Answer 1

up vote 3 down vote accepted

You're work and home networks are setup on the same subnet (192.168.1.0/24) You are going to need to switch one of them to another subnet otherwise the machines will never be able to route out to the machines on the other network, as they think they are local.

If you still can't talk after you switch the subnet at one location, post back here and we can work with you from there.


To clarify a little on how VPN works based on your comment.

You don't assign the VPN clients to the same subnet as you office. They need to be on a unique subnet. For my example lets assume the following:

  • Home subnet is 192.168.1.0/24
  • Office subnet is 10.0.0.0/24
  • VPN subnet is 10.2.0.0./24

What a connection to the office would look like is this:

  • Home computer: NIC1: 192.168.1.50; vNIC1-VPN: 10.2.0.50
  • pfSense: PublicNIC: 1.1.1.1; PrivateNIC: 10.0.0.10; vNIC1-VPN: 10.2.0.1
  • office server: NIC1: 10.0.0.100

The vNICx-VPN nics will be setup by your vpn client/server

After the user has established a VPN connection to the office, the traffic flow will look like:

The Home Computer connects to 10.0.0.100 it will:

  1. Look up the route in the routing table
  2. see a route that specifies the VPN adapter as the gateway
  3. The VPN Client subsystem will encapsulate the packets
  4. The machine will then send them over the public internet to the pfSense router.

Once the router gets a VPN encapsulated packet it:

  1. sends it to the VPN Daemon subsystem
  2. The VPN subsystem will decode the packet
  3. The host will look up the unencrypted destination
  4. The machine will then route it out the proper interface to be sent to the Server.

The response from the server will be sent to the pfSense router (since the subnet is not directly connected and the machine doesn't have any routes to that machine)

The pfSense router will:

  1. look up the Home computer VPN IP as that is what the server will see the packet as comming from.
  2. The routing table will tell it to send it through the VPN virtual adapter.
  3. The packet will be sent to the vpn Subsystem encapsulated, and sent over the internet to the client machine.

Once at the client machine the VPN subsystem will decrypt the packet and send it up the networking stack to the application.

Wash, rinse, repeat.

share|improve this answer
    
Can I not "cross-route" with some specialized rules? Unfortunately I cannot change every employee's home subnet so as to be compatible with the work subnet. Nor can I change the office setup at this point in time. Is there anything else I can do? –  humble_coder Jan 7 '10 at 2:08
    
The problem is that you would potentially need to push the "cross-route" to the client machines as well were it even possible. Assuming this were even possible (which it isn't) - how on earth would you handle IP address collisions (home computers and work computers with the same IP address). This just isn't going to work without changing the network. I would recommend changing the work network - probably to something in the 10.x.y.z range. –  Goyuix Jan 7 '10 at 3:21
1  
@huble_coder: No, Connected routes take precedence that is why most companies try to avoid the 192.168.0.0/24, 192.168.1.0/24 and 192.168.2.0/24 ( the most common home networks ). A 10.0.0.0/8 or 172.16.0.0/20 would be most preferable. If you want to saty 192.168.0.0/16 then go with something like 192.168.200.0/24 –  Zypher Jan 7 '10 at 5:24
    
Alright, I will beg borrow and steal today in order to get approval for office IP change. That said, once I have them on a different subnet, I still face the challenge of not being able to assign the VPN clients to the same subnet as the office -- pfSense warns me that the address range I've chosen for VPN clients is in the same subnet as the office. So, how do I proceed from there? –  humble_coder Jan 7 '10 at 15:35
    
Ok so I got the office switched to 10.0.0.0/24. Everything works like a charm--mostly. I can map, ping, and manually mount remote drives. However it seems that no NETWORK NEIGHBORHOOD, or "zero-config" items work. Do I need to set up a rule to pass all traffic on the network (or maybe just UDP)? –  humble_coder Jan 14 '10 at 16:40

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.