Table of contents
Combined revision comparison
...
Local BridgeFig. 3-6-1 Local bridge function
.
...
Fig. 3-6-2 Local bridge settings window.
...
Fig. 3-6-3 Preparing the local bridge network adapter.
...
Fig. 3-6-4 Removing protocol stacks from local bridge network adapter.
...
Fig. 3-6-5 Setting a fixed IP address for the Local bridge network adapter.
...
Fig. 3-6-6 Local bridge session status window
.
...
Manufacturer | Product Series | Link Type |
Intel | Intel PRO or Gigabit Adapter series | 100Base-TX 1000Base-T 1000Base-SX 1000Base-LX 10GBase-SR 10GBase-LR |
Broadcom | Broadcom NetXtreme series | 100Base-TX 1000Base-T |
3Com | 3Com series | 100Base-TX 1000Base-T |
...
Fig. 3-6-7 This figure shows a normal VPN session in monitor mode, but network adapters in this mode are able to physically receive all Ethernet frames within the Virtual Hub in the same way as this System Administrator.
...
3.6.11 Points to Note when Local Bridging in Linux, FreeBSD, Solaris or Mac OS X
The following precautions should be noted when using the local bridge function on a Linux / UNIX operating system.
- 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
Linux's internal configurationrather than with the SoftEther VPN. When wishing to communicate in any form with a UNIXLinuxcomputer 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
Linux, network device names such as eth0, eth1 and so on are designated. These device names can be obtained using the [ifconfig -a] command.
Other changes:
- /body/p[6]/a/@class:
" external"⇒ nothing - /body/p[6]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-1.gif"⇒ "http://www.softether.org/@api/deki/files/209/=3-6-1.png" - /body/p[6]/a/@title: nothing ⇒ "3-6-1.png"
- /body/p[6]/a/img/@alt:
"Click to enlarge."⇒ "3-6-1.png" - /body/p[6]/a/img/@border:
"2"⇒ nothing - /body/p[6]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-1_small.jpg"⇒ "/@api/deki/files/209/=3-6-1.png?size=webview" - /body/p[6]/a/img/@class: nothing ⇒ "internal default"
- /body/p[6]/a/img/@style: nothing ⇒ "width: 550px; height: 303px;"
- /body/p[7]/@style: nothing ⇒ "text-align: center; "
- /body/p[14]/a/@class:
" external"⇒ nothing - /body/p[14]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-2.gif"⇒ "http://www.softether.org/@api/deki/files/210/=3-6-2.png" - /body/p[14]/a/@title: nothing ⇒ "3-6-2.png"
- /body/p[14]/a/img/@alt:
"Click to enlarge."⇒ "3-6-2.png" - /body/p[14]/a/img/@border:
"2"⇒ nothing - /body/p[14]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-2_small.jpg"⇒ "/@api/deki/files/210/=3-6-2.png?size=webview" - /body/p[14]/a/img/@class: nothing ⇒ "internal default"
- /body/p[14]/a/img/@style: nothing ⇒ "width: 550px; height: 509px;"
- /body/p[15]/@style: nothing ⇒ "text-align: center; "
- /body/p[23]/a/@class:
" external"⇒ nothing - /body/p[23]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-3.gif"⇒ "http://www.softether.org/@api/deki/files/211/=3-6-3.png" - /body/p[23]/a/@title: nothing ⇒ "3-6-3.png"
- /body/p[23]/a/img/@alt:
"Click to enlarge."⇒ "3-6-3.png" - /body/p[23]/a/img/@border:
"2"⇒ nothing - /body/p[23]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-3_small.jpg"⇒ "/@api/deki/files/211/=3-6-3.png?size=webview" - /body/p[23]/a/img/@class: nothing ⇒ "internal default"
- /body/p[23]/a/img/@style: nothing ⇒ "width: 550px; height: 221px;"
- /body/p[24]/@style: nothing ⇒ "text-align: center; "
- /body/p[27]/a/@class:
" external"⇒ nothing - /body/p[27]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-4.gif"⇒ "http://www.softether.org/@api/deki/files/212/=3-6-4.png" - /body/p[27]/a/@title: nothing ⇒ "3-6-4.png"
- /body/p[27]/a/img/@alt:
"Click to enlarge."⇒ "3-6-4.png" - /body/p[27]/a/img/@border:
"2"⇒ nothing - /body/p[27]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-4_small.jpg"⇒ "/@api/deki/files/212/=3-6-4.png?size=webview" - /body/p[27]/a/img/@class: nothing ⇒ "internal default"
- /body/p[27]/a/img/@style: nothing ⇒ "width: 277px; height: 350px;"
- /body/p[28]/@style: nothing ⇒ "text-align: center; "
- /body/p[30]/a/@class:
" external"⇒ nothing - /body/p[30]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-5.gif"⇒ "http://www.softether.org/@api/deki/files/213/=3-6-5.png" - /body/p[30]/a/@title: nothing ⇒ "3-6-5.png"
- /body/p[30]/a/img/@alt:
"Click to enlarge."⇒ "3-6-5.png" - /body/p[30]/a/img/@border:
"2"⇒ nothing - /body/p[30]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-5_small.jpg"⇒ "/@api/deki/files/213/=3-6-5.png?size=webview" - /body/p[30]/a/img/@class: nothing ⇒ "internal default"
- /body/p[30]/a/img/@style: nothing ⇒ "width: 313px; height: 350px;"
- /body/p[31]/@style: nothing ⇒ "text-align: center; "
- /body/p[34]/a/@class:
" external"⇒ nothing - /body/p[34]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-6.gif"⇒ "http://www.softether.org/@api/deki/files/214/=3-6-6.png" - /body/p[34]/a/@title: nothing ⇒ "3-6-6.png"
- /body/p[34]/a/img/@alt:
"Click to enlarge."⇒ "3-6-6.png" - /body/p[34]/a/img/@border:
"2"⇒ nothing - /body/p[34]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-6_small.jpg"⇒ "/@api/deki/files/214/=3-6-6.png?size=webview" - /body/p[34]/a/img/@class: nothing ⇒ "internal default"
- /body/p[34]/a/img/@style: nothing ⇒ "width: 550px; height: 435px;"
- /body/p[35]/@style: nothing ⇒ "text-align: center; "
- /body/p[52]/a/@class:
" external"⇒ nothing - /body/p[52]/a/@href:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images/3-6-7.gif"⇒ "http://www.softether.org/@api/deki/files/215/=3-6-7.png" - /body/p[52]/a/@title: nothing ⇒ "3-6-7.png"
- /body/p[52]/a/img/@alt:
"Click to enlarge."⇒ "3-6-7.png" - /body/p[52]/a/img/@border:
"2"⇒ nothing - /body/p[52]/a/img/@src:
"file:///C:/TMP/130301vpn4man/VPN4%20Manual%20(English)/html/images_small/3-6-7_small.jpg"⇒ "/@api/deki/files/215/=3-6-7.png?size=webview" - /body/p[52]/a/img/@class: nothing ⇒ "internal default"
- /body/p[52]/a/img/@style: nothing ⇒ "width: 550px; height: 221px;"
- /body/p[53]/@style: nothing ⇒ "text-align: center; "
Version from 16:39, 2 Mar 2013
...
...
...
...
...
...
...
Manufacturer | Product Series | |
Intel | Intel PRO series | 100Base-TX 1000Base-T 1000Base-SX 1000Base-LX 10GBase-SR 10GBase-LR |
Broadcom | Broadcom NetXtreme series | 100Base-TX 1000Base-T |
3Com | 3Com series | 100Base-TX 1000Base-T |
...
...
- 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 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
Linux's internal configurationrather than with the SoftEther VPN. When wishing to communicate in any form with aLinuxcomputer 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
Linux, network device names such as eth0, eth1 and so on are designated. These device names can be obtained using the [ifconfig -a] command.
...
3.6.12 Points to Note when Local Bridging in Solaris
The following precautions should be noted when using the local bridge function on a Solaris operating system.
The VPN Server / VPN Bridge must be operated with root authority to use the local bridge function.The local bridge function is disabled when the VPN Server / VPN Bridge is launched with general user authority.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 Solaris 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 Solaris's internal configuration rather than with the SoftEther VPN. When wishing to communicate in any form with a Solaris 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 Solaris, network device names such as e1000 and so on are designated. These device names can be obtained using the[ifconfig -a]command.
Current version
...
Local Bridge function.
...
Local bridge settings window.
...
Preparing the local bridge network adapter.
...
Removing protocol stacks from local bridge network adapter.
...
Setting a fixed IP address for the Local bridge network adapter.
...
Local bridge session status window.
...
Manufacturer | Product Series | Link Type |
Intel | Intel PRO or Gigabit Adapter series | 100Base-TX 1000Base-T 1000Base-SX 1000Base-LX 10GBase-SR 10GBase-LR |
Broadcom | Broadcom NetXtreme series | 100Base-TX 1000Base-T |
3Com | 3Com series | 100Base-TX 1000Base-T |
...
3.6.11 Points to Note when Local Bridging in Linux, FreeBSD, Solaris or Mac OS X
The following precautions should be noted when using the local bridge function on a Linux / UNIX operating system.
- 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.