|
|
On Wednesday, August 18, 2004 1:14 PM [GMT-5=EST], Erik Anderson <erikba@xxxxxxxxxxxxxxxxx> wrote: > Just throwing a quick "FIXED" out to the list. I'm fairly certain > that the problem I was having was with the NAT switch not being able > to handle two machines establishing two UDP conversations to the same > port on the same machine... Good to hear. You're explanation is close. The OpenVPN server shouldn't have any problems handling multiple clients coming into the same UDP port. However, when there are multiple clients on the same NAT'd network, the server will get confused if they are all using the same local UDP port. This is why it is a good idea to define a unique local port for each client's configuration file on that subnet. In my case, since the clients are always the initiators, I don't even need to punch a hole through their firewall(s) to obtain a successful connection. Of course, the server, which BTW is also NAT'd, will require that the applicable port be accessible from the public side, not to mention having that port forwarded accordingly. Finally, I wanted to reiterate to James that the 'nobind' option solved my clients' reconnection issues that were previously mentioned in this thread. Thanks James! -Adam ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |