|
|
Alohá!
/dev/rob0 wrote:
http://openvpn.net/static.html
http://openvpn.net/1xhowto.html
thx
If you don't need multiple client connections, why bother with a
server/client setup?
As posted, road warriors and more remote LANs coming up.
Turn on proxy
ARP, and life is good. 192.168.16.0/24 hosts have routes to
192.168.40.0/24 through 192.168.16.40 =OR= openvpn is running on (or
the peer is reached through) their default gateway. 192.168.40.0/24
hosts have routes to 192.168.16.0/24 through 192.168.40.16 =OR= openvpn
is running on (or the peer is reached through) their default gateway.
Symmetry is good!
The latter is my case. Looking at my diagram and routes shows that this
is the case for me, unfortunately I cannot host OpenVPN on the default
gateway of LAN A as that is an appliance firewall but since that one is
forwarding 192.168.122.0/24 as well as 10.8.0.0./16 to server A things
should work out - as they do for connections from LAN B to LAN A...
Firewalls, well, generally I treat tun+ interfaces like trusted local
ones.
Same here, see first post.
regards
Martin
____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|