|
|
Matthew Matthew Haas wrote: ... > > However, as I said, I'd like to also access machines on the B network, > although any attempts at setting up the routing seem to generate some > wild and crazy packet surges on B's firewall/NAT and do not seem to > allow for a 2-way connection for communications (machines on network B > SEE my packets, but don't know how to return them). Do they have reasonable routes for your packets > > I would have thought that, if I had the VPN IP of 192.168.250.10, and > on network B, which has a VPN at 192.168.10.8, I could simply do a: > > route add 192.168.250.10/32 192.168.10.8 > > And machines on the B network would then be able to reciprocate > communications back (and all would be happy). This does not seem to be > the case. > > IP Forwarding is enabled on both VPN endpoints (networks A and B), and > I wouldn't imagine it being needed on the single machine TunnelBlick > clients. If you are using private subnets behind clients you will either need to make sure they are unique to your network and add respective routes or you will have to NAT them to the addresses of the respective VPN clients ... > > Like I said, things mostly work, but it would be nice to get this > "fringe client access to other VPN network" access going, as it would > facilitate communications on some projects in very big ways. > > Any pointers or suggestions to information I would need to pursue are > most welcome, and if anyone would be interested in fielding any > particular configuration settings and network settings I'd be willing to > oblige (just let me know what configs you'd like to see). A little ascii art of your network might be a good idea. cheers Erich > ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users |