|
|
<snip> > > would effect how packets pass thru a given Linux system? > > There's iptables; ebtables; the routing table; the settings in > /proc/sys/net/ipv4/ip_forward (and its interface-specific > equivalents)... and that's pretty much all that comes to mind off the > top of my head. > > ebtables is pretty new and almost never on by default -- This is very interesting to know about. Neither of the systems has the ebtables user space tools installed nor do I see the ebtables kernel module active with lsmod. I'm assuming this is not an issue but it looks worth looking into for the the future! > so if you > cleared iptables from the equation and the routing tables were set up > equivalently on both sides, the ip_forward settings in /proc are > probably the likely suspects. I turned on ip_forward relatively early during configuration. I know that it is turned on and the routing tables are fine as performing pings and traceroutes between the various systems was never an issue. I also had no problem reaching the WINs server on the server's subnet nor opening sockets to the OpenVPN client. The only issue was the ability to open TCP sockets on systems on the server subnet from the client, everything else worked, indicating the basic environment was correctly configured. Some were along the line, the TCP packets were being dropped or blocked in a specific case. Thanks for your responses, Brett ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users |