[ovs-discuss] Docker & Open vSwitch question.
batmanustc at gmail.com
Wed Nov 14 06:41:35 UTC 2018
So your solution is:
0) add br1 and add patch port to br0, and add eth0(port to outside) to br0
1) config vlan100 on container1, access mode
2) config vlan200 on container2, access mode
3) config vlan100/200 on patch port of br1, trunk mode
4) config vlan100/200 on patch port of br0, trunk mode, and config flow to
remove vlan tag when output to eth0
Is that right?
Orabuntu-LXC <gilbert at orabuntu-lxc.com> 于2018年11月4日周日 下午9:02写道：
> I guess by "patch" you mean "patch ports" . I think you will need to bring
> VLANs into the solution to accomplish what you are describing. My
> Orabuntu-LXC software ( https://github.com/gstanden/orabuntu-lxc ) uses a
> scheme of this type.
> HTH Gilbert
> On Sat, Nov 3, 2018, 9:15 AM Kevin Swagger <kdawg1496 at gmail.com> wrote:
>> I am trying to have two separate networks each with an OVS bridge. I have
>> a few docker containers connected to each bridge. I used a command like
>> "ovs-docker add-port ovs-br1 eth1 container1 " to connect the docker
>> containers to the bridges. I tried creating my own docker network that all
>> the containers used and when I removed the patch connection between the two
>> bridges the containers could still communicate. When I created two separate
>> docker networks the containers could not communicate to the other network
>> of containers. Is there a way I can accomplish my goal?
>> I want the two Open vSwitch bridges to be able to communicate by a patch.
>> I want the docker containers to only communicate over the patch and if I
>> remove the patch I want the containers to not be able to communicate.
>> Thank you
>> discuss mailing list
>> discuss at openvswitch.org
> discuss mailing list
> discuss at openvswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss