Hi,
On Wed, Apr 03, 2024 at 11:31:03AM +0200, Ralf Hildebrandt via Openvpn-users
wrote:
> 2024-02-21 11:37:04 TCP/UDP: Preserving recently used remote address:
> [AF_INET]193.175.73.xxx:1194
The code is a bit complex to read and I'm not sure I do understand it
(and maybe we broke it at some
On 03.04.24 13:30, Ralf Hildebrandt via Openvpn-users wrote:
I don't see such an option in the docs (for 2.6, to be precise), but let me
ask a question for clarification: Does your setup answer requests to a
now-disabled IP with some explicit denial (ICMP UNREACHABLE, RST, whatever),
No, since
> I shall assume that your question is "how do I tell the client *not* to try
> sticking to the last IP used?". ;-)
Yes!
> I don't see such an option in the docs (for 2.6, to be precise), but let me
> ask a question for clarification: Does your setup answer requests to a
> now-disabled IP with
On 03.04.24 11:31, Ralf Hildebrandt via Openvpn-users wrote:
We're using DNS Round-robin-records with a TTL of 300s for our openvpn
endpoint servers.
Yet, clients seem to reconnect to the same IP, although the DNS entry
has expired; the log usually shows something like:
2024-02-21 11:37:04
W dniu 3.04.2024 o 11:31, Ralf Hildebrandt via Openvpn-users pisze:
Hi!
We're using DNS Round-robin-records with a TTL of 300s for our openvpn
endpoint servers.
Yet, clients seem to reconnect to the same IP, although the DNS entry
has expired; the log usually shows something like:
2024-02-21
Hi!
We're using DNS Round-robin-records with a TTL of 300s for our openvpn
endpoint servers.
Yet, clients seem to reconnect to the same IP, although the DNS entry
has expired; the log usually shows something like:
2024-02-21 11:37:04 TCP/UDP: Preserving recently used remote address:
