This is a long shot, but maybe some of the techies here have experience with this.
I'm putting together a PPTP VPN server using Slackware Linux 9 and PoPToP. The goal is to allow Windows users to login to the LAN via the Internet. The PPTP server is hosted on a firewall using Shorewall (front-end for iptables).
Problem: I can get it to connect and communicate with the subnet the PPTP hands out IPs for, but it won't communicate with any other subnet.
The server:
- Internet: 192.168.1.1 (for testing) on eth0
- LAN: 10.1.10.0 via eth1 - actual IP is 10.1.10.93
- DMZ: 10.2.10.0 via eth2 - actual IP is 10.2.10.93
- PPTP hands out 10.3.10.2 - 10.3.10.254 to clients
- VPN "local" IP on server: 10.3.10.1
The client:
- Windows 2000 Pro
- Local IP is 192.168.1.2
- Gateway is set to 192.168.1.1 (the server)
- Receives 10.3.10.x from server
- Subnet mask for 10.3.10.x is 255.255.255.255 -- standard for PPTP, I don't think this can change, but I'm still researching that
I think the firewall is basicly OK, but might need some masquerading entries or something. The important thing to note with the firewall is it does allow connections, and this issue persists even if the firewall is turned off.
The clients CAN ping 10.1.10.93 and 10.2.10.93, since they are on that server. I believe the issue is route-related -- I don't know what routes to put in though, and whether they should be on the server or client. The server has no problem communicating with anything on any subnet, it's just the client.
Does anyone have any ideas?
If you answer, please consider that I may not know what you're talking about if you just say "do this and do that". Please be explicit so you don't have me asking "wtf?" on every step. That's not to say I don't have a handle on what I'm messing with, but some people like to assume others know more than they actually do.
I'm putting together a PPTP VPN server using Slackware Linux 9 and PoPToP. The goal is to allow Windows users to login to the LAN via the Internet. The PPTP server is hosted on a firewall using Shorewall (front-end for iptables).
Problem: I can get it to connect and communicate with the subnet the PPTP hands out IPs for, but it won't communicate with any other subnet.
The server:
- Internet: 192.168.1.1 (for testing) on eth0
- LAN: 10.1.10.0 via eth1 - actual IP is 10.1.10.93
- DMZ: 10.2.10.0 via eth2 - actual IP is 10.2.10.93
- PPTP hands out 10.3.10.2 - 10.3.10.254 to clients
- VPN "local" IP on server: 10.3.10.1
The client:
- Windows 2000 Pro
- Local IP is 192.168.1.2
- Gateway is set to 192.168.1.1 (the server)
- Receives 10.3.10.x from server
- Subnet mask for 10.3.10.x is 255.255.255.255 -- standard for PPTP, I don't think this can change, but I'm still researching that
I think the firewall is basicly OK, but might need some masquerading entries or something. The important thing to note with the firewall is it does allow connections, and this issue persists even if the firewall is turned off.
The clients CAN ping 10.1.10.93 and 10.2.10.93, since they are on that server. I believe the issue is route-related -- I don't know what routes to put in though, and whether they should be on the server or client. The server has no problem communicating with anything on any subnet, it's just the client.
Does anyone have any ideas?
If you answer, please consider that I may not know what you're talking about if you just say "do this and do that". Please be explicit so you don't have me asking "wtf?" on every step. That's not to say I don't have a handle on what I'm messing with, but some people like to assume others know more than they actually do.