Hi 
many thanks to murphy and kk. the problem solved.
git clone git://noxrepo.org/nox
>> cd nox
>> git checkout openflow-1.0
>> ./boot.sh
>> mkdir build
>> ../configure --with-python=yes --enable-ndebug
>> make

Regards
________________________________________
From: James "Murphy" McCauley [jam...@nau.edu]
Sent: 13 July 2010 18:45
To: kk yap
Cc: Kiani, Parham; nox-dev@noxrepo.org
Subject: Re: [nox-dev] problem with NOX

I don't _think_ the checkout was the problem.

Aren't those commands equivalent (at least with current versions of git)?

-- Murphy

On Jul 13, 2010, at 9:03 AM, kk yap wrote:

> Hi Kiani,
>
> There is a typo or a mistake in the command.
>
> git checkout openflow-1.0
>
> should be
>
> git checkout -b openflow-1.0 orgin/openflow-1.0
>
> Regards
> KK
>
> On 13 July 2010 08:55, Kiani, Parham <pki...@essex.ac.uk> wrote:
>> Hi Murphy
>> thanks for your help. I have triyed to install it again, unfortunately, when 
>> i run "make" it seems it never stop or compile, it repeats some commands, so 
>> it force me to stoped by hand. i was wondering if you could take a look at 
>> it.( attached file)
>> git clone git://noxrepo.org/nox
>> cd nox
>> git checkout openflow-1.0
>> ./boot.sh
>> mkdir build
>> ../configure --with-python=yes --enable-ndebug
>> make
>>
>>
>> ________________________________________
>> From: James "Murphy" McCauley [jam...@nau.edu]
>> Sent: 13 July 2010 14:52
>> To: Kiani, Parham
>> Cc: nox-dev@noxrepo.org
>> Subject: Re: [nox-dev] problem with connect Nox to switch
>>
>> Looks like a simple version mismatch.  The version of Open vSwitch
>> you're using supports OpenFlow 1.0 (wire protocol 0x01).  The version of
>> NOX you're using supports OpenFlow 0.8.9 (wire protocol 0x97).
>>
>> So somehow you need to get your versions matched up.  I have no idea how
>> FlowVisor factors in, since I don't know which versions of OpenFlow it
>> supports, but if you want to build a version of NOX that supports
>> OpenFlow 1.0, you should use the openflow-1.0 branch:
>> git clone git://noxrepo.org/nox
>> cd nox
>> git checkout openflow-1.0
>>
>> -- Murphy
>>
>> On Tue, 2010-07-13 at 14:05 +0100, Kiani, Parham wrote:
>>> Hi all
>>> I have a controller with nox and flowvisor and a computer with 5ports 
>>> (openvswitch) as a first switch. i used to connect my switch to controller 
>>> easily( ovs-openflowd dp0 tcp: 192.168.1.2). I have tried with help of 
>>> vmware create another slice and install openvswitch as second switch. the 
>>> problem accure when I wanted to connnect two switches to controller. but 
>>> now, I can not even connect the first switch to controller.  I have 
>>> planning to create three switch in this computer ( 5ports), do i need three 
>>> nox and flowvisor? thaks in advance .
>>>
>>>
>>> :/nox/build/src$ sudo ./nox_core -i ptcp:6633 switch packetdump
>>> NOX 0.8.0~full~beta (nox_core), compiled Jun 10 2010 19:46:40
>>> Compiled with OpenFlow 0x97 (exp)
>>> 00001|openflow|WARN:stream: version negotiation failed: we support versions 
>>> 0x97 to 0x97 inclusive but peer supports no later than version
>>>
>>>
>>>
>>> sudo ovs-openflowd dp0 tcp:192.168.1.2
>>> Jul 13 13:34:20|00001|openflowd|INFO|Open vSwitch version 1.0.1
>>> Jul 13 13:34:20|00002|openflowd|INFO|OpenFlow protocol version 0x01
>>> Jul 13 13:34:20|00003|ofproto|INFO|using datapath ID 00000023208adfd2
>>> Jul 13 13:34:20|00004|rconn|INFO|dp0<->tcp:192.168.1.2: connecting...
>>> Jul 13 13:34:20|00005|rconn|INFO|dp0<->tcp:192.168.1.2: connected
>>> Jul 13 13:34:20|00006|rconn|INFO|dp0<->tcp:192.168.1.2: connection closed 
>>> by peer
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>> _______________________________________________
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>> _______________________________________________
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>>
_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to