I have looked at the two posts in the forums that make this same attempt, but they appear to be incomplete / unresolved / abandoned.
I would like to take a different approach to resolving this. Tunngle is based on OpenVPN, and my ignorant assumption is that this means I should be able to create the same environment with my OpenVPN server.
SUMMARY
Tunngle creates a VPN connection that allows the connected clients to see broadcast traffic from each other. An example is a LAN game server that broadcasts it's presence, and the clients being able to detect that on the subnet. (Some games can only be played this way, as opposed to the client specifying the IP of the server and letting routing take care of the rest of it.)
ENVIRONMENT
Currently, I am testing with this setup:
OpenVPN server set up on Synology NAS in 192.168.231.0 subnet
Windows 7 on the same subnet (the computer from which I will be playing)
Windows XP connecting to the OpenVPN server via WAN
MY APPROACH
I have noted the results of route print in the following three situations:
1. Not connected to a VPN
2. Connected to Tunngle (the working configuration for what I want to achieve)
3. Connected to my OpenVPN sever with it's default config
I am hoping that someone here is familiar enough with this information to be able to guide me in configuring my server and clients so that I can attain the same network functionality as the Tunngle connection.
ROUTING
1. No VPN connection
Code: Select all
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.231.1 192.168.231.200 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.231.0 255.255.255.0 On-link 192.168.231.200 266
192.168.231.200 255.255.255.255 On-link 192.168.231.200 266
192.168.231.255 255.255.255.255 On-link 192.168.231.200 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.231.200 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.231.200 266
2. Connected to Tunngle
Code: Select all
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.231.1 192.168.231.200 266
0.0.0.0 0.0.0.0 7.254.254.254 7.69.6.243 10029
7.0.0.0 255.0.0.0 7.254.254.254 7.69.6.243 31
7.69.6.243 255.255.255.255 On-link 7.69.6.243 286
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
192.168.231.0 255.255.255.0 On-link 192.168.231.200 266
192.168.231.200 255.255.255.255 On-link 192.168.231.200 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.231.200 266
224.0.0.0 240.0.0.0 On-link 7.69.6.243 286
255.255.255.255 255.255.255.255 On-link 7.69.6.243 286
Code: Select all
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.231.1 192.168.231.200 266
10.0.1.0 255.255.255.0 10.0.1.9 10.0.1.10 1
10.0.1.1 255.255.255.255 10.0.1.9 10.0.1.10 1
10.0.1.8 255.255.255.252 On-link 10.0.1.10 257
10.0.1.10 255.255.255.255 On-link 10.0.1.10 257
10.0.1.11 255.255.255.255 On-link 10.0.1.10 257
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.231.0 255.255.255.0 On-link 192.168.231.200 266
192.168.231.0 255.255.255.0 10.0.1.9 10.0.1.10 1
192.168.231.200 255.255.255.255 On-link 192.168.231.200 266
192.168.231.255 255.255.255.255 On-link 192.168.231.200 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.231.200 266
224.0.0.0 240.0.0.0 On-link 10.0.1.10 257
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.231.200 266
255.255.255.255 255.255.255.255 On-link 10.0.1.10 257
Any help with this will be very much appreciated, and I hope that it can stand as a final answer to this question for others to find in the future.
Best,
-Doc