weizhouapache opened a new pull request #5078:
URL: https://github.com/apache/cloudstack/pull/5078


   ### Description
   
   when linux bridge is setup (refer to 
http://docs.cloudstack.apache.org/projects/archived-cloudstack-getting-started/en/latest/networking/vxlan.html#configure-product-to-use-vxlan-plugin)
 and used as the kvm traffic label of physical networks, the vms on different 
hosts cannot reach each other.
   
   (1) does not work:
   ```
   /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvxlan.sh -v 1001 
-p eth1 -b brvx-1001 -o add
   ```
   "bridge fdb" shows
   ```
   00:00:00:00:00:00 dev vxlan1001 dst 239.0.3.233 via eth1 self permanent
   ```
   
   (2) this works:
   ```
   /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvxlan.sh -v 1001 
-p cloudbr1 -b brvx-1001 -o add
   ```
   "bridge fdb" shows
   ```
   00:00:00:00:00:00 dev vxlan1001 dst 239.0.3.233 via cloudbr1 self permanent
   ```
   
   
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [X] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [X] Major
   - [ ] Minor
   - [ ] Trivial
   
   
   ### Screenshots (if appropriate):
   
   
   ### How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   <!-- see how your change affects other areas of the code, etc. -->
   
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
 document -->
   


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to