Re: [Openvpn-users] a few problem/comment/bug with version 2.1.x

[Charles Duffy <cduffy@xxxxxxxxxxx>]

Farkas Levente wrote:
> - why not accept among the server.conf's push the following options:
>   - persist-remote-ip
>   - keepalive
>   this has a good reason or just forget to include. imho it'd useful.
>   "Options error: option 'persist-remote-ip' cannot be used in this context
>    Options error: option 'keepalive' cannot be used in this context"

keepalive is a macro which pushes *other* values; it doesn't make sense 
to push it.

> - if i set the above server network then i've got in the log file:
>   "IFCONFIG POOL: base=192.168.254.2 size=252
>    IFCONFIG POOL LIST"
>   in this case i still can use in the ccd/* files eg. the following:
>   ifconfig-push 192.168.254.2 255.255.255.0
>   or i should have to use different network for the fixed ip? or?

You can still use ifconfig-push in cases where a pool is in use. I don't 
know the semantics regarding how these work together; you might need to 
push IPs which are outside of the pool to get correct operation.

>   wouldn't it be much better, cleaner and easier if the client-to-client
>   defined and an iroute in the ccd/* files also 'generate' the above
>   route command and push command for all clients except the ones who
>   owns the network?

This would make it necessary to read and evaluate *all* ccd files before 
deciding what any of them did, and this would mean that the OpenVPN 
daemon would need to watch all such files for modification (rather than 
just reading the relevant single file at connect time). I'm not sure I 
like it much.

That said, though, feature inclusion is a call for James.



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