Re: [Openvpn-users] Beta11 - client-to-client

[Matteo Lunardi <matteo.lunardi@xxxxxxxxx>]

Leonard Isham ha scritto:
> On Tue, 2 Nov 2004 09:55:09 -0500, Adam Pavelec wrote:
> > On Tuesday, November 02, 2004 2:12 AM [GMT-5=EST], Mathias Sundman wrote:
> > > > I've been experiencing a problem regarding the client-to-client
> > > > directive in my bridged configuration.  It seems that when I have
> > > > two or more remote clients behind the same subnet requesting
> > > > resources from eachother by netbios name, their traffic is routed
> > > > through the OpenVPN tunnel instead of being routed locally.  I've
> > > > been running Beta11 since its release, and it seems that this issue
> > > > has just recently appeared.  Am I missing something in my server
> > > > configuration to prevent this from happening?
...
> > > It's a matter of name resolution. Unfortunally I don't know how you
> > > should be able to set a "prefered" subnet. Windows will probably
> > > broadcast both subnets, or use the IP address it receives from a WINS
> > > server if you have specified one.
...
> > I fully understand the whole theory behind this, but it's really strange
> > that it only recently started affecting me.  It all began few weeks ago when
> > I noticed my VNC connections from my Wi-Fi connected laptop into my wired
> > desktop becoming completely laggy.  Pings were sometimes 4,000+ms, and I
> > began to think it was the Wi-Fi connection at my new residence.  Then I
> > actually paid attention and noticed that the pings were resolving to the
> > desktop's OpenVPN 'virtual' IP address instead of its local IP address.
...
> > > What happens:
> > > 1. Netbios resolution looks to the WINS server or master browser which
> > > has the bridged IP address related to the netbios name.
> > So, the OpenVPN client is receiving name resolution from the Master Browser
> > at the server site?
...
> > I may just end up removing the client-to-client form the server config.
...
> The issue is with MIcrosoft's name resolution.  Both clients are,
> apparently using the master browser on the server LAN and it only
> knows the TAP IP address.  Therefore using netbios will cause you to
> use OpenVPN.
...

I hope I understood well the matter...

If the problem is due to netbios resolution, you should check the 
netbios node type on the windows client with 'ipconfig /all' and try to 
setup someone different by checking this document:
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

You can encounter some troubles if you push the dhcp NetBT option with 
openvpn or with a local dhcp server, since node type is a machine based 
setting and not an interface setting: once it has been setup by one 
connection, if other connections don't setup a custom node type, it will 
be used for all interfaces:
http://sourceforge.net/mailarchive/message.php?msg_id=9530112

Maybe you should see what happens with a nodetype of 2, but beware that 
you could be unable even to log in with domain usernames if it doesn't 
work; no problems to log in with local usernames to restore the node 
type, or remove it to fall back to default.

Which OS there is/are on the clients?  For win2k/xp you could also check 
the status of the Computer Browser service, and start/stop it.


Bye.
Matteo

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