On Wed, Apr 22, 2015 at 8:33 AM, Shanmugam Sundaram
<[email protected]> wrote:
> Thanks Gurucharan,
>
> I'm using Open vSwitch with Dockers along with VLAN.
>
> Docker (IP: 172.16.10.11/24  VLAN: 10) ----veth pair on ovs-bridge----->
> Host Machine (IP: 192.168.1.10/24 Gateway: 192.168.1.1 ).
>
> I'm currently using pipework script to achieve this. But I'm unable to
> connect to internet. I'm not sure how to achieve it, in the above setup.
Looks like you have a VLAN connection to the OVS bridge. Unless your
underlay knows how to re-direct packets with VLAN 10 to the correct
destination, it won't go anywhere.

>
> And also, is it possible to limit inbound connections to the docker using
> flow tables.
>
> Please help me on this with some directions, links
A VM connected to a OVS bridge can do all of the above. So there is no
reason on why it won't work with Docker.


>
> Thank You..
>
> regards,
> Shan
>
>
>
>
> On Wed, Apr 22, 2015 at 8:48 PM, Gurucharan Shetty <[email protected]>
> wrote:
>>
>> On Wed, Apr 22, 2015 at 7:55 AM, Shanmugam Sundaram
>> <[email protected]> wrote:
>> > Hi Team,
>> >
>> > I'm using linux veth pairs to connect across network namespaces.
>> > Especially
>> > in Dockers.
>> > Is it possible to use Open vSwitch Patch ports to connect two OVS
>> > Bridges,
>> > that are in two different namespaces.
>> > Say, I have bridge 'ovs-docker' inside docker and 'ovs-host' in the host
>> > machine, can we connect these two bridges using OVS Patch ports
>> I don't think it is possible. A patch port is visible only to the
>> userspace process. So patch ports will only work if you have a single
>> ovs-vswitchd daemon that can see both the bridges.
>>
>> >
>> > --
>> > regards,
>> > Shan
>> >
>> > _______________________________________________
>> > discuss mailing list
>> > [email protected]
>> > http://openvswitch.org/mailman/listinfo/discuss
>> >
>
>
>
>
> --
> regards,
> Shan
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to