Re: [Openvpn-users] Linux(server) <-> W2K(client) all working fine except Samba

[Massimiliano Hofer <max@xxxxxxxxxx>]

Alle 11:41 PM, domenica 7 dicembre 2003, James Yonan ha scritto:

> The problem is that Windows lacks an API for setting the IP addresses of
> adapters.  The two methods presented are the IP helper API (ipapi) and
> netsh, and neither solve the problem 100%.
>
> The IP helper API (ipapi) only adds a secondary address to an adapter, not
> a primary address.  So if the primary address is undefined, Windows tries
> to give the bogus "autoconfiguration" address to it.  That's why you see a
> second address popping up.

This sounds utterly stupid to me. Why should Windows add an address without 
any request or negotiation?
I shouldn't have thought it was a problem of OpenVPN, but I recommend adding a 
very visibile note in the documentation and not recommending automatic 
address assignment.

> You can get away from this difficulty by using netsh instead of ipapi
> (--ip-win32 netsh).  But once again, netsh is buggy on some platforms.

I'll try it, but most of the time the manual configuration will be just fine. 
I tried the ipapi only because it was the recommended one.

> You need the ping option on both sides of the connection, and the
> connection establishment will occur when each side receives the ping from
> the other side. Then you can have a route-delay option to time the
> activation of the route directives relative to the point of connection
> establishment.

Thank your for your advice. I'll try it as soon as possible. I erroneously 
thought that receiving a ping implied a reply even without the ping option on 
the peer.

-- 
Bye,
   Massimiliano Hofer
        Nucleus