Ok, this is an very intressting point! I would prefere to add port-security maybe an system switch to change this behavior in runtime (of cource, it need an re-provisining).

Is there an releation with my other problem? One Instance with multiple Networks and for every Network an floating IP -> only one floating IP is working all other are without any response? Also port-forwarding in the router are broken and do not word …

 

Von: Curtis [mailto:serverascode@gmail.com]
Gesendet: Freitag, 29. März 2019 19:44
An: von Hoesslin, Volker
Cc: starlingx-discuss@lists.starlingx.io
Betreff: Re: [Starlingx-discuss] pre-stable version bevor next release?

 

On Fri, Mar 29, 2019 at 10:55 AM von Hoesslin, Volker <Volker.Hoesslin@swsn.de> wrote:

Hi anybody,

i realy love this project but I have some reason to deploy now an working stack. Is there currently an working version or have to wait until new release date? The current stable version isn’t working in all details for me, look at discuss “Unrecognized attribute(s) 'port_security_enabled'”.

 

 

With regards to port security, I tried to write this email a couple times, it's tough b/c I don't know the history, but here are my thoughts:

 

- Security groups are effectively disabled in stx (noop driver), at least in my deployment from an ISO from last week

- This is probably for performance reasons, ie. iptables, but I'm not sure of the history

- Maybe it's time to revisit security groups? eg. k8s is there and uses iptables, or maybe openflow based driver would be an option...or other?

- Likely we (the project) just need to make sure it gets properly documented, if it's not already

 

Maybe some others with more history will chip in. :)

 

Thanks,

Curtis

 

 

 

Thx,

Volker…

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss



--

Blog: serverascode.com