[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

[Openvpn-users] OpenVPN: bridging the really weird networks


  • Subject: [Openvpn-users] OpenVPN: bridging the really weird networks
  • From: mts.spb.suxx@xxxxxxx
  • Date: Wed, 7 Sep 2005 12:54:10 +0400

Hello openvpn-users,

  In the quest for the most secure and fast networking in my really
  small LAN I've disabled "NetBIOS over TCP/IP" and installed NetBEUI
  instead. All the networking operates as expected, TCP/IP is used
  only for POP3, SMTP and HTTP access.

  Now I want to provide the remote connection to the LAN. The server
  part of the OpenVPN v2.0.2 is on winXP-SP2, the client part is on
  winXP-SP2 too.

  My network (on the client machine) bindings are:
    File_and_printer_sharing_for_MSnetworks->NetBEUI->TAP-win32
    Client_for_MSnetworks->NetBEUI->TAP-win32

  Do I get it right - I need to do the same binding with the "bridged
  connection" on the server machine? Like this:
    File_and_printer_sharing_for_MSnetworks->NetBEUI->dridged_TAP-win32_and_NIC
    Client_for_MSnetworks->NetBEUI->bridged_TAP-win32_and_NIC

  In my client's OpenVPN configuration:
       dev tap
       dev-node OpenVPN  # this is the renamed TAP-win32 adapter
  What should I put in the server's configuration? Is it:
       dev tap
       dev-node bridged_connection_name

 Do I get it right - since I'm bridging rather than routing - I need
 not care about the DNS, default gateway and other IP parameters?
 Especially if I'm on NetBEUI.

 Please comment.
 FAQ and readme are not very definitive on all this...
 
-- 
Best regards,
 Tony.           mailto:mts.spb.suxx@xxxxxxx


____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users