cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrija Panic <andrija.pa...@gmail.com>
Subject Re: Static NAT with multiple public interfaces uses wrong outgoing IP
Date Fri, 31 Jul 2020 11:15:27 GMT
Seems like a regression in 4.13 branch (well, after the 4.11.3 where it was
supposedly fixed) - there is a new bug report for the same:
https://github.com/apache/cloudstack/issues/4234

I've assigned it to 4.15 milestone, and hopefully someone will pick it up.

Best,

On Thu, 30 Jul 2020 at 17:29, li jerry <div8cn@hotmail.com> wrote:

> HI all
>        Recently we upgraded a set of CloudStack 4.7.1 to 4.13.1. After the
> upgrade, a static NAT with multiple public interfaces uses the wrong
> outgoing IP (all was normal before the upgrade)
>
> All NAT-failed networks have the following common points:
>
> 1. There are 2 or more public network nics on VR (eth2, eth3...), each nic
> has different public network ip
> 2. When VM Enable Static Nat, and Static Nat IP is not on the first public
> network nic (eth2), the exit of the VM will be source nat ip (it should be
> static nat ip if it is correct)
>
>
> The fault is very similar to this
> https://github.com/apache/cloudstack/issues/3168
>
>
> Has anyone encountered this problem? How should it be handled?
>
>
> Thanks to everyone who helped
> -Jerry
>
>

-- 

Andrija Panić

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message