Hi, On Wed, Jun 14, 2017 at 05:25:37PM -0400, Pippin1st wrote: > That`s how the picture looked in my mind the first time and made the > first diagram. Then changed it twice to correct the order of > comp/frag/enc. and traffic NOT passing routing & iptables > from OpenVPN to tun and back. > > Attached new diagram no.4
As far as I can see, this is factually correct and quite helpful in
understanding the packet flow through the full chain of "things involved"
- great work.
It's missing a small detail (which is not easy to add, admittedly) for
point-to-multipoint servers: there is a routing table *inside* the
openvpn process (iroute), which decides which client the packet should
receive. This happens between "read from tun" and "compress" (as
the compression algorithm is per-client).
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
