Though this port is not officially used (and marked as reserved) one
could craft packets and use 0 thus it's valid.
** Changed in: quantum
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1188246
Title:
Port 0 is accepted as a valid port-range value for security group rule
creation
Status in OpenStack Quantum (virtual network service):
Invalid
Bug description:
Port range is accepting port 0 as a valid port number. Security group
rule will be created for port 0.
quantum security-group-rule-create --direction ingress --protocol tcp
--port-range-min 0 --port-range-max 111 --remote-ip-prefix 0.0.0.0/0 bad
Created a new security_group_rule:
-------------------------------------------------------+
Field Value
-------------------------------------------------------+
direction ingress
ethertype IPv4
external_id
id 8437e51f-b1eb-4824-a56e-40e7c972878e
port_range_max 111
port_range_min 0
protocol tcp
security_group_id c38d90ec-519b-472e-8afc-b5711b83f6e0
source_group_id
source_ip_prefix
tenant_id 28312660553314
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1188246/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
