Hi Berry,
That "round robin" behavior of your OpenVPN is probably due to having a domain
name in your client configuration file. (e.g, your clients are getting/resolving
the IP(s) of your server via DNS.)
The result that you get from ipinfo is normal, simply because your "default" IP
(the one that the OS is using for sending the network packets) is still your
primary("A") address. (You can think of that "alias" thing as "In addition to
my default IP address, which is A, I also respond to the packets that are
designated for my alias/secondary IP address, which is B.")
On Tue, Jun 5, 2018 at 7:52 PM, Berry Wendermouth <bayb...@riseup.net> wrote:
> Hi.
>
> Some days ago I received a second public IP address ("B") for my VPS /
> OpenBSD system. In order for this ip to be available I added it as an
> alias to my first public IP "A" as described in [1].
>
> I am also running an OpenVPN server on this machine.
>
> When I check for the public ip [2] the original IP "A" is constantly
> reported.
>
> When I check from a connected VPN client the public IP is returned in
> a "Round Robin" manner, switching between "A" and "B" for each check.
>
> As I understand this problem is likely related to my pf.conf.
> Before I go into that I'm wondering how this "round robin" behavior is
> even possible in the first place.
>
> Thank you for your feedback and comments.
>
> B.W.
>
> ---
> [1] "Setting up aliases on an interface"
> https://www.openbsd.org/faq/faq6.html
> [2] for example with `curl ipinfo.io/ip`
>
--
Best regards
Sohrab Monfared
