I have a remote ROS x86 system that I have been trying to get a PPTP connection setup with PC running DUDE.
I need to set the DUDE PC up with a VPN connection so I can use it to monitor the remote ROS unit and local network devices.
ether1 = 10.10.1.3/25 - Public
ether3 = 192.168.0.254/24 - Local
I need help on the proper IP addresses or routes I should be using to be able to get DUDE server able reach devices on the 192.168.0.0/24 network.
Thanks for any help
There isn’t enough information to comment properly.
What is the connection between the sites?
There must be more than the IP addresses quoted, 10.x.x.x is a private address, not public, so there must be other intermediate devices if you’re going over a public network.
Draw a simple diagram e.g.
PC <—> ADSL Router <—> Internet <—> ADSL Router <—> MT Router
Give IP addresses of each interface, if they’re public then quote as 89.x.x.x so you don’t give away too many secrets.
Regards
Chris Macneill
PC ↔ Cable Modem ↔ Internet ↔ VSAT Modem ↔ ROS
Dude PC = 71.89.89.12/28 - Public IP
ROS Ether1= 213.10.10.3/25 - Public IP
ROS Ether3= 192.168.0.254/24 - Local
What are the addresses for each side of the Cable Modem and Vsat modem? I still don’t think we have the full picture here.
If your PC and MT router are truely on public IP addresses, then all you should need is a local route on the PC to tell it where to find the 192.168.x.x addresses.
If the PC is running WinXP/2000 then use:-
route /p add 192.168.0.0 MASK 255.255.255.0 213.10.10.3
the /p makes the route persistant, i.e. it survives a reboot.
I’m a little suspicious that the public addresses you have quoted are for the cable modem and Vsat modem. You originally said the “public” side of the MT router was 10.x.x.x, that would indicate that the “private” side of the VSAT router is also 10.x.x.x.
What is the endpoint for your PPTP connection, the VSAT router or the MT router? Have you actually got the PPTP connection working, i.e. does it connect OK or do you get errors? Even without the routes set correctly you should still be able to get the PPTP session to connect OK.
Regards
Chris Macneill
PC and ROS have ‘true’ Public IP addresses.
I have 14 “Public IP” addresses from service provider here where the Dude PC is located.
I have 254 “Public IP” addresses from VSAT service provider on other end with ROS box.
I used the 10.x.x.x IP addresses in first post so I did not have to give out my true Public IP’s.
End point connection of PPTP will be the ROS box.
I can get a connection just fine but Dude cannot find or ping any of the ‘Local’ IP’s (192.168.0.0/24) on the ROS box.
OK, I assume you’re using plain routing on the MT router? If so, the route I put in the previous post should work.
If you are using NAT you have to map public to private addresses, therefore to connect to more than one address on the 192.168.0.x subnet you’ll need to allocate an equal number of public addresses in order to perform the mapping.
Regards
Chris Macneill
Sorry if I don’t know much in the way of creating this connection.
Dude PC (WinXP Pro) = 71.10.10.12 - Public IP
ROS (ether1) = 213.10.10.3/25 - Public IP
ROS (ether3) = 192.168.0.254/24
Using Winbox to setup the PPTP connection.
Enabled PPTP on ROS
Created Secret
User = test
Password = test
Service = PPTP
Caller ID = 71.10.10.12
Profile = default
Local Address =??
Remote Address = ??
Routes = ??
Do I need to add route on the Dude PC or just in ROS box?
I have tried
192.168.0.254 @ Local Address
192.168.0.253 @ Remote Address
192.168.0.253 @ Local Address
192.168.0.252 @ Remote Address
Can connect using both above and ping 192.168.0.254 but rest of network 192.168.0.0/24 is unreachable.
Please forgive the ignorance as this is my first go around with PPTP
as workaround you can set that windows machine traffic all goes through the tunnel, but that wont be good, as i understand, that this dude server connects to other devices near.
check what subnet mask you have if you set addresses like you said, i suspect that it is /32
so you must setup route that will tell your windows PC that all the rest network is there too, hence /24 (or whatever you have there) route must be added.
as i do not know how windows networking works i cannot help you any further with this problem