> > This is really not *necessary*, but the way the code does tun & tap and > net30 & subnet, it gets confused about things. Needs fixing, sorry for > that. > > > > so in some cases a server-side statement > route 192.168.1.0 255.255.255.0 > works fine with 'topology net30' but NOT with 'topology subnet'. > > This is a long standing bug that needs to be fixed before we can > forcefeed everybody 'topology subnet'.
Okay. I see where the confusion is coming from. if you have net30, the second parameter for the ifconfig is always the gateway. In subnet you explicity need to set the gateway by setting/pushing route-gateway. In normal setups the --server macro automatically does that for you. I am not really seeing a bug here but a misconfiguration of OpenVPN. Sure the error messages could be improved and I am all ear to this. Arne
