yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #32601
[Bug 1449344] Re: When VM security group is not choosen, the packets are still blocked by default
It's by design behavior, marking bus as Invalid
** Summary changed:
- When VM security group is not choose,the packets is still block by security group
+ When VM security group is not choosen, the packets are still blocked by default
** Summary changed:
- When VM security group is not choosen, the packets are still blocked by default
+ When VM security group is not chosen, the packets are still blocked by default
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1449344
Title:
When VM security group is not chosen, the packets are still blocked by
default
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
1.1 Under test tenement,create network:net1,subnet:subnet1,network address:192.168.1.0/24 and other keep default
1.2 Create router:R1,R1 inner interface relate to subnet1 and set outer network for R1
1.2 Create VM1-1,choose subnet1,security group choose default and firewall is closed
1.3 Edit security group of VM1-1,remove default security group from VM-1,now VM1-1 security group is none
1.4 VM1-1 ping subnet1 gw:192.168.1.1 fail
Capture in tap.xxx of linux bridge which is connect to VM1-1 ,we can see icmp request packets which is go to 192.168.1.1 from VM1-1
Capture in qvb.xxx,we can't see any packets.Therefore,the packets is deny by security group.But VM1-1 security group is not choose
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1449344/+subscriptions
References