|
|
"E. Versteegt" <eymert@xxxxxxxxxxxxx> said: > Hi! > > > James Yonan wrote: > > Eymert, > > > > > > > Yes, just get rid of all ifconfig* options in the client config, and don't use > > ifconfig-pool in the server config. > > > > James > > > > I already tried this, but with no effect. The warning about the > conflicting options stays. The client just keeps expecting --ifconfig > options in the server config (remote config), even when I don't mension > any --ifconfig anywhere. With 2.0-beta2 and later, --ifconfig* is not required with --mode server or connecting client, but only if tap interfaces are being used (--dev tap). You will also get a gentle warning from the server: MULTI: no dynamic or static remote --ifconfig address is available for x.x.x.x which is purely informational and does indicate an error condition. You cannot use --dev tun without --ifconfig on Windows. This is because tun interfaces require IP endpoints to be defined. James |