Table of contents

3.6 Local Bridges

    Table of contents
    You are currently comparing two old versions - only when you are comparing against the latest version can you revert. Return to version archive.

    Combined revision comparison

    Comparing version 18:57, 3 Mar 2013 by genya with version 16:55, 4 Mar 2013 by yagi.

    ...

    Using a local bridge makes it possible to easily construct a remote-access VPN and site-to-site VPN. For details, please refer to #10.4 Build a Generic Remote Access VPN#, #, 10.5Build a LAN-to-LAN VPN (Using L2 Bridge)# and #10.6Build a LAN-to-LAN VPN (Using L3 IP Routing)#..

    ...

    Using a function like the one described in #3.4.10#3.4 Virtual Hub Functions enables users making a VPN connection to a Virtual Hub to receive (intercept) all virtual Ethernet frames flowing within that Virtual Hub. A similar operation can be performed for locally bridged Virtual Network Adapters.

    ...

    Connecting a separate device to the LAN port of a network adapter set up in monitor mode enables that device to intercept all packets flowing over that the Virtual Hub. As is the case in monitoring mode (see #3.4.10#),3.4 Virtual Hub Functions), packets cannot be transmitted within the virtual LAN.

    ...

    • To use the local bridge function it is necessary to launch the VPN Server / VPN Bridge in Service Mode (root authority is required when launching in User Mode).
    • The local bridge function is disabled when the VPN Server / VPN Bridge is launched with general user authority.
    • It is necessary to embed a socket interface for low level access to the network adapter (also referred to as a packet socket) in the Linux kernel if one is not already present. This is not a problem for most of the recent Linux kernels.
    • When communication instability occurs as a result of using a network adapter which supports hardware floating to make the local bridge connection, disable said hardware floating. Please refer to your hardware manual for details.
    • Limitations within the Linux or UNIX operating system prevent communication with IP addresses assigned to the network adapter locally bridged from the VPN side (Virtual Hub side). The cause of this restriction lies with OS's internal kernel codes rather than with the SoftEther VPN. When wishing to communicate in any form with a UNIX computer used for local bridging from the VPN side (Virtual Hub side), (for instance, when running both the VPN Server / VPN Bridge service & the HTTP Server service and wishing to grant access to the server service from the VPN side as well), prepare and connect a local bridge network adapter and physically connect both it and the existing network adapter to the same segment (as explained in #3.6.3#,3.6 Local Bridges, it is recommended to prepare a network adapter for exclusive use in local bridging for this and other situations).
    • While Windows enables device names to be designated for all network adapter names, in UNIX, network device names such as eth0, eth1 and so on are designated. These device names can be obtained using the [ifconfig -a] command.

    Version from 18:57, 3 Mar 2013

    This revision modified by genya (Ban)

    ...

    Using a local bridge makes it possible to easily construct a remote-access VPN and site-to-site VPN. For details, please refer to #10.4#, #10.5# and #10.6#.

    ...

    Using a function like the one described in #3.4.10# enables users making a VPN connection to a Virtual Hub to receive (intercept) all virtual Ethernet frames flowing within that Virtual Hub. A similar operation can be performed for locally bridged Virtual Network Adapters.

    ...

    Connecting a separate device to the LAN port of a network adapter set up in monitor mode enables that device to intercept all packets flowing over that the Virtual Hub. As is the case in monitoring mode (see #3.4.10#), packets cannot be transmitted within the virtual LAN.

    ...

    • To use the local bridge function it is necessary to launch the VPN Server / VPN Bridge in Service Mode (root authority is required when launching in User Mode).
    • The local bridge function is disabled when the VPN Server / VPN Bridge is launched with general user authority.
    • It is necessary to embed a socket interface for low level access to the network adapter (also referred to as a packet socket) in the Linux kernel if one is not already present. This is not a problem for most of the recent Linux kernels.
    • When communication instability occurs as a result of using a network adapter which supports hardware floating to make the local bridge connection, disable said hardware floating. Please refer to your hardware manual for details.
    • Limitations within the Linux or UNIX operating system prevent communication with IP addresses assigned to the network adapter locally bridged from the VPN side (Virtual Hub side). The cause of this restriction lies with OS's internal kernel codes rather than with the SoftEther VPN. When wishing to communicate in any form with a UNIX computer used for local bridging from the VPN side (Virtual Hub side), (for instance, when running both the VPN Server / VPN Bridge service & the HTTP Server service and wishing to grant access to the server service from the VPN side as well), prepare and connect a local bridge network adapter and physically connect both it and the existing network adapter to the same segment (as explained in #3.6.3#, it is recommended to prepare a network adapter for exclusive use in local bridging for this and other situations).
    • While Windows enables device names to be designated for all network adapter names, in UNIX, network device names such as eth0, eth1 and so on are designated. These device names can be obtained using the [ifconfig -a] command.

    Version as of 16:55, 4 Mar 2013

    This revision modified by yagi (Ban)

    ...

    Using a local bridge makes it possible to easily construct a remote-access VPN and site-to-site VPN. For details, please refer to 10.4 Build a Generic Remote Access VPN, 10.5Build a LAN-to-LAN VPN (Using L2 Bridge) and 10.6Build a LAN-to-LAN VPN (Using L3 IP Routing).

    ...

    Using a function like the one described in 3.4 Virtual Hub Functions enables users making a VPN connection to a Virtual Hub to receive (intercept) all virtual Ethernet frames flowing within that Virtual Hub. A similar operation can be performed for locally bridged Virtual Network Adapters.

    ...

    Connecting a separate device to the LAN port of a network adapter set up in monitor mode enables that device to intercept all packets flowing over that the Virtual Hub. As is the case in monitoring mode (see 3.4 Virtual Hub Functions), packets cannot be transmitted within the virtual LAN.

    ...

    • To use the local bridge function it is necessary to launch the VPN Server / VPN Bridge in Service Mode (root authority is required when launching in User Mode).
    • The local bridge function is disabled when the VPN Server / VPN Bridge is launched with general user authority.
    • It is necessary to embed a socket interface for low level access to the network adapter (also referred to as a packet socket) in the Linux kernel if one is not already present. This is not a problem for most of the recent Linux kernels.
    • When communication instability occurs as a result of using a network adapter which supports hardware floating to make the local bridge connection, disable said hardware floating. Please refer to your hardware manual for details.
    • Limitations within the Linux or UNIX operating system prevent communication with IP addresses assigned to the network adapter locally bridged from the VPN side (Virtual Hub side). The cause of this restriction lies with OS's internal kernel codes rather than with the SoftEther VPN. When wishing to communicate in any form with a UNIX computer used for local bridging from the VPN side (Virtual Hub side), (for instance, when running both the VPN Server / VPN Bridge service & the HTTP Server service and wishing to grant access to the server service from the VPN side as well), prepare and connect a local bridge network adapter and physically connect both it and the existing network adapter to the same segment (as explained in 3.6 Local Bridges, it is recommended to prepare a network adapter for exclusive use in local bridging for this and other situations).
    • While Windows enables device names to be designated for all network adapter names, in UNIX, network device names such as eth0, eth1 and so on are designated. These device names can be obtained using the [ifconfig -a] command.