[ovs-discuss] internal port problem
Jesse Gross
jesse at nicira.com
Mon Mar 18 04:55:18 UTC 2013
I would recommend reading the ovs-ofctl man page for examples. Your
description is too vague to be more specific than that.
On Sun, Mar 17, 2013 at 7:46 PM, Fang <wchunx416 at 126.com> wrote:
> Just want to try.If I use different bridges,VM cannot access to the
> internet.I am now trying to link the virtual environment into the physical
> network using OVS.
>
>
>
>
>
>
> At 2013-03-18 08:46:02,"Jesse Gross" <jesse at nicira.com> wrote:
>>On Fri, Mar 15, 2013 at 9:06 PM, Fang <wchunx416 at 126.com> wrote:
>>> At 2013-03-15 23:31:07,"Jesse Gross" <jesse at nicira.com> wrote:
>>>>On Thu, Mar 14, 2013 at 10:28 PM, Fang <wchunx416 at 126.com> wrote:
>>>>> Thank you for your reply.I have two more questions.
>>>>> 1.What's the difference between "internal port" and "fake bridge"?I can
>>>>> use
>>>>> "fake bridge" to replace "internal port" in my test.
>>>>
>>>>A fake bridge uses an internal port to emulate the vlan model used by
>>>>the Linux bridge. Therefore, they are functionally the same but a
>>>>fake bridge allows the use of bridge commands to manipulate it. If
>>>>you don't have existing tools then it is better to not use this
>>>>compatibility layer.
>>>>
>>>>> 2.If I use gre tunnel,i have to add the gre port to the different
>>>>> bridge
>>>>> with the host NIC(eth0).Is there any way to put "gre port"
>>>>> and eth0 on one bridge without causing a loop?
>>>>
>>>>You could use OpenFlow rules to completely isolate them. This
>>>>basically just creates two bridges within one.
>>>
>>> Thank you,but could you give me an example about gre
>>> my configuration
>>> Bridge "br0"
>>> Port "br0"
>>> Interface "br0"
>>> type: internal
>>> Port "tap1"
>>> Interface "tap1"
>>> Port "eth0"
>>> Interface "eth0"
>>> Port "gre0"
>>> Interface "gre0"
>>> type: gre
>>> options: {remote_ip="192.168.0.156"}
>>> ovs_version: "1.7.1"
>>> do you mean drop the packets from eth0 to gre0?
>>
>>It's not really clear what your goal is here in trying to use only a
>>single bridge, so it's hard to say how to achieve that.
>
>
>
More information about the discuss
mailing list