Opened 2 years ago

Last modified 2 weeks ago

#1082 new Bug / Defect

Not clear for how long does openVPN caches the resolved IP address of remote host

Reported by: teneri Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version: OpenVPN 2.4.4 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc: Gert Döring, plaisthos, themiron

Description

Currently when running openVPN client in log it says:

    Preserving recently used remote address:

For how long it will cache it? How to tune it?

Maybe best to add some info into man?

Change History (7)

comment:1 Changed 2 years ago by Antonio

There is no "timing" option to tune. The IP is either cached or not.
This particular behaviour can be activated when using "--persist-remote-ip".

However, before going into the details, I'd like to ask if you are having any issue with this option.

If this is not a bug or a feature request, I'd rather move the discussion tot he user mailing list where more people can express their opinion in this regard.

comment:2 Changed 2 years ago by teneri

Thank you, it's clear now.

Thought I don't have the "persist-remote-ip" option set but seeing the "Preserving recently used remote address" events in the log. Anything else except the "persist-remote-ip" option may be triggering this event?

comment:3 Changed 10 months ago by tincantech

Unqualified comment:
This must also be effected by other factors, such as having only one connection profile. I do not use --persist-remote-ip ever and yet almost all of my client logs show that the remote IP is preserved.

comment:4 Changed 10 months ago by Pippin

Another unqualified comment :)

Using

remote 1
remote 2
remote 3
remote 4
remote 5

remote-random

shows

Preserving recently used remote address:

but remote is actually random.

comment:5 Changed 4 weeks ago by tincantech

If the message:

Preserving recently used remote address:

is logged when openvpn is not preserving recently used remote address then this is a bug.

comment:6 Changed 4 weeks ago by tincantech

Cc: Gert Döring added

comment:7 Changed 2 weeks ago by Gert Döring

Cc: plaisthos themiron added

I have no idea what OpenVPN is trying to tell us there, TBH. That message has been there "since ever", but the surrounding code was rewritten a couple of times - so it might not send the "right" message today.

@plaisthos might know, or @themiron

Note: See TracTickets for help on using tickets.