ds with the new releases (
Andrei
- Original Message -
> From: "Andrija Panic"
> To: "dev"
> Sent: Monday, 9 July, 2018 22:39:06
> Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
> Andrei, if not mistaken I believe I saw same behavior eve
t; in the latest 4.11 maintenance release? I thought that it would be as it
> breaks the major function of the VPC.
>
> Cheers.
>
> Andrei
>
> - Original Message -
> > From: "Andrei Mikhailovsky"
> > To: "dev"
> > Sent: Friday, 20
t it would be as it breaks the major function
of the VPC.
Cheers.
Andrei
- Original Message -
> From: "Andrei Mikhailovsky"
> To: "dev"
> Sent: Friday, 20 April, 2018 11:52:30
> Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
Thanks
- Original Message -
> From: "Rohit Yadav"
> To: "dev" , "dev"
> Sent: Friday, 20 April, 2018 10:35:55
> Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
> Hi Andrei,
>
> I've fixed this recently, ple
From: Andrei Mikhailovsky
Sent: Friday, 20 April, 2:21 PM
Subject: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
To: dev
Hello, I have been posting to the users thread about this issue. here is a
quick summary in case if people contributing to the source nat code on the VPC
side would
Hello,
I have been posting to the users thread about this issue. here is a quick
summary in case if people contributing to the source nat code on the VPC side
would like to fix this issue.
Problem summary: no connectivity between virtual machines behind two Static NAT
networks.
Problem ca
