Re: Egress rules not applied in 4.11.0

Hi! Am 11.04.18 um 13:38 schrieb Stephan Seitz: Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But maybe you did a fresh installation. No, Upgrade from 4.9.2.0. I set the OS type to Debian 8 in ACS. "Debian 9.3" is what XenCenter

Re: Egress rules not applied in 4.11.0

sions were kind of > > picky > > > > > > > > > > > with different kinds of Xen virtualization as I've seen on "regular" > > VMs. > > > > > > > > > > > > > > > > > > > &g

Re: Egress rules not applied in 4.11.0

, den 11.04.2018, 11:42 + schrieb Paul Angus: > > > > > > > > > > > > > > > virt-what will give 'xen-domU' for paravirtualized guests. Didn't > > > XenServer make some kind of change around this as a Meltdown/Spectre > > >

Re: Egress rules not applied in 4.11.0

ke some kind of change around this as a Meltdown/Spectre > > migation? > > > > > > > > > > > > > > > > > > > Kind regards, > > > > > > > > Paul Angus > > > > > > > > paul.an...@shapeblue.com &

Re: Egress rules not applied in 4.11.0

t; > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > > @shapeblue > > > > > > > > > > > > > > > -Original Message- > > > From: Stephan Seitz <s.se...@heinlein-support.de> > > > Sent: 11 April 2018 12:

Re: Egress rules not applied in 4.11.0

.com > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK > > @shapeblue > >    > >   > > > > > > -Original Message- > > From: Stephan Seitz <s.se...@heinlein-support.de>  > > Sent: 11 April 2018 12:38 > > To: users@cloud

Re: Egress rules not applied in 4.11.0

gt;   > > > -Original Message- > From: Stephan Seitz <s.se...@heinlein-support.de>  > Sent: 11 April 2018 12:38 > To: users@cloudstack.apache.org > Subject: Re: Egress rules not applied in 4.11.0 > > Hi martin, > > I've just read your issue on github a

RE: Egress rules not applied in 4.11.0

-Original Message- From: Stephan Seitz <s.se...@heinlein-support.de> Sent: 11 April 2018 12:38 To: users@cloudstack.apache.org Subject: Re: Egress rules not applied in 4.11.0 Hi martin, I've just read your issue on github and was wondering how you;ve been able to select Debian 9. But may

Re: Egress rules not applied in 4.11.0

> > https://github.com/apache/cloudstack/pull/2508/files#diff-2d3ea57dfd9156e3983b1bb2d64abecd > > > > > > > > > > > > - Rohit > > > > > > <https://cloudstack.apache.org> > > > > > > > >

Re: Egress rules not applied in 4.11.0

pull/2508/files#diff-2d3ea57dfd9156e3983b1bb2d64abecd - Rohit <https://cloudstack.apache.org> From: Martin Emrich <martin.emr...@empolis.com> Sent: Tuesday, April 10, 2018 2:13:57 PM To: CloudStack-Users Subject: Egress rules not applied in 4.11.0

Re: Egress rules not applied in 4.11.0

<martin.emr...@empolis.com> Sent: Tuesday, April 10, 2018 2:13:57 PM To: CloudStack-Users Subject: Egress rules not applied in 4.11.0 Hi! I upgraded my test cluster from 4.9 to 4.11. The default policy for isolated networks is "Deny". But now, adding rules to allow egress tra

Re: Egress rules not applied in 4.11.0

sers Subject: Egress rules not applied in 4.11.0 Hi! I upgraded my test cluster from 4.9 to 4.11. The default policy for isolated networks is "Deny". But now, adding rules to allow egress traffic are not applied to the virtual router. adding a 0.0.0.0/0 rule looks fine from the U

Re: Egress rules not applied in 4.11.0

Hi! Am 10.04.18 um 11:09 schrieb Stephan Seitz: Hi! I think your facing a bug already discussed here. After reloading (imho doesn't matter if you check "clean up") the network, the egress rules are applied. So just reload every net with egress rules :) IIRC I tried that several times with no

Re: Egress rules not applied in 4.11.0

No need to open an issue ticket. There is already a PR to fix it. https://github.com/apache/cloudstack/pull/2514 On Tue, Apr 10, 2018 at 6:09 AM, Stephan Seitz wrote: > Hi! > > I think your facing a bug already discussed here. After reloading (imho > doesn't matter

Re: Egress rules not applied in 4.11.0

Hi! I think your facing a bug already discussed here. After reloading (imho doesn't matter if you check "clean up") the network, the egress rules are applied. So just reload every net with egress rules :) Oh and don't know if that made it already to  https://github.com/apache/cloudstack/issues 

Egress rules not applied in 4.11.0

Hi! I upgraded my test cluster from 4.9 to 4.11. The default policy for isolated networks is "Deny". But now, adding rules to allow egress traffic are not applied to the virtual router. adding a 0.0.0.0/0 rule looks fine from the UI, but does not appear in the iptables output on the VR.