using with windows 10 pptp vpn

solemnwarning / ipxwrapper

http://www.solemnwarning.net/ipxwrapper/

GNU General Public License v2.0

191 stars 27 forks source link

using with windows 10 pptp vpn #6

Open thanosazlin opened 5 years ago

thanosazlin commented 5 years ago

currently unable to get ipxwrapper to work with warcraft 2 or Red Alert 2 with a player that is connected via windows 10 builtin pptp vpn connection.. I have my own win2012 vpn server for gaming. Dosbox IPX works fine. my buddy can VPN into my home system and get on to my network via PPTP then we start up dosbox ipx and play dos games fine.. i have copied the ipxwrapper files into WAR2 and RA2 dirs and attached them to the network adapter used from each host.. i was hoping to see some PPTP adapter listed as when my buddy is connected to my vpn server the pptp adaptor/connection for him in ipconfig shows up like a seperate adapter.. Is there not possible way to get ipxwrapper to work over vpn pptp?

solemnwarning commented 5 years ago

It sounds like the PPTP interface might not be enumerated by GetAdaptersInfo(), or for some reason IPXWrapper is skipping over it. Can you post the listing after "Listing IP interfaces" in the IPXWrapper log (ipxwrapper.log in the application's working directory)?

Krush206 commented 5 years ago

I have the same issue. May I send the log without the MAC addresses? (I'm a bit paranoid)

solemnwarning commented 5 years ago

If you want to obscure any MACs, thats fine. Please replace any of the same MAC with the same substitution (e.g. interface a -> AA:AA:AA:AA:AA:AA, interface b -> BB:BB:BB:BB:BB:BB, etc).

Krush206 commented 5 years ago

The VPN interface does not have any MAC address as an IP interface. It only gets a (generic?) MAC address as an IPX interface. ipxwrapper.log

solemnwarning commented 5 years ago

@Krush206 thanks for the log. Am I right in thinking that the "Conexγo VPN" is your PPTP interface, and that the broadcast address for that network ISN'T 10.255.255.255? Are any of the other adapters involved in the VPN?

Krush206 commented 5 years ago

Yes, that's right. There aren't any other interfaces involved. Actually, the only broadcast address assigned for the VPN interface is 255.255.255.255.

solemnwarning commented 5 years ago

I've had some time to look at this again, and a couple of things strike me as odd:

Two IPX interfaces in your log have the Node address EE:EE:EE:EE:EE:EE, I think they are your VPN interface and the wildcard one.
The broadcast address from the VPN interface isn't listed under the wildcard interface.

IPXWrapper chose 10.255.255.255 as the broadcast address for your VPN interface. Since the VPN interface has a netmask of 255.255.255.255, it falls back to examining the routing table and picking the most-specific destination which encompasses the IP address of the interface.

Is the remote end of your VPN 10.0.0.0/255.0.0.0, or is this coming from somewhere else?

Do the two interfaces actually have the same Node number, or was that an error made when anonymising the log file?

Could you also post the output of the ROUTE PRINT -4 command on your computer?

Thanks

Krush206 commented 5 years ago

I believe the remote end is 10.0.0.0/255.0.0.0, yes. I can't confirm that at all, though. I'm not the administrator of the VPN. I claim I believe the remote end is that one, because the ROUTE PRINT -4 command shows it this way. Here is the log.