Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of nux@li.nux.ro designates
 31.193.175.196 as permitted sender)
Date: Tue, 19 Aug 2014 14:41:10 +0100 (BST)
From: Nux! <nux@li.nux.ro>
To: dev <dev@cloudstack.apache.org>, users@cloudstack.apache.org
Message-ID: <1275723333.73297.1408455670903.JavaMail.zimbra@li.nux.ro>
In-Reply-To: <1576880247.73290.1408455412683.JavaMail.zimbra@li.nux.ro>
References: <975735633.73185.1408446751396.JavaMail.zimbra@li.nux.ro>
 <325624325.73228.1408451121286.JavaMail.zimbra@li.nux.ro>
 <1576880247.73290.1408455412683.JavaMail.zimbra@li.nux.ro>
Subject: Re: VRouter sets the same public IP on 2 interfaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: VRouter sets the same public IP on 2 interfaces
Thread-Index: ifZBQzBCEPRwgN3PeoxbG45yYQIaLPETj0cRtpU4zI/jJWp3mA==

So the VR in the UI shows 3 NICs: isolated, control and public, but in SSH I see 4 NICs, of which eth2 and eth3 have the same IP settings and the SNAT is done on the wrong NIC (eth3 which doesn't seem to work, instead of eth2).

Any ideas? Where is this VR taking it's settings exactly?


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


----- Original Message -----
> From: "Nux!" <nux@li.nux.ro>
> To: "dev" <dev@cloudstack.apache.org>, users@cloudstack.apache.org
> Sent: Tuesday, 19 August, 2014 2:36:52 PM
> Subject: Re: VRouter sets the same public IP on 2 interfaces
> 
> I've added another zone and the problem is sadly very repeatable. :(
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> 
> ----- Original Message -----
> > From: "Nux!" <nux@li.nux.ro>
> > To: "dev" <dev@cloudstack.apache.org>, users@cloudstack.apache.org
> > Sent: Tuesday, 19 August, 2014 1:25:21 PM
> > Subject: Re: VRouter sets the same public IP on 2 interfaces
> > 
> > Right, so the SNAT on the VR is done on eth3 instead of eth2, not sure why
> > this is happening. Can't spot anything dodgy in the logs.
> > Once I remove the SNAT and add it on the eth2 (which has the same IP) then
> > all my egress rules start to work again.
> > 
> > I'll try to recreate the zone and hope this glitch goes away.
> > 
> > 
> > 
> > --
> > Sent from the Delta quadrant using Borg technology!
> > 
> > Nux!
> > www.nux.ro
> > 
> > 
> > ----- Original Message -----
> > > From: "Nux!" <nux@li.nux.ro>
> > > To: "dev" <dev@cloudstack.apache.org>, users@cloudstack.apache.org
> > > Sent: Tuesday, 19 August, 2014 12:12:31 PM
> > > Subject: VRouter sets the same public IP on 2 interfaces
> > > 
> > > Hi,
> > > 
> > > I have 4 networks defined (public, guest, storage and mgmt). It looks
> > > like
> > > the VR sets up two internal NIcs (eth2 and eth3) for connecting to the
> > > public network. It also sets the same IP address on them.
> > > Egress = Allow is also ignored and my VMs can't reach anything.
> > > 
> > > Has anyone seen this before? I'm on 4.3
> > > 
> > > Thanks
> > > 
> > > --
> > > Sent from the Delta quadrant using Borg technology!
> > > 
> > > Nux!
> > > www.nux.ro
> > > 
> > > 
> > 
>