|
|
"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. Are you using 2.0-beta2 on both sides of connection? The ability to omit client --ifconfig is a recent development. James |