ifup-ens192 opened a new issue, #8459:
URL: https://github.com/apache/cloudstack/issues/8459
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
VPC network
-->
~~~
~~~
##### CLOUDSTACK VERSION
<!--
CloudStack 4.18.1
-->
~~~
~~~
##### CONFIGURATION
<!--
advanced networking
-->
##### OS / ENVIRONMENT
<!--
CentOS 7.9
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Under the newly created VPC network, even without any configuration.
Instances located in different layers can still communicate with each other at
will.
##### STEPS TO REPRODUCE
<!-- Paste example playbooks or commands between quotes below -->
~~~
The following is my entire operation process. First, create a new vpc
network.
Use default network scheme and default ACL rules
The same goes for the other one
This is the network plan I just checked. This is the network plan that comes
with acs. I have not made any modifications.
Next I use the vpc network I just created to create two instances
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
As expected, the two instances should not be able to ping each other, but
the actual situation is the opposite.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Enter the instance from the console and ping the IP addresses of the two
machines.
Finally, attach a screenshot of the virtual router. Its status is normal.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
