[BitVisor-devel-en:88] vpn.mode functional clarification?

Dr. Lonnie Cumberland, PhD lonnie at outstep.com
Sat Jan 27 04:44:10 JST 2024


Hello All,

Hope that you are doing well today.

While I understand that the BitVisor (v1.1) documentation manual (v1.0) 
is very dated given all of the new features and changes that are out in 
the BitVisor v2.0 (mercurial) release, I would like to ask for a bit of 
clarification on how bitvisor functions relative to the "vpn.mode" setting:

Page 20 of the manual says:

"
The possible values of L2Trans and L3Trans correspond to transparent 
layer 2 and layer 3 modes, used for testing. In the L3IPsec mode, 
BitVisor will create the IPSec connection for data transmission.
"

Thus vpn.mode can be set to (L2Trans | L3Trans | L3IPsec) options.

What I read out of this is:

  * L2Trans --- This mode is a virtual switch which uses the MAC address
    for addressing
  * L3Trans --- This mode is a virtual router which uses the IP (IPv4 or
    IPv6) or other protocol for addressing and routing
  * L3IPsec --- This mods make bitvisor act as an IPsec "client" to
    connect to an external SWAN IPsec capable server like you might have
    by using a SoftEther VPN Server (https://www.softether.org) which
    supports IPsec clients and connecting to it via bitvisor.

My questions here are how the L2Trans and L3Trans function.

 1. Is it such that they act as virtual switch/router "server" so that
    others can connect to them which you might see in a private LAN
    configuration with multiple non-bitvisor clients connecting to a
    bitvisor node that is running a switch/router?
 2. Can other bitvisor instances connect to each other in these modes
    such that routers/switches can form a mesh network?
 3. Or, depending upon the above then does this allow for switch/router
    bridging?

For the L2/L3 switch/router questions, I would also be interested in how 
these modes are configured to make them functional as the manual does 
not really go into it much, and presumably without encryption I would 
guess if they act as normal virtual devices while encryption in the 
modes can be discussed much later, perhaps.

Thanks again and have a great evening,
Lonnie



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bitvisor.org/archives/bitvisor-devel-en/attachments/20240126/b49a4969/attachment.htm>


More information about the BitVisor-devel-en mailing list