Re: [ovs-discuss] Shiyu (Sean) Luo wants to stay in touch on LinkedIn

[陈文龙]

lol, send invation to a maillist.

2011/1/10 Shiyu (Sean) Luo 

>  LinkedIn
>
> I'd like to add you to my professional network on LinkedIn.
>
> - Shiyu (Sean) Luo
> Shiyu (Sean) Luo
> Graduate Student @ UW-Madison
> Madison, Wisconsin Area
>
> Confirm that you know Shiyu 
> (Sean)
>
> © 2010, LinkedIn Corporation
>
> ___
> discuss mailing list
> discuss@openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Question about ovsdb-server options

[陈文龙]

Thanks

2010/12/14 Justin Pettit 

> You can run ovs-vsctl in a mode that allows that to work.  Take a look at
> the end of the ovs-controller man page for an example.
>
> --Justin
>
>
> On Dec 13, 2010, at 7:28 PM, 陈文龙 wrote:
>
> > Could you provide an example? Thanks :-)
> >
> > 2010/12/14 Justin Pettit 
> > On Dec 13, 2010, at 6:23 PM, 陈文龙 wrote:
> >
> > > It is easy to understand the DBS will listen for connection. For
> someone who want to query to connect.
> > > I cannot understand why the DBS needs to connect to somewhere. For
> what?
> >
> > It's useful if you want the database to be configured by some sort of
> central authority.  This is the same direction that an OpenFlow connection
> would be established.
> >
> > --Justin
> >
> >
> >
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Question about ovsdb-server options

[陈文龙]

Could you provide an example? Thanks :-)

2010/12/14 Justin Pettit 

> On Dec 13, 2010, at 6:23 PM, 陈文龙 wrote:
>
> > It is easy to understand the DBS will listen for connection. For someone
> who want to query to connect.
> > I cannot understand why the DBS needs to connect to somewhere. For what?
>
> It's useful if you want the database to be configured by some sort of
> central authority.  This is the same direction that an OpenFlow connection
> would be established.
>
> --Justin
>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] Question about ovsdb-server options

[陈文龙]

NAME
   ovsdb-server - Open vSwitch database server

SYNOPSIS
   ovsdb-server database [--remote=remote]...  [--run=command]
...
OPTIONS
   --remote=remote
  Adds remote as a connection method used by ovsdb-server.
 remote must take one of the following forms:

  pssl:port[:ip]
 Listen  on  the  given SSL port for a connection.  By
default, ovsdb-server listens for connections to any local IP address, but
specifying ip
 limits connections to those from the given ip.  The
--private-key, --certificate, and --ca-cert options are mandatory when this
form is used.

*  ptcp:port[:ip]*
* Listen on the given TCP port for a connection.  By
default, ovsdb-server listens for connections to any local IP address, but
ip may be speci‐*
* fied to listen only for connections to the given ip.*

  punix:file
 Listen on the Unix domain server socket named file for
a connection.

  ssl:ip:port
 The  specified SSL port on the host at the given ip,
which must be expressed as an IP address (not a DNS name).  The
--private-key, --certifi‐
 cate, and --ca-cert options are mandatory when this
form is used.

*  tcp:ip:port*
* Connect to the given TCP port on ip.*

  unix:file
 Connect to the Unix domain server socket named file.

  db:table,column
 Reads additional connection methods from column in all
of the rows in table within the ovsdb-server  database.   The  column  must
 have  type
 string  or  set  of  strings.   The  connection
 methods  in the column must have one of the forms described above.  As the
contents of column
 changes, ovsdb-server also adds and drops connection
methods accordingly.



It is easy to understand the DBS will listen for connection. For someone who
want to query to connect.
I cannot understand why the DBS needs to connect to somewhere. For what?
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] What is the mechanism of GRE tunnel implement by OVS?

[陈文龙]

For example,
(Host ip: 1.1.1.1) OVS1 gre remote_ip:2.2.2.2
(Host ip: 2.2.2.2) OVS2 gre remote_ip:1.1.1.1
If OVS1 wants to send a packet to OVS2 through gre tunnel, does it send the
packet to 2.2.2.2:?
And when OVS2 receives a packet from 2.2.2.2:, that means it
is a packet go through the tunnel.
Is that right? And what is the certain port?
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openvswitch

[陈文龙]

Suggest that host1 has IP 1.1.1.1 and host2 has IP 2.2.2.2 .
In host1:
1. create interface gre0 type gre, set remote_ip as 2.2.2.2.
2. create port gre0 include interface gre0.
3. add port gre0 to the bridge.
In host2:
1. create interface gre0 type gre, set remote_ip as 1.1.1.1.
2. create port gre0 include interface gre0.
3. add port gre0 to the bridge.

Hope it helps.

2010/9/22 Maciej Gałkiewicz 

> Hello
>
> I read your post about ethernet over GRE (
> http://openvswitch.org/pipermail/discuss_openvswitch.org/2010-August/000899.html).
> Did you manage to configure openvswitch as you desired? Do you have some
> clues how to do this?
>
> best regards
> Maciej Galkiewicz
>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] How do GRE overcome VLAN nest problem?

[陈文龙]

2010/8/19 Justin Pettit 

> On Aug 18, 2010, at 2:44 AM, 陈文龙 wrote:
>
> > Sorry, I am not clear about your idea.
> > Is it possible to do VLAN nesting ?
> > Or something have the same effect.
> >
> > For example, the Service Provider provide me a VLAN 10.
> > Can I have my own "VVLANs" 10, 20, 30 base on VLAN 10.
>
> VLAN nesting can be done with Q-in-Q and S-Channel.  This is supported in
> some switches, but not currently in Open vSwitch.
>
> --Justin
>
>
>
Thanks.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] How do GRE overcome VLAN nest problem?

[陈文龙]

2010/8/18 Justin Pettit 

> On Aug 17, 2010, at 8:54 PM, 陈文龙 wrote:
>
> > In the paper, section 3, says
> > the support for GRE is essential in overcoming
> > the limitations VLANs face in larger deployments: the
> > number of available VLANs is limited (compared to the
> > size of many virtual environments), VLANs do not nest
> > well, and, as a link layer concept, VLANs do not extend
> > beyond LANs.
> > How do the support for GRE overcome the second problem?
>
> I think that was mostly related to the first point, in that nesting VLANs
> is generally not sufficient for overcoming the limited VLAN id space.
>
> --Justin
>
>
>
Sorry, I am not clear about your idea.
Is it possible to do VLAN nesting ?
Or something have the same effect.

For example, the Service Provider provide me a VLAN 10.
Can I have my own "VVLANs" 10, 20, 30 base on VLAN 10.

Thanks.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] How do GRE overcome VLAN nest problem?

[陈文龙]

In the paper, section 3, says

> the support for GRE is essential in overcoming
> the limitations VLANs face in larger deployments: the
> number of available VLANs is limited (compared to the
> size of many virtual environments), VLANs do not nest
> well, and, as a link layer concept, VLANs do not extend
> beyond LANs.
>
How do the support for GRE overcome the second problem?

Thanks.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] ovsdbmonitor error: remote command failed (rc=127)

[陈文龙]

You are right.

Thanks!

2010/8/14 Ben Pfaff 

> On Fri, Aug 13, 2010 at 5:44 AM, 陈文龙  wrote:
> > Host1 running OVS
> > IP:10.1.132.54
> >
> > Host2 run ovsdbmonitor
> > Host name or IP : 10.1.132.54
> > SSH Password : **
> > Connect target: unix:/var/run/openvswitch/db.sock
>
> ovsdbmonitor assumes that ovsdb-client is in /usr/bin on the remote host,
> and that it can execute it over SSH.  Is all that correct?
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] ovsdbmonitor error: remote command failed (rc=127)

[陈文龙]

Host1 running OVS
IP:10.1.132.54

Host2 run ovsdbmonitor
Host name or IP : 10.1.132.54
SSH Password : **
Connect target: unix:/var/run/openvswitch/db.sock
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Ethernet over GRE tunneling?

[陈文龙]

>From the mail-list I find *DarkBls* darkbls at yahoo.com

 has similar problem.
If his physical servers is distributed far away, across routers, they are
the same problem.

* [ovs-discuss] GRE tunneling / star
topology<http://openvswitch.org/pipermail/discuss_openvswitch.org/2010-June/000801.html>
*


在 2010年8月12日 上午10:21，陈文龙 写道：

> I want to set up the network topology like:
>
> +-+ 1.1.1.1   2.2.2.2 +-+
> | Router  |- Public network   | Router  |
> +-+   +-+
> |  |
> +-+   +--+
> | Switch  |   | Switch   |
> +-+   +--+
>   | |
> +---+ +--+
> | Host1 | | Host2|
> |---| |--|
> |OVS| |OVS   |
> |VM1 VMx| |VM2 .. VMy|
> +---+ +--+
> 192.168.1.10  192.168.1.20
>
> I want to build GRE tunnel between 1.1.1.1 and 2.2.2.2,
> so that, a packet 192.168.1.10 broadcasts can be broadcast to 192.168.1.20.
> And VM1 regards VM2 as a LAN member.
>
> If the tunnel takes the dot1Q tag, that's better.
>
> How to configure OVS to implement that?
>
>
> 2010/8/12 Jesse Gross 
>
> On Wed, Aug 11, 2010 at 2:13 AM, 陈文龙  wrote:
>>
>>> What is the different with Implement GRE Protocol ?
>>> Does OVS have any advanced features than GRE?
>>> Is OVS able to take a broadcast packet and go through GRE tunnel and
>>> broadcast in another subnet?
>>
>>
>> GRE is a standardized protocol so there aren't really "advanced features"
>> per se.  However, the Open vSwitch implementation supports a large number
>> tunnels and has significantly higher performance when compared to other
>> implementations.
>>
>> GRE is just tunneling Ethernet frames between switches so a broadcast
>> packet will be broadcast by a remote switch, regardless of where it is.
>>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Ethernet over GRE tunneling?

[陈文龙]

I want to set up the network topology like:

+-+ 1.1.1.1   2.2.2.2 +-+
| Router  |- Public network   | Router  |
+-+   +-+
|  |
+-+   +--+
| Switch  |   | Switch   |
+-+   +--+
  | |
+---+ +--+
| Host1 | | Host2|
|---| |--|
|OVS| |OVS   |
|VM1 VMx| |VM2 .. VMy|
+---+ +--+
192.168.1.10  192.168.1.20

I want to build GRE tunnel between 1.1.1.1 and 2.2.2.2,
so that, a packet 192.168.1.10 broadcasts can be broadcast to 192.168.1.20.
And VM1 regards VM2 as a LAN member.

If the tunnel takes the dot1Q tag, that's better.

How to configure OVS to implement that?


2010/8/12 Jesse Gross 

> On Wed, Aug 11, 2010 at 2:13 AM, 陈文龙  wrote:
>
>> What is the different with Implement GRE Protocol ?
>> Does OVS have any advanced features than GRE?
>> Is OVS able to take a broadcast packet and go through GRE tunnel and
>> broadcast in another subnet?
>
>
> GRE is a standardized protocol so there aren't really "advanced features"
> per se.  However, the Open vSwitch implementation supports a large number
> tunnels and has significantly higher performance when compared to other
> implementations.
>
> GRE is just tunneling Ethernet frames between switches so a broadcast
> packet will be broadcast by a remote switch, regardless of where it is.
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] Ethernet over GRE tunneling?

[陈文龙]

What is the different with Implement GRE Protocol ?
Does OVS have any advanced features than GRE?
Is OVS able to take a broadcast packet and go through GRE tunnel and
broadcast in another subnet?
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

IT WORKS!

Thank you all!

在 2010年8月11日 下午12:21，陈文龙 写道：

> Thanks very much.
> keep trying
>
> 在 2010年8月11日 上午11:55，kk yap 写道：
>
>  I am not comprehending here.  Here's the commands you need:
>>
>> git clone git://noxrepo.org/nox
>> cd nox
>> git checkout -b openflow-1.0 origin/openflow-1.0
>> ./boot.sh
>> mkdir build
>> cd build
>> ../configure
>> make
>>
>> Hope this helps.
>>
>> Regards
>> KK
>>
>> 2010/8/10 陈文龙 :
>> > I have download openflow-1.0
>> > what should I do next?
>> > where should I put the openflow source, and recompile nox?
>> >
>> > 在 2010年8月11日 上午11:46，kk yap 写道：
>> >>
>> >> git checkout -b openflow-1.0 origin/openflow is needed.
>> >>
>> >> Regards
>> >> KK
>> >>
>> >> 2010/8/10 陈文龙 :
>> >> >
>> >> > I don't understand.
>> >> > I do git clone git://noxrepo.org/nox.
>> >> > And then compile it.
>> >> >
>> >> > What else should I do?
>> >> > Compile OF-1.0 individually?
>> >> >
>> >> > 在 2010年8月11日 上午11:39，kk yap 写道：
>> >> >>
>> >> >> Note the need to checkout the openflow-1.0 branch.  :)
>> >> >>
>> >> >> Regards
>> >> >> KK
>> >> >>
>> >> >> 2010/8/10 陈文龙 :
>> >> >> > Compiled source from git://noxrepo.org/nox.
>> >> >> > It occurs the same problem.
>> >> >> >
>> >> >> > OVS 1.0.1
>> >> >> > NOX 0.8.0
>> >> >> >
>> >> >> >> debian1:~/nox/src# ./nox_core -i ptcp:2525 packetdump
>> >> >> >> NOX 0.8.0~full~beta (nox_core), compiled Aug 11 2010 07:24:38
>> >> >> >> Compiled with OpenFlow 0x97 (exp)
>> >> >> >> 1|openflow|WARN:stream: version negotiation failed: we
>> support
>> >> >> >> versions 0x97 to 0x97 inclusive but peer supports no later than
>> >> >> >> version
>> >> >> >> 0x01
>> >> >> >> 2|nox|WARN:Error sending features request: Protocol error
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > 在 2010年8月11日 上午11:12，陈文龙 写道：
>> >> >> >>
>> >> >> >> thanks, trying the git version.
>> >> >> >>
>> >> >> >> report latter.
>> >> >> >>
>> >> >> >>
>> >> >> >> 在 2010年8月11日 上午11:06，kk yap 写道：
>> >> >> >>>
>> >> >> >>> Why not try openflow-1.0 branch of NOX0.6 at git://
>> noxrepo.org/nox?
>> >> >> >>>
>> >> >> >>> Regards
>> >> >> >>> KK
>> >> >> >>>
>> >> >> >>> On 10 August 2010 19:55, 陈文龙  wrote:
>> >> >> >>> > OVS 1.0.1
>> >> >> >>> > NOX 0.5.0
>> >> >> >>> > Is that ok?
>> >> >> >>> >
>> >> >> >>> > 2010/8/11 Ben Pfaff 
>> >> >> >>> >>
>> >> >> >>> >> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙 
>> wrote:
>> >> >> >>> >> > OVS runs in Dom0. NOX runs in DomU.
>> >> >> >>> >> >
>> >> >> >>> >> >
>> >> >> >>> >> > 1|openflow|WARN:stream: version negotiation failed: we
>> >> >> >>> >> > support
>> >> >> >>> >> > versions
>> >> >> >>> >> > 0x97 to 0x97 inclusive but peer supports no later than
>> version
>> >> >> >>> >> > 0x01
>> >> >> >>> >> > 2|nox|WARN:Error sending features request: Protocol
>> error
>> >> >> >>> >> >
>> >> >> >>> >> > OVS support OF version 0x97 but NOX do not?
>> >> >> >>> >>
>> >> >> >>> >> I think you have it backward.  Any recent OVS supports
>> OpenFlow
>> >> >> >>> >> 1.0
>> >> >> >>> >> (0x01).
>> >> >> >>> >> I think you must be using an old version of NOX that does
>> not.
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> > ___
>> >> >> >>> > discuss mailing list
>> >> >> >>> > discuss@openvswitch.org
>> >> >> >>> >
>> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

Thanks very much.
keep trying

在 2010年8月11日 上午11:55，kk yap 写道：

> I am not comprehending here.  Here's the commands you need:
>
> git clone git://noxrepo.org/nox
> cd nox
> git checkout -b openflow-1.0 origin/openflow-1.0
> ./boot.sh
> mkdir build
> cd build
> ../configure
> make
>
> Hope this helps.
>
> Regards
> KK
>
> 2010/8/10 陈文龙 :
> > I have download openflow-1.0
> > what should I do next?
> > where should I put the openflow source, and recompile nox?
> >
> > 在 2010年8月11日 上午11:46，kk yap 写道：
> >>
> >> git checkout -b openflow-1.0 origin/openflow is needed.
> >>
> >> Regards
> >> KK
> >>
> >> 2010/8/10 陈文龙 :
> >> >
> >> > I don't understand.
> >> > I do git clone git://noxrepo.org/nox.
> >> > And then compile it.
> >> >
> >> > What else should I do?
> >> > Compile OF-1.0 individually?
> >> >
> >> > 在 2010年8月11日 上午11:39，kk yap 写道：
> >> >>
> >> >> Note the need to checkout the openflow-1.0 branch.  :)
> >> >>
> >> >> Regards
> >> >> KK
> >> >>
> >> >> 2010/8/10 陈文龙 :
> >> >> > Compiled source from git://noxrepo.org/nox.
> >> >> > It occurs the same problem.
> >> >> >
> >> >> > OVS 1.0.1
> >> >> > NOX 0.8.0
> >> >> >
> >> >> >> debian1:~/nox/src# ./nox_core -i ptcp:2525 packetdump
> >> >> >> NOX 0.8.0~full~beta (nox_core), compiled Aug 11 2010 07:24:38
> >> >> >> Compiled with OpenFlow 0x97 (exp)
> >> >> >> 1|openflow|WARN:stream: version negotiation failed: we support
> >> >> >> versions 0x97 to 0x97 inclusive but peer supports no later than
> >> >> >> version
> >> >> >> 0x01
> >> >> >> 2|nox|WARN:Error sending features request: Protocol error
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > 在 2010年8月11日 上午11:12，陈文龙 写道：
> >> >> >>
> >> >> >> thanks, trying the git version.
> >> >> >>
> >> >> >> report latter.
> >> >> >>
> >> >> >>
> >> >> >> 在 2010年8月11日 上午11:06，kk yap 写道：
> >> >> >>>
> >> >> >>> Why not try openflow-1.0 branch of NOX0.6 at git://
> noxrepo.org/nox?
> >> >> >>>
> >> >> >>> Regards
> >> >> >>> KK
> >> >> >>>
> >> >> >>> On 10 August 2010 19:55, 陈文龙  wrote:
> >> >> >>> > OVS 1.0.1
> >> >> >>> > NOX 0.5.0
> >> >> >>> > Is that ok?
> >> >> >>> >
> >> >> >>> > 2010/8/11 Ben Pfaff 
> >> >> >>> >>
> >> >> >>> >> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙 
> wrote:
> >> >> >>> >> > OVS runs in Dom0. NOX runs in DomU.
> >> >> >>> >> >
> >> >> >>> >> >
> >> >> >>> >> > 1|openflow|WARN:stream: version negotiation failed: we
> >> >> >>> >> > support
> >> >> >>> >> > versions
> >> >> >>> >> > 0x97 to 0x97 inclusive but peer supports no later than
> version
> >> >> >>> >> > 0x01
> >> >> >>> >> > 2|nox|WARN:Error sending features request: Protocol
> error
> >> >> >>> >> >
> >> >> >>> >> > OVS support OF version 0x97 but NOX do not?
> >> >> >>> >>
> >> >> >>> >> I think you have it backward.  Any recent OVS supports
> OpenFlow
> >> >> >>> >> 1.0
> >> >> >>> >> (0x01).
> >> >> >>> >> I think you must be using an old version of NOX that does not.
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > ___
> >> >> >>> > discuss mailing list
> >> >> >>> > discuss@openvswitch.org
> >> >> >>> >
> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
> >> >> >>> >
> >> >> >>> >
> >> >> >>
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

NOX compiled with OpenFlow 0x97
OVS says it support version 0x97, but peer(NOX) supports no latter than
version 0x01.
So, OVS doesn't get the right OF version of NOX.

What's wrong ?

在 2010年8月11日 上午11:29，陈文龙 写道：

> Compiled source from git://noxrepo.org/nox.
> It occurs the same problem.
>
> OVS 1.0.1
> NOX 0.8.0
>
> debian1:~/nox/src# ./nox_core -i ptcp:2525 packetdump
>> NOX 0.8.0~full~beta (nox_core), compiled Aug 11 2010 07:24:38
>> Compiled with OpenFlow 0x97 (exp)
>>
>> 1|openflow|WARN:stream: version negotiation failed: we support
>> versions 0x97 to 0x97 inclusive but peer supports no later than version 0x01
>> 2|nox|WARN:Error sending features request: Protocol error
>>
>
>
>
>
> 在 2010年8月11日 上午11:12，陈文龙 写道：
>
> thanks, trying the git version.
>>
>> report latter.
>>
>>
>> 在 2010年8月11日 上午11:06，kk yap 写道：
>>
>> Why not try openflow-1.0 branch of NOX0.6 at git://noxrepo.org/nox?
>>>
>>> Regards
>>> KK
>>>
>>> On 10 August 2010 19:55, 陈文龙  wrote:
>>> > OVS 1.0.1
>>> > NOX 0.5.0
>>> > Is that ok?
>>> >
>>> > 2010/8/11 Ben Pfaff 
>>> >>
>>> >> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙  wrote:
>>> >> > OVS runs in Dom0. NOX runs in DomU.
>>> >> >
>>> >> >
>>> >> > 1|openflow|WARN:stream: version negotiation failed: we support
>>> >> > versions
>>> >> > 0x97 to 0x97 inclusive but peer supports no later than version 0x01
>>> >> > 2|nox|WARN:Error sending features request: Protocol error
>>> >> >
>>> >> > OVS support OF version 0x97 but NOX do not?
>>> >>
>>> >> I think you have it backward.  Any recent OVS supports OpenFlow 1.0
>>> >> (0x01).
>>> >> I think you must be using an old version of NOX that does not.
>>> >
>>> >
>>> > ___
>>> > discuss mailing list
>>> > discuss@openvswitch.org
>>> > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>>> >
>>> >
>>>
>>
>>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

Compiled source from git://noxrepo.org/nox.
It occurs the same problem.

OVS 1.0.1
NOX 0.8.0

debian1:~/nox/src# ./nox_core -i ptcp:2525 packetdump
> NOX 0.8.0~full~beta (nox_core), compiled Aug 11 2010 07:24:38
> Compiled with OpenFlow 0x97 (exp)
> 1|openflow|WARN:stream: version negotiation failed: we support versions
> 0x97 to 0x97 inclusive but peer supports no later than version 0x01
> 2|nox|WARN:Error sending features request: Protocol error
>




在 2010年8月11日 上午11:12，陈文龙 写道：

> thanks, trying the git version.
>
> report latter.
>
>
> 在 2010年8月11日 上午11:06，kk yap 写道：
>
> Why not try openflow-1.0 branch of NOX0.6 at git://noxrepo.org/nox?
>>
>> Regards
>> KK
>>
>> On 10 August 2010 19:55, 陈文龙  wrote:
>> > OVS 1.0.1
>> > NOX 0.5.0
>> > Is that ok?
>> >
>> > 2010/8/11 Ben Pfaff 
>> >>
>> >> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙  wrote:
>> >> > OVS runs in Dom0. NOX runs in DomU.
>> >> >
>> >> >
>> >> > 1|openflow|WARN:stream: version negotiation failed: we support
>> >> > versions
>> >> > 0x97 to 0x97 inclusive but peer supports no later than version 0x01
>> >> > 2|nox|WARN:Error sending features request: Protocol error
>> >> >
>> >> > OVS support OF version 0x97 but NOX do not?
>> >>
>> >> I think you have it backward.  Any recent OVS supports OpenFlow 1.0
>> >> (0x01).
>> >> I think you must be using an old version of NOX that does not.
>> >
>> >
>> > ___
>> > discuss mailing list
>> > discuss@openvswitch.org
>> > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>> >
>> >
>>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

thanks, trying the git version.

report latter.


在 2010年8月11日 上午11:06，kk yap 写道：

> Why not try openflow-1.0 branch of NOX0.6 at git://noxrepo.org/nox?
>
> Regards
> KK
>
> On 10 August 2010 19:55, 陈文龙  wrote:
> > OVS 1.0.1
> > NOX 0.5.0
> > Is that ok?
> >
> > 2010/8/11 Ben Pfaff 
> >>
> >> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙  wrote:
> >> > OVS runs in Dom0. NOX runs in DomU.
> >> >
> >> >
> >> > 1|openflow|WARN:stream: version negotiation failed: we support
> >> > versions
> >> > 0x97 to 0x97 inclusive but peer supports no later than version 0x01
> >> > 2|nox|WARN:Error sending features request: Protocol error
> >> >
> >> > OVS support OF version 0x97 but NOX do not?
> >>
> >> I think you have it backward.  Any recent OVS supports OpenFlow 1.0
> >> (0x01).
> >> I think you must be using an old version of NOX that does not.
> >
> >
> > ___
> > discuss mailing list
> > discuss@openvswitch.org
> > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
> >
> >
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] openflow version incompatible with nox?

[陈文龙]

OVS 1.0.1
NOX 0.5.0
Is that ok?

2010/8/11 Ben Pfaff 

> On Tue, Aug 10, 2010 at 6:59 PM, 陈文龙  wrote:
> > OVS runs in Dom0. NOX runs in DomU.
> >
> >
> > 1|openflow|WARN:stream: version negotiation failed: we support
> versions
> > 0x97 to 0x97 inclusive but peer supports no later than version 0x01
> > 2|nox|WARN:Error sending features request: Protocol error
> >
> > OVS support OF version 0x97 but NOX do not?
>
> I think you have it backward.  Any recent OVS supports OpenFlow 1.0 (0x01).
> I think you must be using an old version of NOX that does not.
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] openflow version incompatible with nox?

[陈文龙]

OVS runs in Dom0. NOX runs in DomU.


1|openflow|WARN:stream: version negotiation failed: we support versions
0x97 to 0x97 inclusive but peer supports no later than version 0x01
2|nox|WARN:Error sending features request: Protocol error

OVS support OF version 0x97 but NOX do not?

Here is how I set up:
Dom0 runs OVS, create bridge xenbr0.
DomU runs NOX, listen on port 2525.
Dom0 ping DomU ok.
DomU ping Dom0 ok.
Dom0: ovs-vsctl set-controller xenbr0 tcp:[DomU's IP]:2525
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] questions about open flow setup

[陈文龙]

thanks

2010/8/10 Ben Pfaff 

> On Tue, Aug 10, 2010 at 2:25 AM, 陈文龙  wrote:
> > How to set the bridge's controller?
>
> "ovs-vsctl set-controller".  Please read the manpage for details.
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] questions about open flow setup

[陈文龙]

How to set the bridge's controller?
I tried
#ovs-vsctl set bridge xenbr0 controller=10.1.132.112
ovs-vsctl: "10.1.132.112" is not a valid UUID

P.S.
VM1 running NOX has ip 10.1.132.112
Host running OVS, has xenbr0 with ip 10.1.132.54
vif1 for VM1 is added to xenbr0.

*Ben Pfaff* blp at nicira.com

*Mon Jul 12 13:58:08 EDT 2010*

   - Previous message: [ovs-discuss] questions about open flow setup
   

   - Next message: [ovs-discuss] questions about open flow setup
   

   - *Messages sorted by:* [ date
]
[
   thread 
]
[
   subject 
]
[
   author 
]

--

It looks like you only have a single physical machine.  In that case,
the OVS setup is simple.  Create a bridge, e.g. br0.  Add a VIF for each
VM, including the NOX controller VM, to that bridge.  If you want the

VMs to have access to a physical network, then add e.g. eth0 to the
bridge also.  (If Dom0 has an IP address on eth0 then you'll need to
move it to br0 instead.)  *Set the bridge's controller to point to the

NOX VM's IP address.*
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] Do I have to configure switches as VLAN trunks to set up VLANs for VMs?

[陈文龙]

To set up VLANs for VMs, I may take use of many physicals, connect them
together.
Configure them as VLAN trunks will result in a big broadcast domain, which
may
reduce the performance of network.
Is there any way to avoid it?

Another question is if I want to set up VLANs across router, what should I
do?
If it is possible, how to extend VLANs in WAN/Internet ?

Thanks in advance.


   +-+
   | router  |
   +-+
 /  \
/\
+--+  +-+
|  switch  |  | switch  |
+--+  +-+
  |  |  |  |
 VLAN10  VLAN20VLAN10  VLAN20
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] How to perform cenralized management?

[陈文龙]

Centralized management is mentioned in the paper.
I am not clear about how to do that.
Which CLI(command line interface) can do that ?

Would you show me an example?

Thanks!

 Extending Networking into the Virtualization
Layer

> *Centralized management.* The interfaces for configuration

 management and asynchronous notification can

be used to create a single logical switch image across

multiple Open vSwitches running on separate physical

servers (similar to [7, 20]). In essence, a global management

process synthesizes a logical view of the switches

and their configuration declarations and lets admins

operate on that view instead of individual switches.

Therefore, as VMs join, leave, and migrate, it is the

responsibility of this management process to ensure any

configuration state remains coupled to the logical entities

for which it was declared.

We have used this interface to build a full CLI for

configuring the network as a whole. The CLI presents

the abstraction of a virtual port to which network configuration

state can be applied (e.g., VLANs, RSPAN, QoS

policies, or ACLs). Each virtual port then corresponds

to a unique VM and follows the VM throughout the

network. As a result, it is possible to query and configure

a collection of virtual switches as if they were a single

switch.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] Cannot find ovsdbmonitor

[陈文龙]

Where is the ovsdbmonitor? I cannot find it in /usr/local/bin.



>
> * ovsdbmonitor, a GUI tool for remotely viewing OVS databases and


>   OpenFlow flow tables.

http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=README;hb=HEAD
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Question about Remote Control of OVS-daemon

[陈文龙]

Firstly, run ovs daemon on host3.
Then, host1 and host2 run ovs connect to host3.
What you do on host3 would be done on host1 and host2.

For example,
IP of host1, host2, host3 is ip1, ip2, ip3.
ovs listen on port

On host3:
ovsdb-server /path/to/db --remote=tcp:port
ovs-vsctl --db=tcp:ip3:port init
ovs-vswitchd tcp:ip3:port

On host2, host3:
ovs-vsctl --db=tcp:ip3:port init
ovs-vswitchd tcp:ip3:port

>From now on, do everything on host3.
e.g.
host3# ovs-vsctl --db=tcp:ip3:port add-br br0
That would create bridge br0 on each host.


在 2010年7月31日 下午10:58，Nikos 写道：

>  Yeah but in that way I would have to enter manually the ips of the host.
>
> I was looking for something that would give a command to all the hosts that
> host3  is attached.
>
> Like if I had a deployment of 100 PC adding 100 ips for one command
> wouldn’t be effective
>
>
>
> Thanks again!
>
>
>
> *From:* 陈文龙 [mailto:qzche...@gmail.com]
> *Sent:* Friday, July 30, 2010 3:15 AM
> *To:* Nikos Bregiannis
> *Cc:*
> *Subject:* Re: [ovs-discuss] Question about Remote Control of OVS-daemon
>
>
>
> I think you should start OvS listening on tcp but not unix socket on host0
> and host1.
> And use command on host3 like
> ovsctl --db=tcp:: 
>
> 2010/7/30 Nikos Bregiannis 
>
> Hi,
>
> I'm having two pc's running ovs-daemon and some virtual machines on them. I
> haven't created any VLANs yet but i would like to ask if i could remotely
> (let's say the hosts 0 lays in usa host 1 in europe and host3 is in Canada)
> control both of them using the same properties and changes without having to
> change in every single machine over internet. Is what I am asking related to
> *VMware’s vNetwork distributed vswitch or Cisco’s Nexus 1000V* you mention
> in the site? Can this be achieved with an open source program.
>
> Thanks in advance
>
> +-+ +--+
> | vm0vm1  | |  vm2vm3  |
> |  |  |   | |   |  |   |
> |  ovs-daemon | |  ovs-daemon  |
> | | |  |
> | host0   | |host1 |
> +-+ +--+
>\   /
> \ /
>  \   /
>   \ /
>\   /
>   +-+
>   | |
>   |   host3 |
>   | |
>   +-+
>
> Nikos Bregiannis
>
> ___
> discuss mailing list
> discuss@openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Open vSwitch installation in userspace.

[陈文龙]

Have you loaded the openvswitch_mod module?

2010/7/30 Hardeep Uppal 

> Hi,
>
> I am new to Open vSwitch and had a few question about open vswitch setup in
> userspace in dom0 (2.6.26-2-xen-686). I followed steps 1 to 5 from
> INSTALL.Linux to compile and install open vswitch.
>
> % ./configure
> % make
> % su
> % make install
>
> I then initialize the configuration database using ovsdb-tools as
> instructed on step 7.
>  % ovsdb-tool create /usr/local/etc/ovs-vswitchd.conf.db
> vswitchd/vswitch.ovsschema
>
> I made sure that directory /sys/class/misc/tun and /dev/net/tun exist. All
> this looked like it worked fine until I tried to initialize the database and
> started open vswitch daemon. I got the following error when I tried to setup
> a bridge using the command "ovs-vsctl add-br br0".
>
> r...@ettm:/home/ettm/Desktop/openvswitch-1.0.1# ovsdb-tool create
> /usr/local/etc/ovs-vswitchd.conf.db vswitchd/vswitch.ovsschema
> r...@ettm:/home/ettm/Desktop/openvswitch-1.0.1#  ovsdb-server
> /usr/local/etc/ovs-vswitchd.conf.db
> --remote=punix:/usr/local/var/run/openvswitch/db.sock
> Jul 29 12:42:33|1|reconnect|INFO|unix:/tmp/stream-unix.8222.0:
> connecting...
> Jul 29 12:42:33|2|reconnect|INFO|unix:/tmp/stream-unix.8222.0:
> connected
> Jul 29 12:42:39|3|jsonrpc|INFO|unix:/tmp/stream-unix.8222.0: connection
> closed
> Jul 29 12:42:39|4|reconnect|INFO|unix:/tmp/stream-unix.8222.0:
> connection dropped
> Jul 29 12:43:21|5|reconnect|INFO|unix:/tmp/stream-unix.8251.0:
> connecting...
> Jul 29 12:43:21|6|reconnect|INFO|unix:/tmp/stream-unix.8251.0:
> connected
> Jul 29 12:55:12|7|reconnect|INFO|unix:/tmp/stream-unix.10566.0:
> connecting...
> Jul 29 12:55:12|8|reconnect|INFO|unix:/tmp/stream-unix.10566.0:
> connected
> Jul 29 12:55:12|9|jsonrpc|INFO|unix:/tmp/stream-unix.10566.0:
> connection closed
> Jul 29 12:55:12|00010|reconnect|INFO|unix:/tmp/stream-unix.10566.0:
> connection dropped
>
> r...@ettm:/home/ettm/Desktop/openvswitch-1.0.1# ovs-vsctl init
> Alarm clock
> r...@ettm:/home/ettm/Desktop/openvswitch-1.0.1# ovs-vswitchd
> unix:/usr/local/var/run/openvswitch/db.sock
> Jul 29
> 12:43:21|1|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connecting...
> Jul 29
> 12:43:21|2|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
> connected
> Jul 29 12:43:21|3|dpif_linux|ERR|/proc/devices: openvswitch major not
> found (is the module loaded?)
> Jul 29 12:43:21|4|dpif|WARN|failed to enumerate system datapaths: No
> such device
> Jul 29 12:55:12|5|dpif_linux|ERR|/proc/devices: openvswitch major not
> found (is the module loaded?)
> Jul 29 12:55:12|6|dpif|WARN|failed to create datapath br0: No such
> device
>
>
> I am not sure what the error corresponds to. I would appreciate any help.
>
> Thanks,
>
> Hardeep
>
>
>
> ___
> discuss mailing list
> discuss@openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] Question about Remote Control of OVS-daemon

[陈文龙]

I think you should start OvS listening on tcp but not unix socket on host0
and host1.
And use command on host3 like
ovsctl --db=tcp:: 

2010/7/30 Nikos Bregiannis 

> Hi,
>
> I'm having two pc's running ovs-daemon and some virtual machines on them. I
> haven't created any VLANs yet but i would like to ask if i could remotely
> (let's say the hosts 0 lays in usa host 1 in europe and host3 is in Canada)
> control both of them using the same properties and changes without having to
> change in every single machine over internet. Is what I am asking related to
> *VMware’s vNetwork distributed vswitch or Cisco’s Nexus 1000V* you mention
> in the site? Can this be achieved with an open source program.
>
> Thanks in advance
>
> +-+ +--+
> | vm0vm1  | |  vm2vm3  |
> |  |  |   | |   |  |   |
> |  ovs-daemon | |  ovs-daemon  |
> | | |  |
> | host0   | |host1 |
> +-+ +--+
>\   /
> \ /
>  \   /
>   \ /
>\   /
>   +-+
>   | |
>   |   host3 |
>   | |
>   +-+
>
> Nikos Bregiannis
>
> ___
> discuss mailing list
> discuss@openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
>
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

Re: [ovs-discuss] How to see if the physical host is seeing VLAN tagged packets correctly leaving/arriving on the eth0 interface?

[陈文龙]

Thanks!

2010/7/30 Ben Pfaff 

> On Wed, Jul 28, 2010 at 10:24 PM, 陈文龙  wrote:
> > The physical host is running OvS.
> > ovs-vsctl add-br br0
> > ovs-vsctl add-port br0 tap1.0 tag=100
> > How to see if the packet from/to tap1.0 is tagged right?
>
> You could use tcpdump on a trunk port, e.g.:
>tcpdump -pne -i eth0 vlan 100
> presuming that eth0 is a trunk port also on br0.
>
> (Be sure to include the "vlan 100" keywords on the tcpdump command line.
> tcpdump is not very good about dealing with vlans and needs a bit of
> help.)
>
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] How to see if the physical host is seeing VLAN tagged packets correctly leaving/arriving on the eth0 interface?

[陈文龙]

The physical host is running OvS.
ovs-vsctl add-br br0
ovs-vsctl add-port br0 tap1.0 tag=100

How to see if the packet from/to tap1.0 is tagged right?
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org

[ovs-discuss] Is open vswitch a distributed virtual switch?

[陈文龙]

For example
Two hosts, host0, host1.
Four VMs, vm0, vm1, vm2, vm3.
vm0,vm1 run on host0.
vm2,vm3 run on host1.

I want to create two VLANs, vlan0, vlan1.
vm0,vm2 in vlan0.
vm1,vm3 in vlan1.

Is that possible?


+-+ +--+
| vm0vm1  | |  vm2vm3  |
|  |  |   | |   |  |   |
|vlan0  vlan1 | | vlan0  vlan1 |
| | |  |
| host0   | |host1 |
+-+ +--+

vm0 & vm2 think they are in a LAN.
If vm0 broadcast a packet, vm2 will receive, vm1 will not.

How to construct a network topology like that using open vswitch?
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org