Re: [nox-dev] [Nox-dev] How to develop a new routing component in NOX?

[Kyriakos Zarifis]

Hi Giang,

are you interested in building a component in python, or C++?

Did you take a look at this page? (It has basic guidelines for both)
http://noxrepo.org/noxwiki/index.php/Developing_in_NOX
I would suggest looking at that, and then looking at the code of a simple
example component (like, pyswitch, for python components)

On Tue, Mar 6, 2012 at 10:13 AM, Giang Nguyen  wrote:

> Hi all.
> I'm new membie in NOX. I have a project with Mininet , NOX and OF switch.I
> want to develop a new routing algorithm in NOX. But I can't know where to
> start. Could you help me how to start to develop new routing component in
> NOX, everybody? which information does relate to this component? from which
> component or directory i must import to this component?
>
> Hope all of you help me.
>
> Thank in advance!
>
> --
> Giang Nguyen
> Electronic and Telecommunication Class-K52
> Center for Training of Excellent Students
> Ha Noi University of Science and  Technology
> Ha Noi, Viet Nam
> YM:giangnguyen_bk
> Mobile:(+84) 016646..4
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox-gui flowtracer problem

[Kyriakos Zarifis]

Resolved - patch will be pushed to destiny. Thanks wunyuan for pointing it
out!

On Wed, Feb 8, 2012 at 6:22 PM, wunyuan  wrote:

>  Dear Kyriakos Zarifis,
>
> In flow path, I keep client a and client b pinging each other. Then, I try
> that, but it still has not changed. I attach two picture to show it. The
> flowtrace1 is a graph after clicking trace button. The flowtrace2 is a
> graph after zooming in on the topology.
>
> 於 2012/2/8 下午 05:03, Kyriakos Zarifis 提到:
>
> I haven't used the flowtracer tool in a long time, but just a first guess
> (assuming that there is actually a flow setup on a path for the entry you
> are tracing): I've noticed that in some system the graphics don't refresh
> sometimes until you force them to refresh by, e.g. zooming in/out on the
> topology.
> Can you try that (just roll your mousewheel) and if anything changes?
>
>  If that doesn't work, we can take the discussion offline and I can try
> to replicate your error on my machine.
>
>  On Wed, Feb 8, 2012 at 12:36 AM, wunyuan wrote:
>
>> Dear all,
>>
>>
>> I build a testbed as follows:
>>
>>   NOX
>>   /  \
>>of1of2
>> /\
>>ab
>>  I had fixed "ValueError: invalid literal for int() with base 16:
>> '0xe4115b1251b4L' " with 64 bit version ubuntu. First, I start NOX and
>> configure a and b to ping each other. Also, I run the nox-gui.py. Now, I
>> select one flow entry from the nox-gui panel on the left and click the
>> "Trace !" button but I can not see anything on the topology panel. What
>> should I configure If i want to see flow on the topology panel? Thanks.
>>
>> Best regards,
>> Wun-Yuan
>>
>>
>> 於 2012/1/5 下午 03:07, wunyuan 提到:
>>
>>  Dear all，
>>>
>>> I build a testbed as follows:
>>>
>>>   NOX
>>>   /  \
>>>of1of2
>>> /\
>>>ab
>>> Firstly, I set a and b to ping each other. Secondly, I input "./nox_core
>>> -v -v -i ptcp:9550 routing lavi monitoring trackhost_pktin" to run the NOX.
>>> and then start nox-gui. Thirdly, I click "FlowTracer" botton and then
>>> double click of1 node on nox-gui to show its flow entries. Finally, I
>>> highlight one entry and click "Trace!" botton. However,I cannot find any
>>> flows on nox-gui and I find one error message. this error message is as
>>> follows:
>>>
>>> File "~/nox/src/gui/views/flowtracer.py", line 95, in trace_flow
>>>value = int(value,16)
>>> ValueError: invalid literal for int() with base 16: '0xe4115b1251b4L'
>>>
>>> How could I fix it?
>>>
>>>
>>
>> --
>>
>> ===
>>  網路與資安組－黃文源(Wun-Yuan Huang)
>>
>> 財團法人國家實驗研究院
>> 國家高速網路與計算中心南部事業群
>> National Center for High-Performance Computing South Region Office
>> 台南縣台南科學園區南科三路28號
>> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744,
>> Taiwan, R.O.C.
>> TEL：06-5050940 ext.751
>> FAX：06-5050945
>> E-Mail：wuny...@nchc.narl.org.tw
>> ===
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>
>
>
> --
>
> ===
> 網路與資安組－黃文源(Wun-Yuan Huang)
> 財團法人國家實驗研究院
> 國家高速網路與計算中心南部事業群
> National Center for High-Performance Computing South Region Office
> 台南縣台南科學園區南科三路28號
> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan, 
> R.O.C.
> TEL：06-5050940 ext.751
> FAX：06-5050945
> E-Mail：wuny...@nchc.narl.org.tw
> ===
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] DATABASE Network view (NOX)

[Kyriakos Zarifis]

On Tue, Feb 28, 2012 at 8:17 AM, marwen mechtri wrote:

> Hello,
>
> I would like to know if NOX use a database to store the network view.
> and where is it located. is it sqlite, or mysql database.
>

the network view isn't stored in a database - rather, there are a few
components that are responsible for creating the network view, and making
it available to other components.
This is done specifically by these components:
Discovery
, Topology ,
Authenticator
 .
If you want to programmatically interact with the network view, you would
use the API provided by these components.

otherwise how can I interface with NOX in order to look at the network view
>

If you want to just look at the network (and get some real time
information, but not manage it programatically) you can use the
GUI (currently
only in the branch "destiny")


> Thanks in advance,
> Best Regards,
> Marouen
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] NOX error

[Kyriakos Zarifis]

Is there a meta.json in the build tree?
"nox/build/src/nox/coreapps/examples/" ?
(not in "nox/src/nox/coreapps/examples/")

if it is there, maybe its contents have changed and are in wrong format -
feel free to paste it

On Sat, Feb 18, 2012 at 7:47 AM, Baraki Halefom  wrote:

> anyone familiar with the following error.
>
> 2|pyrt|ERR:Can't load and parse 'nox/coreapps/examples/meta.json
>
>  the meta.json file has all the required dependency lists
>
>
>
>
> --
>
>
> Baraki H. Abay
> Department of Math and Computer science
> North Carolina Central University
> Durham, 27707 NC
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] monitoring module not available in my nox repository

[Kyriakos Zarifis]

That's right, 'monitoring' is only in destiny.

"git checkout -b destiny origin/destiny"
to create a new local destiny branch and switch to it   (from
here
)

On Thu, Feb 16, 2012 at 9:22 AM, Aaron Rosen  wrote:

> I know it's definitely in destiny if you switch branches to that.
>
> Aaron
>
> On Thu, Feb 16, 2012 at 12:02 PM, Baraki Halefom 
> wrote:
> > hello every one,
> >
> > I am trying to gather the flow statistics info from switches in my
> network
> > through my Component.
> > I tried to import the 'monitoring' module to use it send flow statistics
> > request as follows.
> >
> >  from nox.netapps.monitoring.monitoring import Monitoring
> > and got the following error
> > ImportError: No module named monitoring.monitoring
> >
> > isn't the monitoring module available in the zaku version? what else
> could
> > it be? similarly it gives me similar error when i import the pyopenflow
> > (import nox.lib.pyopenflow as of) model. when i check the directory list
> > both modules are not available.
> >
> >
> > Moreover,
> >
> > inst.register_for_flow_stats_in(my_flow_in_handler)
> > gives me the following error
> > Attribute erro: myswitch instance has no attribute
> > 'register_for_flow_stats_in' where 'myswitch' is my custom component
> >
> > thanks in advance
> >
> > --
> >
> >
> > Baraki H. Abay
> > Department of Math and Computer science
> > North Carolina Central University
> > Durham, 27707 NC
> >
> >
> > ___
> > nox-dev mailing list
> > nox-dev@noxrepo.org
> > http://noxrepo.org/mailman/listinfo/nox-dev
> >
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] g++ internal when compiling

[Kyriakos Zarifis]

Murphy pointed out that this could be because of the "-j 5" flag. This flag
"make" to run 5 jobs at a time.
Indeed, from the wiki:
"The *../configure* step checks for required dependencies. 'make -j 5'
should work on a system with 1 GB of RAM; 'make -j' may work on systems
with more RAM."
I was indeed compiling in a vm with 1gb ram, and running "make" without '-j
5' worked. It looks like 'authenticator' and 'user_event_log' are the most
memory intensive components to compile. Or there's a breaking change with a
more recent version of g++. Or a combination :>
Anyway, give that a try, I'm guessing that this will work for you too.

On Wed, Feb 15, 2012 at 2:33 PM, Kyriakos Zarifis wrote:

> I couldn't look at it at the time, so I ended up simply not compiling the
> offending components.. I am planning to take a look at some point soon (but
> if you do it first feel free to share:> )
>
> On Wed, Feb 15, 2012 at 2:15 PM, Shrutarshi Basu wrote:
>
>> Did you manage to fix it? If so, do you remember what you did?
>> Thanks,
>>
>>
>> On Wed, Feb 15, 2012 at 3:00 PM, Kyriakos Zarifis 
>> wrote:
>>
>>> I actually came across this too last week when compiling destiny on
>>> Ubuntu 11.10.
>>> It also happened for "user_event_log" and I think maybe one more
>>> component.
>>>
>>> On Wed, Feb 15, 2012 at 9:58 AM, Shrutarshi Basu 
>>> wrote:
>>>
>>>> Hi guys,
>>>> I'm trying to compile the Destiny branch on Ubuntu 10.04 with GCC 4.4
>>>> but I keep getting the following error:
>>>>
>>>> g++: Internal error: Killed (program cc1plus)
>>>> Please submit a full bug report.
>>>> See  for instructions.
>>>> make[9]: *** [authenticator_la-authenticator_util.lo] Error 1
>>>> make[9]: *** Waiting for unfinished jobs
>>>> make[9]: Leaving directory
>>>> `/home/user/src/nox/build/src/nox/netapps/authenticator'
>>>> make[8]: *** [all] Error 2
>>>>
>>>> Can someone tell me what's wrong? Configure finishes fine, should I be
>>>> using a different GCC version?
>>>> Thanks,
>>>> Basu
>>>>
>>>> --
>>>> Shrutarshi Basu
>>>> Basus.me
>>>> The ByteBaker <http://bytebaker.com>
>>>>
>>>>
>>>> ___
>>>> nox-dev mailing list
>>>> nox-dev@noxrepo.org
>>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>>
>>>>
>>>
>>
>>
>> --
>> Shrutarshi Basu
>> Basus.me
>> The ByteBaker <http://bytebaker.com>
>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] g++ internal when compiling

[Kyriakos Zarifis]

I couldn't look at it at the time, so I ended up simply not compiling the
offending components.. I am planning to take a look at some point soon (but
if you do it first feel free to share:> )

On Wed, Feb 15, 2012 at 2:15 PM, Shrutarshi Basu wrote:

> Did you manage to fix it? If so, do you remember what you did?
> Thanks,
>
>
> On Wed, Feb 15, 2012 at 3:00 PM, Kyriakos Zarifis 
> wrote:
>
>> I actually came across this too last week when compiling destiny on
>> Ubuntu 11.10.
>> It also happened for "user_event_log" and I think maybe one more
>> component.
>>
>> On Wed, Feb 15, 2012 at 9:58 AM, Shrutarshi Basu wrote:
>>
>>> Hi guys,
>>> I'm trying to compile the Destiny branch on Ubuntu 10.04 with GCC 4.4
>>> but I keep getting the following error:
>>>
>>> g++: Internal error: Killed (program cc1plus)
>>> Please submit a full bug report.
>>> See  for instructions.
>>> make[9]: *** [authenticator_la-authenticator_util.lo] Error 1
>>> make[9]: *** Waiting for unfinished jobs
>>> make[9]: Leaving directory
>>> `/home/user/src/nox/build/src/nox/netapps/authenticator'
>>> make[8]: *** [all] Error 2
>>>
>>> Can someone tell me what's wrong? Configure finishes fine, should I be
>>> using a different GCC version?
>>> Thanks,
>>> Basu
>>>
>>> --
>>> Shrutarshi Basu
>>> Basus.me
>>> The ByteBaker <http://bytebaker.com>
>>>
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>
>
> --
> Shrutarshi Basu
> Basus.me
> The ByteBaker <http://bytebaker.com>
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] g++ internal when compiling

[Kyriakos Zarifis]

I actually came across this too last week when compiling destiny on Ubuntu
11.10.
It also happened for "user_event_log" and I think maybe one more component.

On Wed, Feb 15, 2012 at 9:58 AM, Shrutarshi Basu wrote:

> Hi guys,
> I'm trying to compile the Destiny branch on Ubuntu 10.04 with GCC 4.4 but
> I keep getting the following error:
>
> g++: Internal error: Killed (program cc1plus)
> Please submit a full bug report.
> See  for instructions.
> make[9]: *** [authenticator_la-authenticator_util.lo] Error 1
> make[9]: *** Waiting for unfinished jobs
> make[9]: Leaving directory
> `/home/user/src/nox/build/src/nox/netapps/authenticator'
> make[8]: *** [all] Error 2
>
> Can someone tell me what's wrong? Configure finishes fine, should I be
> using a different GCC version?
> Thanks,
> Basu
>
> --
> Shrutarshi Basu
> Basus.me
> The ByteBaker 
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Extending pytopology component

[Kyriakos Zarifis]

Hi Andrea,

that sounds good. Yes, the .i file is the right place to make the
extensions. Here's a tutorial that helped when I was looking into swig:
http://www.swig.org/tutorial.html

On Wed, Feb 15, 2012 at 3:27 AM, andrea simeoni
wrote:

> Hi guys,
>
> I need a certain amount of information by the Topology component. I'm
> working in python and the pytopology component exposes only a subset of the
> whole Topology functionalities. To this aim I was thinking to extend
> pytopology with proper functions. Since I've not SWIG experience could
> someone explain me where I have to put modifications? I was thinking to
> extend the "pytopology.i" file. Is it the correct approach?
>
> Best regards
>
> --
> Andrea Simeoni
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox-gui flowtracer problem

[Kyriakos Zarifis]

Aha, try " ./nox_core -v -v -i ptcp: monitoring flowtracer"

(btw you'll need "-v -v" to get the log messages to show on your GUI,
that's why your log panel is empty)

On Thu, Feb 9, 2012 at 4:06 PM, wunyuan  wrote:

>  ha, I don't run flowtracer component. I only run "./nox_core -i ptcp:
> switch lavitest_showflow" or "./nox_core -i ptcp: switch lavi".
>
> 於 2012/2/9 下午 09:53, Kyriakos Zarifis 提到:
>
> Ah, the first question I should have asked: Are you running the
> "flowtracer" component?
> "./nox_core blah blah flowtracer"
>
> On Wed, Feb 8, 2012 at 6:22 PM, wunyuan  wrote:
>
>>  Dear Kyriakos Zarifis,
>>
>> In flow path, I keep client a and client b pinging each other. Then, I
>> try that, but it still has not changed. I attach two picture to show it.
>> The flowtrace1 is a graph after clicking trace button. The flowtrace2 is a
>> graph after zooming in on the topology.
>>
>> 於 2012/2/8 下午 05:03, Kyriakos Zarifis 提到:
>>
>> I haven't used the flowtracer tool in a long time, but just a first guess
>> (assuming that there is actually a flow setup on a path for the entry you
>> are tracing): I've noticed that in some system the graphics don't refresh
>> sometimes until you force them to refresh by, e.g. zooming in/out on the
>> topology.
>> Can you try that (just roll your mousewheel) and if anything changes?
>>
>>  If that doesn't work, we can take the discussion offline and I can try
>> to replicate your error on my machine.
>>
>>  On Wed, Feb 8, 2012 at 12:36 AM, wunyuan wrote:
>>
>>> Dear all,
>>>
>>>
>>> I build a testbed as follows:
>>>
>>>   NOX
>>>   /  \
>>>of1of2
>>> /\
>>>ab
>>>  I had fixed "ValueError: invalid literal for int() with base 16:
>>> '0xe4115b1251b4L' " with 64 bit version ubuntu. First, I start NOX and
>>> configure a and b to ping each other. Also, I run the nox-gui.py. Now, I
>>> select one flow entry from the nox-gui panel on the left and click the
>>> "Trace !" button but I can not see anything on the topology panel. What
>>> should I configure If i want to see flow on the topology panel? Thanks.
>>>
>>> Best regards,
>>> Wun-Yuan
>>>
>>>
>>> 於 2012/1/5 下午 03:07, wunyuan 提到:
>>>
>>>  Dear all，
>>>>
>>>> I build a testbed as follows:
>>>>
>>>>   NOX
>>>>   /  \
>>>>of1of2
>>>> /\
>>>>ab
>>>> Firstly, I set a and b to ping each other. Secondly, I input
>>>> "./nox_core -v -v -i ptcp:9550 routing lavi monitoring trackhost_pktin" to
>>>> run the NOX. and then start nox-gui. Thirdly, I click "FlowTracer" botton
>>>> and then double click of1 node on nox-gui to show its flow entries.
>>>> Finally, I highlight one entry and click "Trace!" botton. However,I cannot
>>>> find any flows on nox-gui and I find one error message. this error message
>>>> is as follows:
>>>>
>>>> File "~/nox/src/gui/views/flowtracer.py", line 95, in trace_flow
>>>>value = int(value,16)
>>>> ValueError: invalid literal for int() with base 16: '0xe4115b1251b4L'
>>>>
>>>> How could I fix it?
>>>>
>>>>
>>>
>>> --
>>>
>>> ===
>>>  網路與資安組－黃文源(Wun-Yuan Huang)
>>>
>>> 財團法人國家實驗研究院
>>> 國家高速網路與計算中心南部事業群
>>> National Center for High-Performance Computing South Region Office
>>> 台南縣台南科學園區南科三路28號
>>> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744,
>>> Taiwan, R.O.C.
>>> TEL：06-5050940 ext.751
>>> FAX：06-5050945
>>> E-Mail：wuny...@nchc.narl.org.tw
>>> ===
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>
>>
>>
>> --
>>
>> ===
>> 網路與資安組－黃文源(Wun-Yuan Huang)
>> 財團法人國家實驗研究院
>> 國家高速網路與計算中心南部事業群
>> National Center for High-Performance Computing South Region Office
>> 台南縣台南科學園區南科三路28號
>> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan, 
>> R.O.C.
>> TEL：06-5050940 ext.751
>> FAX：06-5050945
>> E-Mail：wuny...@nchc.narl.org.tw
>> ===
>>
>>
>
>
> --
>
> ===
> 網路與資安組－黃文源(Wun-Yuan Huang)
> 財團法人國家實驗研究院
> 國家高速網路與計算中心南部事業群
> National Center for High-Performance Computing South Region Office
> 台南縣台南科學園區南科三路28號
> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan, 
> R.O.C.
> TEL：06-5050940 ext.751
> FAX：06-5050945
> E-Mail：wuny...@nchc.narl.org.tw
> ===
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox-gui flowtracer problem

[Kyriakos Zarifis]

Ah, the first question I should have asked: Are you running the
"flowtracer" component?
"./nox_core blah blah flowtracer"

On Wed, Feb 8, 2012 at 6:22 PM, wunyuan  wrote:

>  Dear Kyriakos Zarifis,
>
> In flow path, I keep client a and client b pinging each other. Then, I try
> that, but it still has not changed. I attach two picture to show it. The
> flowtrace1 is a graph after clicking trace button. The flowtrace2 is a
> graph after zooming in on the topology.
>
> 於 2012/2/8 下午 05:03, Kyriakos Zarifis 提到:
>
> I haven't used the flowtracer tool in a long time, but just a first guess
> (assuming that there is actually a flow setup on a path for the entry you
> are tracing): I've noticed that in some system the graphics don't refresh
> sometimes until you force them to refresh by, e.g. zooming in/out on the
> topology.
> Can you try that (just roll your mousewheel) and if anything changes?
>
>  If that doesn't work, we can take the discussion offline and I can try
> to replicate your error on my machine.
>
>  On Wed, Feb 8, 2012 at 12:36 AM, wunyuan wrote:
>
>> Dear all,
>>
>>
>> I build a testbed as follows:
>>
>>   NOX
>>   /  \
>>of1of2
>> /\
>>ab
>>  I had fixed "ValueError: invalid literal for int() with base 16:
>> '0xe4115b1251b4L' " with 64 bit version ubuntu. First, I start NOX and
>> configure a and b to ping each other. Also, I run the nox-gui.py. Now, I
>> select one flow entry from the nox-gui panel on the left and click the
>> "Trace !" button but I can not see anything on the topology panel. What
>> should I configure If i want to see flow on the topology panel? Thanks.
>>
>> Best regards,
>> Wun-Yuan
>>
>>
>> 於 2012/1/5 下午 03:07, wunyuan 提到:
>>
>>  Dear all，
>>>
>>> I build a testbed as follows:
>>>
>>>   NOX
>>>   /  \
>>>of1of2
>>> /\
>>>ab
>>> Firstly, I set a and b to ping each other. Secondly, I input "./nox_core
>>> -v -v -i ptcp:9550 routing lavi monitoring trackhost_pktin" to run the NOX.
>>> and then start nox-gui. Thirdly, I click "FlowTracer" botton and then
>>> double click of1 node on nox-gui to show its flow entries. Finally, I
>>> highlight one entry and click "Trace!" botton. However,I cannot find any
>>> flows on nox-gui and I find one error message. this error message is as
>>> follows:
>>>
>>> File "~/nox/src/gui/views/flowtracer.py", line 95, in trace_flow
>>>value = int(value,16)
>>> ValueError: invalid literal for int() with base 16: '0xe4115b1251b4L'
>>>
>>> How could I fix it?
>>>
>>>
>>
>> --
>>
>> ===
>>  網路與資安組－黃文源(Wun-Yuan Huang)
>>
>> 財團法人國家實驗研究院
>> 國家高速網路與計算中心南部事業群
>> National Center for High-Performance Computing South Region Office
>> 台南縣台南科學園區南科三路28號
>> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744,
>> Taiwan, R.O.C.
>> TEL：06-5050940 ext.751
>> FAX：06-5050945
>> E-Mail：wuny...@nchc.narl.org.tw
>> ===
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>
>
>
> --
>
> ===
> 網路與資安組－黃文源(Wun-Yuan Huang)
> 財團法人國家實驗研究院
> 國家高速網路與計算中心南部事業群
> National Center for High-Performance Computing South Region Office
> 台南縣台南科學園區南科三路28號
> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan, 
> R.O.C.
> TEL：06-5050940 ext.751
> FAX：06-5050945
> E-Mail：wuny...@nchc.narl.org.tw
> ===
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox-gui flowtracer problem

[Kyriakos Zarifis]

I haven't used the flowtracer tool in a long time, but just a first guess
(assuming that there is actually a flow setup on a path for the entry you
are tracing): I've noticed that in some system the graphics don't refresh
sometimes until you force them to refresh by, e.g. zooming in/out on the
topology.
Can you try that (just roll your mousewheel) and if anything changes?

If that doesn't work, we can take the discussion offline and I can try to
replicate your error on my machine.

On Wed, Feb 8, 2012 at 12:36 AM, wunyuan  wrote:

> Dear all,
>
>
> I build a testbed as follows:
>
>   NOX
>   /  \
>of1of2
> /\
>ab
> I had fixed "ValueError: invalid literal for int() with base 16:
> '0xe4115b1251b4L' " with 64 bit version ubuntu. First, I start NOX and
> configure a and b to ping each other. Also, I run the nox-gui.py. Now, I
> select one flow entry from the nox-gui panel on the left and click the
> "Trace !" button but I can not see anything on the topology panel. What
> should I configure If i want to see flow on the topology panel? Thanks.
>
> Best regards,
> Wun-Yuan
>
>
> 於 2012/1/5 下午 03:07, wunyuan 提到:
>
>  Dear all，
>>
>> I build a testbed as follows:
>>
>>   NOX
>>   /  \
>>of1of2
>> /\
>>ab
>> Firstly, I set a and b to ping each other. Secondly, I input "./nox_core
>> -v -v -i ptcp:9550 routing lavi monitoring trackhost_pktin" to run the NOX.
>> and then start nox-gui. Thirdly, I click "FlowTracer" botton and then
>> double click of1 node on nox-gui to show its flow entries. Finally, I
>> highlight one entry and click "Trace!" botton. However,I cannot find any
>> flows on nox-gui and I find one error message. this error message is as
>> follows:
>>
>> File "~/nox/src/gui/views/**flowtracer.py", line 95, in trace_flow
>>value = int(value,16)
>> ValueError: invalid literal for int() with base 16: '0xe4115b1251b4L'
>>
>> How could I fix it?
>>
>>
>
> --
>
> ==**==**===
> 網路與資安組－黃文源(Wun-Yuan Huang)
>
> 財團法人國家實驗研究院
> 國家高速網路與計算中心南部事業群
> National Center for High-Performance Computing South Region Office
> 台南縣台南科學園區南科三路28號
> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan,
> R.O.C.
> TEL：06-5050940 ext.751
> FAX：06-5050945
> E-Mail：wuny...@nchc.narl.org.**tw 
> ==**==**===
>
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Switch Statistics

[Kyriakos Zarifis]

the component 'monitoring' does that - I'd suggest taking a look there

On Wed, Feb 1, 2012 at 1:31 PM, Siddharth Sharma wrote:

> HI,
>
>   Can anyone please tell me how to get SWITCH STATISTICS (for ex. flow
> statistics, port statistics, etc).
>
> I am trying to send the request from NOX Controller to OpenFlow Switch to
> get the statistics, but not able to do that. If possible, can anyone please
> provide with the sample code.
>
> Thanks
> Siddharth
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Receiving JSON messages

[Kyriakos Zarifis]

That's the reason; the jsonmsg_event isn't exposed in python on zaku.
I'd really encourage you to try to migrate to destiny. Not only because
this will work, but more importantly because destiny is a far more
developed branch by now, with many fixes and added features.

If you really don't want to switch to destiny, maybe you could just grab
jsonmsg_event.i from destiny and stick it in your zaku tree. (I can't
remember if this is going to just work or you'll need to hack something,
but give it a try and see what breaks?)

On Thu, Jan 26, 2012 at 1:37 PM, Giorgio Mazza
wrote:

> **
> Yes, I'm using zaku...
> And I do not have any file called "jsonmsg_event.i".
> Any idea about how can I receive json messages and handle them in order to
> install flow entries?
> Do I have to use destiny branch?
> I don't know if it could be simple to switch from zaku to destiny, but i'd
> rather to keep zaku, as I already worked a bit on it in order to extend it
> with other classes and with the component I am try to improve.
> Is it possible to implement those functionalities going on with zaku?
>
> Giorgio
>
>
> On 26/01/2012 21:38, Kyriakos Zarifis wrote:
>
> Hi Girogio,
>
>  I forgot to ask, but, are you using the destiny branch or zaku? It looks
> like you're using zaku.
>
>  In your _source_ directory, not the build dir,  (so:
> nox/src/nox/coreapps/messenger), you should have a file called
> "jsonmsg_event.i", which creates the module you're missing. That exists
> only in destiny
>
> On Thu, Jan 26, 2012 at 5:27 AM, Giorgio Mazza  > wrote:
>
>>  Actually I get the same error, because I do not have neither
>> pyjsonmsgevent nor pymsgevent in messenger folder...
>> This is the list of what I have in messenger folder:
>>
>> giorgio@controller:~/nox/build/src$ ls -a  nox/coreapps/messenger/
>> . jsonmessenger.la
>>  messenger.la
>> ..jsonmessenger_la-jsonmessenger.lo
>> messenger_la-messenger.lo
>> cacert.pem.libs
>>   messenger.py
>> .deps Makefile
>>meta.json
>> __init__.py  messenger_core.la
>> servercert.pem
>> __init__.pycmessenger_core_la-messenger_core.lo   serverkey.pem
>>
>>
>> Do I miss anything in my folders or did I make something wrong?
>>
>> Giorgio
>>
>>
>> On 26/01/2012 13:05, Murphy McCauley wrote:
>>
>> Oops, that was my bad -- as I said, I had adapted that from another
>> message.
>> The correct import should be:
>> from nox.coreapps.messenger.pyjsonmsgevent import JSONMsg_event
>>
>>  -- Murphy
>>
>>  On Jan 26, 2012, at 3:40 AM, Giorgio Mazza wrote:
>>
>>  Thanks, I think I will specify a port.
>>
>> Another question...
>> At the moment I get an error while importing the JSON_Msg event in the
>> install() of my component.
>>
>> "in install
>> from nox.coreapps.messenger.pymsgevent import JSONMsg_event
>> ImportError: No module named pymsgevent "
>>
>> I blindly followed your instructions at first, but then I looked in my
>> messenger folder without finding where this event is defined.
>> Could you please tell me where is it, so that I can insert the correct
>> path in my install function? I'm using the standard message folder.
>> Thank you.
>> Regards,
>>
>> Giorgio
>>
>> On 25/01/2012 22:28, Murphy McCauley wrote:
>>
>> I believe it defaults to port 2703.  You should be able to set the port
>> number by specifying it on the commandline...
>> ./nox_core -i ptcp: jsonmessenger=tcpport=4096 your_app_here
>>
>>  It listens on all IP addresses; there is currently no way to specify
>> just one.
>>
>>  -- Murphy
>>
>>  On Jan 25, 2012, at 1:11 PM, Giorgio Mazza wrote:
>>
>>  A question about the socket opened when invoking jsonmessenger.
>> What are the IP address, the tcp port and the interface that this socket
>> refers to? Is there any way to set them?
>> I undersotood the mechanism, but I don't know where to send my messages
>> from the external application.
>> Thank you.
>> Regards,
>>
>> Giorgio
>>
>> On 24/01/2012 13:49, Murphy McCauley wrote:
>>
>> The minimum to get up and going should be something like this:
>>
>>  1) In your component's install function:
>> from nox.coreapps.messenger.pymsgevent import JSONMsg_event
>> JSONMsg_event.register_event_converter(self.ctxt)
>> self.register_h

Re: [nox-dev] Receiving JSON messages

[Kyriakos Zarifis]

form, to see if I understood
> correctly.
> Basically in my external application I have to set up a socket that sends
> json messages and this would be quite simple.
> In my nox component, instead, I have to import the "JSONMsg_event" and,
> within the "install()" instruction, to handle it with my specific method,
> that, in my case, would only save these json messages into a dictionary,
> for using them later, according to some conditions.
> Is that correct?
>
> A couple of things that I didn't understand:
> - I assume I also have to set up a server socket in my nox component, in
> order to receive json messages and handle  JSONMsg_events. So, I think this
> socket has to be already up and running when I handle the event. So, when
> do I have to create it and how? Do I have to use messenger.py channel class?
> - Second question, probably related to the first. I think to be pretty
> confused about jsonmessenger: what are the jsonmessenger files I could look
> into in order to understand fields and methods that I would need to use?
> Are the jsonmessenger.cc and jsonmessenger.hh in
> nox/src/nox/coreapps/messenger? And, if it is the case, how can I integrate
> them into a python component?
>
> Thanks again,
>
> Giorgio
>
> On 24/01/2012 12:28, Kyriakos Zarifis wrote:
>
> Hi Giorgio,
>
>  yes, I think using jsonmessenger would be the best approach for this.
>
>  you need to implement a send/receive interface on the external
> application and in your nox component. For the external application, it's
> pretty straightforward - Connect to the jsonmessenger socket and send json
> strings. In your nox application you need to register for JSON messages,
> and handle them appropriately.
>
>  The wiki explains the communication in a few steps (specifically for the
> GUI<->NOX, but it will be similar and simpler for any external app) 
> here<http://noxrepo.org/noxwiki/index.php/NOX_GUI#Connecting_a_subview_to_a_NOX_component>
> :
>
>  If you want to see a full example, the GUI <http://tinyurl.com/6p2yl5o> and
> the monitoring <http://tinyurl.com/6nv83a3> component in destiny could be
> a place to look. I'm afraid it's much more complex than what you need, but
> the bits you need are in there if you dig in the code a bit.
>
>
> On Tue, Jan 24, 2012 at 2:16 AM, Giorgio Mazza  > wrote:
>
>> Hi all!
>> I have written a simple component in python that works fine.
>> Now I would to improve it, making it to install flow entries depending on
>> parameters received from an external application.
>> In particular I want to pass those parameters via json messages to my
>> component, which, in my thougths, has to open a "permanent" socket
>> listening for them, save those parameters in a dictionary and, as a
>> consequence, decide the desired switch behaviour (whether install or not a
>> flow entry for the received parameters).
>> In previous threads I found that I have to use jsonmessenger (even in
>> python?) or to have a look to discovery.py, but I am not sure to have
>> understood what I have to do and where in order to realize such a behaviour.
>> Could anyone, please, help me?
>> Thank you in advance,
>>
>> Giorgio Mazza
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>
>
>  ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
>  ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
>  ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] NOX on IRC

[Kyriakos Zarifis]

Great to see some activity on IRC already :>

On Tue, Jan 17, 2012 at 6:15 PM, Kyriakos Zarifis wrote:

> The nox-dev mailing list is still the best way discuss NOX or ask for
> help, but there is now also a IRC channel where NOX users and developers
> can hangout for a more real-time type of interaction.
>
> Join us on #noxcontroller on "freenode" servers.
>
> (For instant web-based access: http://webchat.freenode.net/ )
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Problem with editing wiki

[Kyriakos Zarifis]

Thanks for reporting! Should be fixed - can you give it another try?

Also, thanks for offering help with sysadmin tasks:> lets talk offline/on
IRC about that

On Wed, Jan 18, 2012 at 10:12 AM, Maciej Gałkiewicz <
maciej.galkiew...@gmail.com> wrote:

> Hello
> I have got following error when trying to save edited wiki page:
> *Fatal error*: Allowed memory size of 20971520 bytes exhausted (tried to
> allocate 8157 bytes) in */var/www/
> noxrepo.org/noxwiki/extensions/SpamBlacklist/SpamBlacklist_body.php* on
> line *411*
>
> Do you have any tracker for such things? I am willing to help with
> sysadmin tasks.
>
> regards
> Maciej
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Account on nox wiki

[Kyriakos Zarifis]

Hi Maciej,

thanks for your contribution!
I will contact you with the details of your account.

On Wed, Jan 18, 2012 at 2:11 AM, Maciej Gałkiewicz <
maciej.galkiew...@gmail.com> wrote:

> Hello
>
> I would like to help with documentation on nox wiki. I have found some
> links which does not work anymore or do not point to appropriate
> destination. The next thing is installation manual. It does not work for
> debian wheezy and I have experienced some problems with debian squeeze too.
> I would be happy to help.
>
> regards
> Maciej
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] 'Monitoring' component status

[Kyriakos Zarifis]

Hi Joe,

That's right, monitoring periodically queries switches for statistics and
exposes that info.
The interface is probably not going to chance any time soon. It has been
used and tested to some extent, and has been proven ok for what it used so
far.
It exposes information like table_stats, port_stats, aggregate_stats
I'm not aware of scripts that demonstrate its usage, but the GUI interacts
with monitoring to display some switch statistics etc.
So if you wanted to delve into the code there you could find an example of
how to use the API. (It's probably more complicated than you need since,
'messenger' is used between the GUI and monitoring for their communication.
You probably don't care about interfacing with an external program like
that)


On Tue, Jan 17, 2012 at 5:58 PM, Joe Stringer wrote:

> Hi all,
>
> I'm currently writing an SNMP subagent to interface with NOX to fetch
> openflow statistics from NOX. To this end, I was thinking of fetching
> the statistics via JSON messages. I noticed that netapps/monitoring in
> the destiny branch caches stats about connected datapaths, and it
> looks like it could be useful for my project.
>
> What is the current status of the monitoring component in the destiny
> branch?
> - Is the interface likely to change much?
> - What information does it expose?
> - Are there any scripts like src/scripts/nox-console.py that have
> examples of how to structure messages to get certain types of replies?
>
> Cheers,
> Joe
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

[nox-dev] NOX on IRC

[Kyriakos Zarifis]

The nox-dev mailing list is still the best way discuss NOX or ask for help,
but there is now also a IRC channel where NOX users and developers can
hangout for a more real-time type of interaction.

Join us on #noxcontroller on "freenode" servers.

(For instant web-based access: http://webchat.freenode.net/ )
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] What is the main difference between “route” and “routing” in NOX

[Kyriakos Zarifis]

Here's an overview of the "routing" component
http://noxrepo.org/noxwiki/index.php/Routing

On Mon, Jan 16, 2012 at 2:41 AM, 王楠  wrote:

> Hi，
>
>   I want to do some study on the forwarding capability within NOX.
>   I notice there are two components “route” and “routing” in folder netapps
>   as if they are doing the similar job .
>   could someone explain what is the main difference between
>“route” and “routing”？
>
> Thank you.
>
> Mike
> wangnan8...@gmail.com
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Flow-mod error 8: Specified buffer does not exist.

[Kyriakos Zarifis]

Hi Sergio,

if you don't care to send out the buffered packet that triggered the
packet_in (or if, for example, you just want to install a flow proactively)
using buffer_id=-1 I think should work.

On Fri, Jan 13, 2012 at 8:09 AM, Sergio Jiménez Feijóo wrote:

> Hi Guys,
>
> I'm having trouble trying to add several flowmods to my OpenFlow switches.
> My application collects information from the network topology and
> calculates a (layer 2) route for every flow. Then it performs flow-mods in
> all the switches of the selected route in order to send the flow to its
> destination. I'm using as an example the "coreapps/switch" flowmod code.
> When my controller sends the flow-mod packets to the switches they respond
> with an error message (Specified buffer does not exist).
>
> My app worked nicely on a testbed of 6 Linksys WRT54GL with an OpenFlow
> capable firmware and NOX Zaku without FlowVisor. Now I'm using 5 NEC
> IP8800/S3640-24T2XW with NOX Destiny and FlowVisor and I'm experiencing
> this problem. Is the buffer_id really necessary? Can I add a flowmod
> without specifying any buffer_id? How can I avoid this error?
>
> I don't care about the packets that arrived before the flowmod being
> dropped. I just need to run a flowmod in several switches matching one
> single packet (the same one). I want all the switches to learn how to treat
> that type of packet all at the same time (I run a for loop in my code).
>
> Thank you for your help.
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Measuring delay of links between switches

[Kyriakos Zarifis]

Hi Bernd,

this sounds like an interesting idea to me, and something that could be
proven useful.
One concern is that in the trip from the controller to switch A, switch B
and back to the controller, you have the propagation delay of the control
channels, the propagation delay between A<->B, but also the processing
delay on the switches.
So some caution should be taken there in order to make sure that the
processing delay on the switches is minimized, in order to get the best
possible estimate of the delay of the link A<->B.
Also I would imagine that, say, if there was no other traffic, buffers were
all empty etc, even then different switches would perform a bit
differently, so that's another factor that would influence the estimation,
though it's probably negligible.


On Wed, Jan 11, 2012 at 7:33 AM, Bernd Wittefeld <
s9bew...@stud.uni-saarland.de> wrote:

> Hi,
> I am currently working on a component that needs a lot of statistical
> information about the current network state.
> In fact, I need the packet lLoss rate and the delay of single links
> between OpenFlow-switches.
> The PLR can be computed quite easily from the statistics that the switch
> gives me (tx_packets and rx_packets of switches that are connected via a
> link), but the delay turns out to be a problem.
> I have the following idea:
>
> I might use the discovery module and install an organizationally specific
> TLV that simply carries a timestamp and with every received LLDP packet, I
> can measure the time it takes for a packet to travel from controller to
> switchA to switchB and back to the controller. The links from the
> controller to the switches can be measured easily, so I can get a rough
> estimate of the Delay on the link (we don't talk about accuracy in the
> first place here :))
> The discovery module can then deliver the delay for a specific link via an
> API function.
>
> What do you think? Is this feasible? Is this way ok or do I abuse the LLDP
> protocol?
>
> If it's ok, the implementation might be relatively straight forward,
> adding a class to nox.lib.packet.lldp for my tlv and add a parser, then
> modify the discovery module and I should be fine?!
>
> If yes, do you have any other suggestions on how to implement this? I also
> thought about a custom component that builds a packet containing a
> timestamp and sends it out every switch port that is connected to another
> switch and install an Action on the target switch to forward that packet
> back to the controller. I don't know if this is feasible and would work in
> the first place (addressing and type of the packet carrying the timestamp
> for example would be a problem).
>
> Or am I completely wrong here? Is there anything that gives me this
> information?
>
> What do you think? I'm open for suggestions :)
>
> Thanks in advance!
>
> Bernd
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox-gui flowtracer problem

[Kyriakos Zarifis]

This seems to be a bug where the component was expecting a hex string, but
the "L" in the end of the long int messes things. Thanks for reporting.
What kind of switch are you using?

For a temporary fix in your case, try replacing line 95 with:
   value = int(value[:-1],16)

On Wed, Jan 4, 2012 at 11:07 PM, wunyuan  wrote:

> Dear all，
>
> I build a testbed as follows:
>
>   NOX
>   /  \
>of1of2
> /\
>ab
> Firstly, I set a and b to ping each other. Secondly, I input "./nox_core
> -v -v -i ptcp:9550 routing lavi monitoring trackhost_pktin" to run the NOX.
> and then start nox-gui. Thirdly, I click "FlowTracer" botton and then
> double click of1 node on nox-gui to show its flow entries. Finally, I
> highlight one entry and click "Trace!" botton. However,I cannot find any
> flows on nox-gui and I find one error message. this error message is as
> follows:
>
> File "~/nox/src/gui/views/**flowtracer.py", line 95, in trace_flow
>value = int(value,16)
> ValueError: invalid literal for int() with base 16: '0xe4115b1251b4L'
>
> How could I fix it?
>
> --
>
> ==**==**===
> 系統與網路技術組－黃文源(Wun-Yuan Huang)
> 財團法人國家實驗研究院
> 國家高速網路與計算中心南部事業群
> National Center for High-Performance Computing South Region Office
> 台南縣台南科學園區南科三路28號
> No.28, Nan-Ke 3rd. Rd., Science-based Industrial Park, Tainan 744, Taiwan,
> R.O.C.
> TEL：06-5050940 ext.751
> FAX：06-5050945
> E-Mail：wuny...@nchc.narl.org.**tw 
> ==**==**===
>
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Nox on netkit

[Kyriakos Zarifis]

Did you try to install swig?
something like "apt-get install swig" should do it

On Fri, Dec 30, 2011 at 3:31 PM, Francesco Pocci
wrote:

> Hi,
> I'm just trying to install Nox controller on a virtual machine created
> with netkit, with some problem. One of this is that i have this error:
>
> configure:error: when configured with python, NOX requires swig 1.3.0 or
> later to be installed
>
> At this point i google this problem and i have found no real fix for this
> issue.
>
> what can i do?
>
> regards
> F.P.
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Can i use Tcpreplay with NOX

[Kyriakos Zarifis]

According to the spec, the output port is invalid. Are you sure you are
sending the action of your flow_mods correctly? The port would need to be a
valid ovs port (the interface needs to have been added to ovs)

On Tue, Dec 27, 2011 at 12:34 AM, ali ahmad  wrote:

>  Hi all,
>
> I have a network traffic trace-file for a segment of my network and i want
> to analyze it in time frames i.e analyzing flows after every 10 sec. For
> this i have installed NOX and openvswitch on a ubuntu virtual machine and
> have created another virtual machine from which i am replaying by tracefile
> using tcpreplay on the same interface that both VM share. Packets are
> received at the switch and corresponding packetin event are generated and i
> can setup the flow fields. But i cannot add the flows in the switch flow
> table and error message is generated by openvswitch with type 2 and code 4
> and what i am getting that it is openvswitch is enable to differentiate
> between physical and logical port is their anyway to recitfy this error.
>
> Regards,
>
> Ali Ahmad
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Nox messenger example for external c++ and nox python

[Kyriakos Zarifis]

I'm afraid I don't have an immediate answer as I haven't used the messenger
from c++, and I can't think right now of a c++ that does, for reference.

On Tue, Dec 20, 2011 at 1:09 AM, Harshil Anil Kumar Shah <
harshil_s...@infosys.com> wrote:

> Hi,
>
> In my case where external module is C++ then can I use “pyobject” to
> interact with python module?
>
> ** **
>
> *From:* Harshil Anil Kumar Shah
> *Sent:* Monday, December 19, 2011 3:32 PM
> *To:* 'Kyriakos Zarifis'
> *Cc:* nox-dev@noxrepo.org
> *Subject:* RE: [nox-dev] Nox messenger example for external c++ and nox
> python
>
> ** **
>
> Thanks Zarifis…
>
> ** **
>
> I looked at GUI example. It seems very useful. But in my case, client is
> external C++ module. So in that case do I have to use use messenger.cpp??*
> ***
>
> ** **
>
> -Harshil.****
>
> ** **
>
> *From:* nox-dev-boun...@noxrepo.org [mailto:nox-dev-boun...@noxrepo.org] *On
> Behalf Of *Kyriakos Zarifis
>
> *Sent:* Monday, December 19, 2011 1:38 PM
> *To:* Harshil Anil Kumar Shah
> *Cc:* nox-dev@noxrepo.org
> *Subject:* Re: [nox-dev] Nox messenger example for external c++ and nox
> python
>
> ** **
>
> Hi Harshil,
>
> ** **
>
> it might not be the simplest example, but the GUI communicates with NOX
> using the messenger, so taking a look at that code might be a good starting
> point.
>
> ** **
>
> Specifically, the file communication.py is responsible on the GUI side.
> Similarly on the NOX side, the code that uses the messenger to send
> messages to the GUI is inside the respective component that talks to the
> GUI. The component "monitoring" is one of them.
>
>
> Some of this is documented on the wiki here:
>
>
> http://noxrepo.org/noxwiki/index.php/NOX_GUI#Connecting_a_subview_to_a_NOX_component
> 
>
> On Sun, Dec 18, 2011 at 10:41 PM, Harshil Anil Kumar Shah <
> harshil_s...@infosys.com> wrote:
>
> Hi,
>
>  
>
> I want to exchange messages between external C++ module and python module
> in Nox using protobuf messages. I browsed through couple of posts, I
> figured out I can  use coreapps/messenger. Can I get some working example
> how messenger code can be used for message exchange between external c++
> and nox python module.
>
>  
>
> *Regards,*
>
> *Harshil Shah,*
>
> Convergence Lab, Infosys Labs
>
> Infosys | Bangalore
>
> *Mob #** : +91 97428 87966.*
>
>  
>
>  CAUTION - Disclaimer *
>
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
> 
>
> for the use of the addressee(s). If you are not the intended recipient, 
> please 
>
> notify the sender by e-mail and delete the original message. Further, you are 
> not 
>
> to copy, disclose, or distribute this e-mail or its contents to any other 
> person and 
>
> any such actions are unlawful. This e-mail may contain viruses. Infosys has 
> taken 
>
> every reasonable precaution to minimize this risk, but is not liable for any 
> damage 
>
> you may sustain as a result of any virus in this e-mail. You should carry out 
> your 
>
> own virus checks before opening the e-mail or attachment. Infosys reserves 
> the 
>
> right to monitor and review the content of all messages sent to or from this 
> e-mail 
>
> address. Messages sent to or from this e-mail address may be stored on the 
> 
>
> Infosys e-mail system.
>
> ***INFOSYS End of Disclaimer INFOSYS***
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
> ** **
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] error in "flowtracer" component

[Kyriakos Zarifis]

Right. Basically, the component only makes sense with the GUI, which
requires 'monitoring', which will start 'jsonmessenger' as a dependency. So
the assumption is that you run 'monitoring'. But 'jsonmessenger' should
probably be added to flowtracer's meta.json anyway.. It'd still be
meaningless to run the component without the gui, but you'd avoid this
message. BTW I think flowtracer hasn't been thoroughly tested, so use at
your own discretion:>

On Tue, Dec 20, 2011 at 1:48 AM, Murphy McCauley  wrote:

> flowtracer should have jsonmessenger as a dependency, but doesn't.
>
> Either edit flowtracer's meta.json file to add jsonmessenger as a
> dependency, or simply specify jsonmessenger on the commandline before
> flowtracer (e.g., nox_core jsonmessenger flowtracer).
>
> Hope that helps.
>
> -- Murphy
>
> On Dec 20, 2011, at 1:40 AM, Siddharth Sharma wrote:
>
> Hi,
>
> The *flowtracer component* in NOX controller is not working. When I
> try to run the component, it shows me the following error :
>
>
>
> 00073|nox|ERR:Cannot change the state of 'flowtracer' to INSTALLED:
> 'flowtracer' ran into an error:
> cannot import a Python module 'nox.netapps.flowtracer.flowtracer':
> Traceback (most recent call last):
>   File "./nox/netapps/flowtracer/flowtracer.py", line 12, in 
> from nox.coreapps.messenger.pyjsonmsgevent import JSONMsg_event
>   File "./nox/coreapps/messenger/pyjsonmsgevent.py", line 25, in
> 
> _pyjsonmsgevent = swig_import_helper()
>   File "./nox/coreapps/messenger/pyjsonmsgevent.py", line 21, in
> swig_import_helper
> _mod = imp.load_module('_pyjsonmsgevent', fp, pathname,
> description)
> ImportError: ./nox/coreapps/messenger/_pyjsonmsgevent.so: undefined
> symbol: vigil::JSONMsg_event::JSONMsg_event(vigil::core_message const*)
>
>
>
>
> Please rectify the problem.
>
> Thank You
>
> Regards
> Siddharth
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Nox messenger example for external c++ and nox python

[Kyriakos Zarifis]

Hi Harshil,

it might not be the simplest example, but the GUI communicates with NOX
using the messenger, so taking a look at that code might be a good starting
point.

Specifically, the file communication.py is responsible on the GUI side.
Similarly on the NOX side, the code that uses the messenger to send
messages to the GUI is inside the respective component that talks to the
GUI. The component "monitoring" is one of them.

Some of this is documented on the wiki here:
http://noxrepo.org/noxwiki/index.php/NOX_GUI#Connecting_a_subview_to_a_NOX_component

On Sun, Dec 18, 2011 at 10:41 PM, Harshil Anil Kumar Shah <
harshil_s...@infosys.com> wrote:

> Hi,
>
> ** **
>
> I want to exchange messages between external C++ module and python module
> in Nox using protobuf messages. I browsed through couple of posts, I
> figured out I can  use coreapps/messenger. Can I get some working example
> how messenger code can be used for message exchange between external c++
> and nox python module.
>
> ** **
>
> *Regards,*
>
> *Harshil Shah,*
>
> Convergence Lab, Infosys Labs
>
> Infosys | Bangalore
>
> *Mob #** : +91 97428 87966**.*
>
> ** **
>
>  CAUTION - Disclaimer *
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> notify the sender by e-mail and delete the original message. Further, you are 
> not
> to copy, disclose, or distribute this e-mail or its contents to any other 
> person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has 
> taken
> every reasonable precaution to minimize this risk, but is not liable for any 
> damage
> you may sustain as a result of any virus in this e-mail. You should carry out 
> your
> own virus checks before opening the e-mail or attachment. Infosys reserves the
> right to monitor and review the content of all messages sent to or from this 
> e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS End of Disclaimer INFOSYS***
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Matching aggregate stats responses to requests

[Kyriakos Zarifis]

Hi Shrutarhi,

Destiny is definitely the recommended branch, that's right.

just like you noticed, monitoring generates xids itself, and the epoch is
specific to it. The epoch is just some variable (secs) defined on the top
of the file. However it also increments the xids when an asynchronous user
request occurs (e.g. when a user double-clicks on a switch on the gui to
get it's current flow table). So the xid is incremented for each periodical
or manual request.

If I recall correctly, an earlier patch on destiny generalized this so that
all requests (from any component) have their xid automatically generated
and filled by NOX's packing library (unless you override them and manually
assign one). This is definitely true for C++ components, but I think it has
been exposed to the python side too (relevant
patches<http://noxrepo.org/cgi-bin/gitweb.cgi?p=nox&a=search&h=refs%2Fheads%2Fdestiny&st=commit&s=+xid+>
)

On Fri, Dec 9, 2011 at 10:31 AM, Shrutarshi Basu wrote:

> Hi Kyriakos,
> I've been looking through the monitoring app and figuring out how to use
> xids. It seems like you're using collection_epoch to generate new xids and
> collection_epoch is just a logical clock. However I couldn't tell when you
> are advancing the clock. Is this application specific or is there some rule
> for generating xids that I'm missing?
> Thanks,
> Basu
>
>
> On Fri, Dec 9, 2011 at 12:44 PM, Shrutarshi Basu wrote:
>
>> Thank you, I just checked out the Destiny branch. From what I can tell
>> Destiny seems to be the recommended branch for NOX development. Is that
>> correct?
>>
>>
>> On Thu, Dec 8, 2011 at 7:47 PM, Kyriakos Zarifis 
>> wrote:
>>
>>> Ah, you're also looking at coreapps/examples/monitor.py
>>> I was referring to netapps/monitoring.py   (you can find that in the
>>> destiny branch)
>>> (monitor.py is a much simpler, early monitoring component)
>>>
>>>
>>> On Thu, Dec 8, 2011 at 10:26 AM, Shrutarshi Basu 
>>> wrote:
>>>
>>>> Thanks, it looks like I am working with an older version of NOX -- I
>>>> can see a monitor.py app that does not seem to use the xid at all. I will
>>>> try to upgrade and see what I can do. Will report back.
>>>> Thanks,
>>>> Basu
>>>>
>>>>
>>>> On Wed, Dec 7, 2011 at 4:27 PM, Kyriakos Zarifis >>> > wrote:
>>>>
>>>>> Hi Shrutarshi,
>>>>>
>>>>> the field you should be looking at is the xid (transaction id).
>>>>> I don't remember the specifics right now - I think in Destiny it is
>>>>> automatically set (and returned?) and you can also set it when you send 
>>>>> the
>>>>> request (that's what the monitoring module does)
>>>>>
>>>>> I can be more specific when I look at the code to refresh my memory,
>>>>> but this might help for now
>>>>>
>>>>> On Wed, Dec 7, 2011 at 12:29 PM, Shrutarshi Basu >>>> > wrote:
>>>>>
>>>>>> If I send a bunch of aggregate stats requests for different flows, is
>>>>>> there a way for the aggregate_stats_in handler to know which response it 
>>>>>> is
>>>>>> being called on? I see that it gets the dpid, but what if I have multiple
>>>>>> flows on the same dpid that I want information on?
>>>>>> Thanks,
>>>>>> Basu
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Shrutarshi Basu
>>>>>> Basus.me
>>>>>> The ByteBaker <http://bytebaker.com> -- because Computer Science is
>>>>>> not about computers
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> nox-dev mailing list
>>>>>> nox-dev@noxrepo.org
>>>>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Shrutarshi Basu
>>>> Basus.me
>>>> The ByteBaker <http://bytebaker.com> -- because Computer Science is
>>>> not about computers
>>>>
>>>>
>>>
>>
>>
>> --
>> --
>> Shrutarshi Basu
>> Basus.me
>> The ByteBaker <http://bytebaker.com> -- because Computer Science is not
>> about computers
>>
>>
>
>
> --
> --
> Shrutarshi Basu
> Basus.me
> The ByteBaker <http://bytebaker.com> -- because Computer Science is not
> about computers
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Matching aggregate stats responses to requests

[Kyriakos Zarifis]

Ah, you're also looking at coreapps/examples/monitor.py
I was referring to netapps/monitoring.py   (you can find that in the
destiny branch)
(monitor.py is a much simpler, early monitoring component)

On Thu, Dec 8, 2011 at 10:26 AM, Shrutarshi Basu wrote:

> Thanks, it looks like I am working with an older version of NOX -- I can
> see a monitor.py app that does not seem to use the xid at all. I will try
> to upgrade and see what I can do. Will report back.
> Thanks,
> Basu
>
>
> On Wed, Dec 7, 2011 at 4:27 PM, Kyriakos Zarifis wrote:
>
>> Hi Shrutarshi,
>>
>> the field you should be looking at is the xid (transaction id).
>> I don't remember the specifics right now - I think in Destiny it is
>> automatically set (and returned?) and you can also set it when you send the
>> request (that's what the monitoring module does)
>>
>> I can be more specific when I look at the code to refresh my memory, but
>> this might help for now
>>
>> On Wed, Dec 7, 2011 at 12:29 PM, Shrutarshi Basu wrote:
>>
>>> If I send a bunch of aggregate stats requests for different flows, is
>>> there a way for the aggregate_stats_in handler to know which response it is
>>> being called on? I see that it gets the dpid, but what if I have multiple
>>> flows on the same dpid that I want information on?
>>> Thanks,
>>> Basu
>>>
>>> --
>>> --
>>> Shrutarshi Basu
>>> Basus.me
>>> The ByteBaker <http://bytebaker.com> -- because Computer Science is not
>>> about computers
>>>
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>
>
> --
> --
> Shrutarshi Basu
> Basus.me
> The ByteBaker <http://bytebaker.com> -- because Computer Science is not
> about computers
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Matching aggregate stats responses to requests

[Kyriakos Zarifis]

Hi Shrutarshi,

the field you should be looking at is the xid (transaction id).
I don't remember the specifics right now - I think in Destiny it is
automatically set (and returned?) and you can also set it when you send the
request (that's what the monitoring module does)

I can be more specific when I look at the code to refresh my memory, but
this might help for now

On Wed, Dec 7, 2011 at 12:29 PM, Shrutarshi Basu wrote:

> If I send a bunch of aggregate stats requests for different flows, is
> there a way for the aggregate_stats_in handler to know which response it is
> being called on? I see that it gets the dpid, but what if I have multiple
> flows on the same dpid that I want information on?
> Thanks,
> Basu
>
> --
> --
> Shrutarshi Basu
> Basus.me
> The ByteBaker  -- because Computer Science is not
> about computers
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Component: hosttracker

[Kyriakos Zarifis]

Ah, ok. So I'm not sure exactly how the logic that detects if a host has
been removed is implemented, as I didn't write this component. So I don't
know when the "delete" message is sent for hosts.
I could take a look and get back to you. The logic should be somewhere
inside LAVI/hosttracker, and it might be something along the lines of "if
you haven't heard any traffic from host, remove it, or 'if you hear traffic
from host X on port B, but X is registered on port A, remove it from A".

(for example - what do *you* mean when you say "when I remove the host? :).
In a physical environment, this can mean turning the machine off, or
unplugging its network cable, both of which events aren't easily detectable
from the network's perspective)

On Mon, Dec 5, 2011 at 10:25 PM, ztom  wrote:

>  > when you say the front-end, do you mean noxconsole? the GUI?
> GUI, nox-gui.py
>
>
> > (you can take a look at the GUI to see how the message exchange happens
> and what they messages look like.. the code should be in topology.py)
> I know the process of msg exchange,
> back-end(jsonmsg)->view_interface(signal/slot)->GUI. But when I remove the
> host, nox(with LAVI component) will send a jsonmsg including "node_type:
> host, command: delete". Actually, it doesn't, so I'm confused.
>
> --
> Date: Mon, 5 Dec 2011 22:14:47 -0800
> Subject: Re: [nox-dev] Component: hosttracker
> From: kyr.zari...@gmail.com
> To: switch@hotmail.com
> CC: nox-dev@noxrepo.org
>
>
> when you say the front-end, do you mean noxconsole? the GUI?
> (you can take a look at the GUI to see how the message exchange happens
> and what they messages look like.. the code should be in topology.py)
>
> On Mon, Dec 5, 2011 at 9:28 PM, ztom  wrote:
>
>  Hi~ alls,
>
> I found a component named "hosttracker" with source code, and it can
> handle adding or removing of hosts.
> But when I run it with nox_core($ ./nox_core -v -i ptcp:6633 monitoring
> hosttracker), the front-end still can't receive the jsonmsg
> as "{'node_type': 'host', 'command':'add/remove'}". What should i do???
>
> ---
> thanks
> tom
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Component: hosttracker

[Kyriakos Zarifis]

when you say the front-end, do you mean noxconsole? the GUI?
(you can take a look at the GUI to see how the message exchange happens and
what they messages look like.. the code should be in topology.py)

On Mon, Dec 5, 2011 at 9:28 PM, ztom  wrote:

>  Hi~ alls,
>
> I found a component named "hosttracker" with source code, and it can
> handle adding or removing of hosts.
> But when I run it with nox_core($ ./nox_core -v -i ptcp:6633 monitoring
> hosttracker), the front-end still can't receive the jsonmsg
> as "{'node_type': 'host', 'command':'add/remove'}". What should i do???
>
> ---
> thanks
> tom
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] FW: Help: LAVI and NOX's nox-gui.py

[Kyriakos Zarifis]

Oh, also, there is one component that is responsible for tracking host
traffic, and that's what feeds the host information to LAVI and eventually
to the GUI
I can't remember if it is there as a dependency, so you might need to run
that manually. I think the name is "trackhost_pktin" (can't check right now
unfortunately). So maybe try adding that too after "monitoring" and
"pyswitch" ?

On Fri, Dec 2, 2011 at 11:24 AM, Kyriakos Zarifis wrote:

> Hi,
>
> the hosts should appear when they talk to the network. Did you try
> generating some traffic? A simple ping should do it
>
> (btw, I think "lavi" is not required as an argument as IIRC it's a
> dependency of monitoring anyway)
>
> On Fri, Dec 2, 2011 at 1:21 AM, ztom  wrote:
>
>>
>> Hi~ alls,
>> I used LAVI and nox-gui.py(another front-end as ENVI), and tested some
>> cases with NOX and openvswitch, one switch links to one host,  my cmd is "$
>> ./nox_core -v -i ptcp:6633 monitoring pyswitch lavi ", but there's no host
>> icon and hs2sw link in nox-gui's view, just swicth icon.  Could someone
>> help me...
>>
>> ---
>> thanks a lot
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] FW: Help: LAVI and NOX's nox-gui.py

[Kyriakos Zarifis]

Hi,

the hosts should appear when they talk to the network. Did you try
generating some traffic? A simple ping should do it

(btw, I think "lavi" is not required as an argument as IIRC it's a
dependency of monitoring anyway)

On Fri, Dec 2, 2011 at 1:21 AM, ztom  wrote:

>
> Hi~ alls,
> I used LAVI and nox-gui.py(another front-end as ENVI), and tested some
> cases with NOX and openvswitch, one switch links to one host,  my cmd is "$
> ./nox_core -v -i ptcp:6633 monitoring pyswitch lavi ", but there's no host
> icon and hs2sw link in nox-gui's view, just swicth icon.  Could someone
> help me...
>
> ---
> thanks a lot
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] JSON messages

[Kyriakos Zarifis]

Hi Alex,

can you clarify what you mean by "JSON messages to add/delete flows from
"outside" thru NOX"?


On Fri, Nov 18, 2011 at 4:45 AM, Alex  wrote:

> Hi,
>
> I'm using NOX to get stats about an openflow network.
> I know that it is possible to get the flow table entries or the portstats
> with requests in JSON form when the monitoring component is running.
> But what about JSON messages to add/delete flows from "outside" thru NOX?
> Is it possible sowehow?
>
> Regards,
>
> Alex
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Not able to send ARP Reply

[Kyriakos Zarifis]

Hello,

How exactly did you figure out that the ARP is not received? Id try the
following troubleshooting steps to see where the problem is:
Did you try to use wireshark to see how far you ARP packet goes?
Is it actually sent out the controller interface? (it probably is)
Is it being received on the switch interface? (this might not be true,
depending on how you constructed the ARP)
If yes, is it properly formed? Can the switch process it and install an arp
entry from it?

(you could also paste the code where you construct/send the ARP)

On Mon, Nov 14, 2011 at 5:05 AM, Harshil Anil Kumar Shah <
harshil_s...@infosys.com> wrote:

> Hi,
>
> Currently, I am trying to send ARP Reply to my openflow switch from
> NOX-0.8. In the debug message it shows that ARP Reply is sent and also
> shows the packet information. But I am not able to receive it on my
> openflow switch. What can be the solution?
>
> ** **
>
> Thanks in advance.
>
> ** **
>
> *Regards,*
>
> *Harshil Shah,*
>
> Convergence Lab, Infosys Labs
>
> Infosys | Bangalore
>
> *Mob #** : +91 97428 87966**.*
>
> ** **
>
>  CAUTION - Disclaimer *
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> notify the sender by e-mail and delete the original message. Further, you are 
> not
> to copy, disclose, or distribute this e-mail or its contents to any other 
> person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has 
> taken
> every reasonable precaution to minimize this risk, but is not liable for any 
> damage
> you may sustain as a result of any virus in this e-mail. You should carry out 
> your
> own virus checks before opening the e-mail or attachment. Infosys reserves the
> right to monitor and review the content of all messages sent to or from this 
> e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS End of Disclaimer INFOSYS***
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Getting flow table entries from switch

[Kyriakos Zarifis]

Exactly. FWIW, this is the API that the GUI uses and they were developed in
parallel. If you want to parse the flow table and act on that, you should
use that Monitoring API. If all you need to do is print it out / look at it
you might as well use the GUI directly - but it any case you can look there
for example usage (although it pretty much boils down to what Aaron said)

On Thu, Nov 10, 2011 at 6:45 PM, Aaron Rosen  wrote:

> you also need to:
>
> from nox.netapps.monitoring.monitoring import Monitoring
>
> On Thu, Nov 10, 2011 at 9:44 PM, Aaron Rosen  wrote:
>
>> Hi Theo,
>>
>> Yup there is a Monitoring.send_flow_stats_request()
>>
>> Cheers,
>>
>> Aaron
>>
>> P.S: here are some hints to get it working if it helps:
>>
>> import nox.lib.pyopenflow as of
>>
>>
>> def send_flow_stats_request():
>>global xid
>>flows = of.ofp_match()
>>flows.wildcards = of.OFPFW_ALL  ^ of.OFPFW_DL_SRC
>>match_this_mac = "00:11:22:33:44:55"
>>flows.dl_src =  [int(a[0:2],
>> 16),int(a[3:5],16),int(a[6:8],16),int(a[9:11],16),int(a[12:14],16),int(a[15:17],16)]
>>inst.Monitoring.send_flow_stats_request(dpid, flows, 0xff, xid);
>>xid +=1
>>
>> def flow_stats_in_handler(dpid, flows, more, xid):
>> print str(dpid) + " " + str(flows)
>> for i in flows:
>> print flows[i]
>>
>>
>>
>> You also have to register it with:
>>
>> inst.register_for_flow_stats_in(flow_stats_in_handler)
>>
>>
>>
>>
>>
>>
>> On Thu, Nov 10, 2011 at 9:30 PM, Theophilus Benson 
>> wrote:
>>
>>> Is it possible to programmatically get the flow table entries from a
>>> switch.  I know that aggregate flow stats gives that tells you the number
>>> of bytes sent/received, number of flows matched and match mask for each
>>> flow entries.  However, I wanted the actual flow table entry itself.
>>>
>>> Theo
>>> __**_
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/**listinfo/nox-dev
>>>
>>
>>
>>
>> --
>> Aaron O. Rosen
>> Masters Student - Network Communication
>> 306B Fluor Daniel
>>
>>
>>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] can nox support two more controllers

[Kyriakos Zarifis]

It is not really a goal for NOX, so I doubt it will be a feature in the
future.
If you provide some more information on what you want to do and why you
need multiple controllers, I or somebody else might be able to share some
thoughts.

If you want multiple instances of the same controller for load distribution
and reliability, it becomes really tricky because you need to keep them
synchronized. For some insight (on how tricky it is), you can take a look
at this paper
http://www.usenix.org/event/osdi10/tech/full_papers/Koponen.pdf


On Sun, Nov 6, 2011 at 12:53 AM, hzy  wrote:

> Thank you for your reply.
> Will the future version of NOX support this feature?
> If I can do this to extend the NOX? I know it's maybe very hard, but I
> really want to try?
> Can you give me some advices?
>
> 2011/11/6 Kyriakos Zarifis 
>
>> Hi,
>>
>> NOX does not support multiple controller instances inherently. This means
>> that there is no defined protocol for communication between controller
>> instances or a way to distribute state between them. So the general answer
>> is no.
>>
>> Depending on what you want to do exactly, the answer might be different:
>> Theoretically, you can have different switches connect to different
>> controllers, but the controllers will not know about each other's existence
>> and wouldn't act as a single control entity. It would be like having 2
>> separate control domains and each controller would have a global view of
>> their domain only, which is not very useful.
>>
>> (The statement about nox-console does not have to do anything with
>> multiple controllers support. Nox-console is rather a tool used to send
>> commands to a controller from a terminal.)
>>
>> On Sun, Nov 6, 2011 at 12:09 AM, hzy  wrote:
>>
>>> hi all:
>>> The zaku release of nox *Preliminary support for a console
>>> (nox-console).
>>> Is that mean I can't open two controllers. I wander if I can have two
>>> controllers work together with one control several switches and the other
>>> one control the rest switches.
>>> Any ideas?
>>> Thank you for advance.
>>> *
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] can nox support two more controllers

[Kyriakos Zarifis]

Hi,

NOX does not support multiple controller instances inherently. This means
that there is no defined protocol for communication between controller
instances or a way to distribute state between them. So the general answer
is no.

Depending on what you want to do exactly, the answer might be different:
Theoretically, you can have different switches connect to different
controllers, but the controllers will not know about each other's existence
and wouldn't act as a single control entity. It would be like having 2
separate control domains and each controller would have a global view of
their domain only, which is not very useful.

(The statement about nox-console does not have to do anything with multiple
controllers support. Nox-console is rather a tool used to send commands to
a controller from a terminal.)

On Sun, Nov 6, 2011 at 12:09 AM, hzy  wrote:

> hi all:
> The zaku release of nox *Preliminary support for a console (nox-console).
> Is that mean I can't open two controllers. I wander if I can have two
> controllers work together with one control several switches and the other
> one control the rest switches.
> Any ideas?
> Thank you for advance.
> *
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] pyswitch pop error type information and very much info type information

[Kyriakos Zarifis]

1. You probably get the first error because your topology is a loop and the
switch is getting a packet for a host H and sees that the port that it
thinks it's supposed to send the packet to (learned port) is the same port
where it received the packet (inport).
The learned port is the same as the inport because at some point before
this error happened, the switch received a packet from host H on that port,
and registered the host on that port.

2. What kind of data traffic are you sending?

3. Associating a flow to a VLAN is just another action, like sending a flow
out a port. For the latter, you'd use action OFPAT_OUTPUT. For setting a
VLAN to a flow, you use the action OFPAT_SET_VLAN_VID. This is described in
section 5.2.4. of the spec

On Mon, Oct 31, 2011 at 7:11 AM, dongxia pan  wrote:

> hi, when I execute nox_core with the form: sudo ./nox_core -v -i ptcp:6633
> pyswitch monitoring.
>
> two openvswitches directly link to two physical switches  separatly, which
> don't support openflow protocol.
>
> controller brings about error and info information,as follows:
>
> 1. pyswitch | ERR:' ** warning** learned port = inport'
> 2.00043 | packet | INFO: (udp parse) warning UDP packet data shorter than
> UDP len: 94 < 147
>
> what causes these results ?  is there any one who can give me some hints
> or reasons?
>
> another question: how to configure a VLAN using NOX ?
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] re-build only changed module

[Kyriakos Zarifis]

Hi Rafal,

I think the build system will only compile files that have changed or have
been affected by changes (e.g. adding an include etc), so it generally
won't compile more than it needs to. Unfortunately I don't know of any way
that will reduce the amount of files that are compiled. You may get some
speed up by doing "make -j 5" instead of "make"

On Mon, Oct 31, 2011 at 8:16 AM, Rafał Oracz  wrote:

> Hi,
>
> Is there any possibility to build only C++ module which has been changed?
> Compiling whole nox takes a few long minutes, and if you do it often it is
> very disruptive.
>
> thanks.
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to use discovery component？

[Kyriakos Zarifis]

If git clone works for your host machine but not the VM, your VM is probably
not connected to the internet.

On Sat, Oct 29, 2011 at 8:12 PM, hzy  wrote:

> hi kyriakos:
> It is very strange. When I try the commands in my computer(not the vm in my
> computer) it works.
> But I want to update the nox code in my vm.
>
> 在 2011年10月30日 上午11:06，hzy 写道：
>
> hi kyriakos:
>>
>> I checked my directory ~/noxcore/src/nox/netapps, but I could not find the
>> file monitoring.py.
>> I think the nox I used is zaku, how can I change to destiny.
>>
>> When I type "git clone git://noxrepo.org/nox", the following information
>> come up.
>> openflow@openflowvm:~$ git clone git://noxrepo.org/nox
>> Initialized empty Git repository in /home/openflow/nox/.git/
>> noxrepo.org[0: 69.56.251.103]: errno=Connection timed out
>> fatal: unable to connect a socket (Connection timed out)
>>
>> I wonder if I miss some steps.
>>
>> Thank your for advance.
>> hzy
>>
>>
>> 2011/10/28 Kyriakos Zarifis 
>>
>>> Hi,
>>>
>>> like you noticed, the 'discovery' component does not provide any
>>> information like that. It only does neighbor discovery.
>>> If you want to collect switch related information, you need to write your
>>> own component and collect that information programatically using NOX's API
>>> to do switch queries etc.
>>>
>>> The 'monitoring' component (under netapps/) has some very relevant
>>> functionality, so you will find it useful to look at, or even copy code from
>>> it. What 'monitoring' does is that is periodically sends out a bunch of
>>> queries to all connected switches, collects statistics and exposes that info
>>> to other components. It sounds similar to what you want to do.
>>>
>>> One way you could go about measuring a link's utilization is to
>>> periodically see how many bytes have been sent out a port. The bytes sent
>>> over a period T divided by T will give you a rough estimate of the Tx rate.
>>> Divide that by link capacity for a rough estimate of utilization. The
>>> smaller the period, the better the estimate, but the more control traffic.
>>> 'monitoring' also does something like that, so you can take a look there.
>>>
>>>
>>> On Thu, Oct 27, 2011 at 11:48 PM, hzy  wrote:
>>>
>>>> hi Kyriakos：
>>>>
>>>> Thank you for your reply. I have solved my problem. But the discovery
>>>> component doesn't meat my requirement.
>>>> I want to collect the link information dynamically. e.g. the utilization
>>>> rate of bandwith. Can I get this kind of information directly? If not what
>>>> can I do to fit my aim? Can you give me some davices?
>>>>
>>>> thanks for advance.
>>>>
>>>>
>>>>
>>>>
>>>> 2011/10/11 Kyriakos Zarifis 
>>>>
>>>>> Hi there,
>>>>>
>>>>> in order use Link_events in your python component you need to:
>>>>>
>>>>> 1) make your component aware of the Link_event object by importing it
>>>>> 2) register a handler for the event in your component's configure() (to
>>>>> make your component respond to such events)
>>>>> 3) write a handler (to tell your component how it should respond to
>>>>> such events)
>>>>>
>>>>> so, in practice:
>>>>>
>>>>> # 1
>>>>> from nox.netapps.discovery.pylinkevent import Link_event
>>>>> ...
>>>>> # 2
>>>>> def install(self):
>>>>> ...
>>>>> self.register_handler(Link_event.static_get_name(),
>>>>> self.handle_link_event)
>>>>> 
>>>>> # 3
>>>>> def handle_link_event(self, e):
>>>>> print "Received link event:", e.__dict__# this will show
>>>>> you the contents of the event (for example: 'dport': 2, 'dpsrc': 1L,
>>>>> 'dpdst': 2L, 'sport': 2, 'action': 'add')
>>>>> # do something about the event here
>>>>>
>>>>>
>>>>> On Tue, Oct 11, 2011 at 3:17 AM, hzy  wrote:
>>>>>
>>>>>> Hi murphy:
>>>>>>
>>>>>> yes, the results are t

Re: [nox-dev] Building custom events

[Kyriakos Zarifis]

correct:>

On Fri, Oct 28, 2011 at 7:47 AM, andrea simeoni
wrote:

> Hi guys,
>
> I solved the problem by adding the line:
>
> *register_event(Observation_event::static_get_name());*
>
> In the configuration method of the component that generates the event.
>
>
> 2011/10/28 andrea simeoni 
>
>> Hi guys,
>>
>> I've created a custom event in my NOX environment: "Observation_event".
>> I'm able to compile my code, and I'm able to post the event; but if I need
>> to handle the event, when launching NOX I got the following error:
>> *
>> |nox|ERR:Cannot change the state of 'MyComp' to INSTALLED:
>> 'MyComp' ran into an error:
>> Event 'Observation_event' doesn't exist.*
>>
>> Where MyComp is the component that needs to handle the event. The code in
>> its configuration function is the following:
>>
>>  void MyComp::configure(const Configuration* c)
>>   {
>> lg.dbg(" Configure called ");
>>
>>  register_handler
>>   (boost::bind(&MioComp::handle_observation_event, this, _1));
>>   }
>>
>>
>> I tried also to add the event in the nox/src/etc/nox.json, including also
>> the name of MyComp in the priority list, but the outcome is the same.
>> Any suggestions? I'm forgetting some step?
>>
>> Thank you
>>
>>
>>
>>
>> --
>> Andrea Simeoni
>>
>
>
>
> --
> Andrea Simeoni
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to add the components of mobilevms to NOX destiny

[Kyriakos Zarifis]

Great.
Make sure you add a space between "ptcp:" and "mobilevms"
What should come right after the ":" is a port number optionally, then
space, then a space-separated list of the components you want to run.

On Fri, Oct 28, 2011 at 1:15 AM, 王健  wrote:

> I have solved this problem with your help. Thank you very much sincerely!!!
> I just forget to add the mobilevms to configure.ac.in. When i run
> ./nox_core -v -v -i ptcp:mobilevms, the output is normal . Next step i will
> check whether it can work fine in my network system~
> best regard
>
>
> wang jian
>
> Friday, October 28, 2011
>
>
> --
> 网易公开课推出哈佛最受欢迎《幸福》课程，帮您修满幸福学分!
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to use discovery component？

[Kyriakos Zarifis]

Hi,

like you noticed, the 'discovery' component does not provide any information
like that. It only does neighbor discovery.
If you want to collect switch related information, you need to write your
own component and collect that information programatically using NOX's API
to do switch queries etc.

The 'monitoring' component (under netapps/) has some very relevant
functionality, so you will find it useful to look at, or even copy code from
it. What 'monitoring' does is that is periodically sends out a bunch of
queries to all connected switches, collects statistics and exposes that info
to other components. It sounds similar to what you want to do.

One way you could go about measuring a link's utilization is to periodically
see how many bytes have been sent out a port. The bytes sent over a period T
divided by T will give you a rough estimate of the Tx rate. Divide that by
link capacity for a rough estimate of utilization. The smaller the period,
the better the estimate, but the more control traffic. 'monitoring' also
does something like that, so you can take a look there.


On Thu, Oct 27, 2011 at 11:48 PM, hzy  wrote:

> hi Kyriakos：
>
> Thank you for your reply. I have solved my problem. But the discovery
> component doesn't meat my requirement.
> I want to collect the link information dynamically. e.g. the utilization
> rate of bandwith. Can I get this kind of information directly? If not what
> can I do to fit my aim? Can you give me some davices?
>
> thanks for advance.
>
>
>
>
> 2011/10/11 Kyriakos Zarifis 
>
>> Hi there,
>>
>> in order use Link_events in your python component you need to:
>>
>> 1) make your component aware of the Link_event object by importing it
>> 2) register a handler for the event in your component's configure() (to
>> make your component respond to such events)
>> 3) write a handler (to tell your component how it should respond to such
>> events)
>>
>> so, in practice:
>>
>> # 1
>> from nox.netapps.discovery.pylinkevent import Link_event
>> ...
>> # 2
>> def install(self):
>> ...
>> self.register_handler(Link_event.static_get_name(),
>> self.handle_link_event)
>> 
>> # 3
>> def handle_link_event(self, e):
>> print "Received link event:", e.__dict__# this will show you
>> the contents of the event (for example: 'dport': 2, 'dpsrc': 1L, 'dpdst':
>> 2L, 'sport': 2, 'action': 'add')
>> # do something about the event here
>>
>>
>> On Tue, Oct 11, 2011 at 3:17 AM, hzy  wrote:
>>
>>> Hi murphy:
>>>
>>> yes, the results are the same.
>>> the NOX I am using is download from
>>> http://www.openflow.org/wk/index.php/OpenFlow_Tutorial.
>>> Never mind, the thing I concern is that how can i deal with the
>>> link_event in my component.
>>> I think I should look some codes, like core.py or something else,  I just
>>> don't know how to start.
>>> Can you give me some advice?
>>> best regards
>>>
>>> hzy
>>>
>>>
>>> 2011/10/11 Murphy McCauley 
>>>
>>>> I don't know anything about pytutorial (it's not one of the mainlin NOX
>>>> components), so I don't really know what to make of that.
>>>>
>>>> You tried implementing getInterface() like below on your my_router
>>>> class?
>>>> def getInterface (self):
>>>>   return str(my_router)
>>>>
>>>> And the results were the same?
>>>>
>>>> This is unrelated, but you also seem to be using a version of NOX that's
>>>> over a year old.  The destiny branch in particular has many bug fixes.
>>>>
>>>> -- Murphy
>>>>
>>>> On Oct 10, 2011, at 7:40 PM, hzy wrote:
>>>>
>>>> Hi murphy:
>>>>
>>>> Thank you for your reply, but I have added these codes in my component.
>>>> This time I tried to invoke component pytutorial, so that you can get
>>>> more information in your computer.
>>>>
>>>> So I add following codes in discovery component.
>>>> self._pytutorial =
>>>> self.resolve("nox.coreapps.tutorial.pytutorial.pyturorial")
>>>> print self._pytutorial.mac_to_port
>>>>
>>>> 00478|pyrt|ERR:unable to invoke a Python event handler:
>>>> Traceback (most recent call last):
>>>>   File ".

Re: [nox-dev] how to add the components of mobilevms to NOX destiny

[Kyriakos Zarifis]

In your application folder, under src/   (NOT build/src)  , make sure you
have updated the Makefile.am file.
This is where you tell the build system to create links inside the build/
tree to files in your src/ tree. So, for example, you need to change
"meta.xml" to "meta.json" in there.
This is why your build failed until you manually copied the .json into your
build/ tree. Delete it from there, and once you update Makefile.am, and do
./boot.sh again, you'll see that a symbolic link to your meta.json will be
created under build/

This is one of the problems, I'm not sure it's the only one. Try changing
that and start again from ./boot.sh

On Thu, Oct 27, 2011 at 7:13 PM, 王健  wrote:

> hello,everyone.
> Maybe i don't express my problem clearly, so i describe it more
> detailed. I got the source code of  mobilevms compoments(a folder) from
> http://www.openflow.org/wk/index.php/Mobile_VMs for NOX 0.4, now i want to
> transplant them to NOX destiny. The source code of mobilevms compoments is
> beyond 10M, so i can not add it to attachment, sorry for this.
> How can I deal with this problem. For example i need convert the
> meta.xml  to meta.json(anything else to modify?) and copy the mobilevms
> folder to nox/src/nox/netapps directory. This problem has confused me for a
> long time. Anyone who can give me a integral and detailed steps for it.
> Thank you very much, look forward to reply from you even a little bit
> advice~
> best wishes
>
>wang jian
>
>  Friday October 28,2011
>
>
>
>
>
>
>
> --
> 网易公开课推出哈佛最受欢迎《幸福》课程，帮您修满幸福学分!
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to add the components of mobilevms to NOX destiny

[Kyriakos Zarifis]

You shouldn't copy any source code into the build/ directory. Anything that
needs to be there will be created automatically when you build
So only copy the folder you downloaded into nox/src/nox/netapps(delete
it from nox/build/src/nox/netapps)

On Wed, Oct 26, 2011 at 7:41 PM, 王健  wrote:

>  Thank you very much for your help, this is my first time to ask a question
> on NOX,  you give me confidence to finish this experiment.
>I downloaded the source code of nox-0.40-with-mobilevms from
> http://www.openflow.org/wk/index.php/Mobile_VMs. Now i want to use its
> mobilevms code on my NOX(destiny), so i follow the steps on nox website--
> http://noxrepo.org/noxwiki/index.php/Developing_in_NOX.
>First i copy the folder mobilevms in
> nox-0.40-with-mobilevms/src/nox/netapps to the specified
> path(src/nox/netapps) indicated by the website.  But there are two paths,
> one is nox/src/nox/netapps, the other is nox/build/src/nox/netapps. As i do
> not sure which it is, so i copy the folder to both. At then i use the
> meta.json you sended to me to replace the meta.xml. Next step i switch to
> nox directory and run the command:  ./boot.sh
> the terminal shows: automake: cannot open <
> build/src/nox/netapps/mobilevms/../../../Make.vars: no such file or
> directory
> autoreconf: automake failed with exit status: 1
> then i go on and run: cd build/
>../configure
> the terminal shows: config.status: error: cannot find input file:
> `build/src/nox/netapps/mobilevms/wireshark_dissectors/dc_stats/Makefile.in'
> i also go on and run:
> make -j
> it shows:automake-1.11: cannot open <
> build/src/nox/netapps/mobilevms/../../../Make.vars: no such file or
> directory
> make: *** [../Makefile.in] error 1
> I don't know where it is wrong, could you please give me some suggests,
> thank you very very much, look forward to hear form you~
> best wishes
>
>  wang jian
>
> Thursday  October  27, 2011< br>
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Flow expired events in NOX

[Kyriakos Zarifis]

Hi,

are you running 'discovery' or any other application that has discovery as a
dependency?
If so, the packet_ins you see are most probably the control (LLDP) packets
sent by discovery to discover neighbors.
( http://noxrepo.org/noxwiki/index.php/Discovery )

the flow expiration time is set from the controller, when you send the
flow_mods. The flow_mod includes arguments to set hard/idle timeout for the
entry. 'Idle timeout' means the entry will expire X seconds after no
matching traffic has hit the switch, 'hard timeout' means it will expire in
X seconds no matter what.
(Section 5.5.3 in http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf
)

On Thu, Oct 20, 2011 at 1:27 PM, Candy Floss  wrote:

> I have copnnected NOX and two switches. Sometimes when I connect the switch
> to the NOX I see packet_in event in addition to datapath_join event. This is
> happening randomly. Not able to find a pattern when this eaxctly happens but
> it happens most of teh time. I'm not starting any flows but I still see
> packet_in event coming continously. What could be the reason?
>
> And also when I start the flow I see flow expired event on NOX in 1-2 secs.
> Where can I change the default timeout? Do I have to change in NOX or in
> openflow switch?
>
> Thanks & Regards,
> Candy
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] openflow switched nets

[Kyriakos Zarifis]

Yes, that is possible. This is where in-band vs out-of-band control comes to
play: If the physical topology looks exactly like what you described then
control of sw1 can only been done in-band (meaning, the control packets are
using the same links as the data packets). In order for that to be possible,
there need to be some initial flow entries in the intermediate switches to
allow a remote switch to connect to the controller. I don't think there is a
standardized way to set up in-band control, but I am guessing a simple
version would be something like:

- s3 connects to c0
- the controller receives packet_in from s3, which originated in s2 while it
tried to connect
- c0 sets a flow on s3 that allows traffic from s2 to reach it
- at this point s2 and s3 are connected to the controller
- sw2 picks up packet from s1 and sends packet_in to c0

OpenvSwitch has a pretty sophisticated approach to in-band control. If
you're interested you can take a look here :
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=DESIGN
(look for "in-band")

On Thu, Oct 20, 2011 at 5:39 AM, scolfield  wrote:

> Hi,
>
> Thanks for your reply.
> It's possible openflow messages across several switches until achieve the
> controller?
> Such as host -> sw1 -> sw2 -> sw3 -> c0 or in a reverse way in linear
> topology?
> Consider that the host packet need to achieve a server connected to sw3and 
> there are only
> one controller linked to one switch.
>
> --
> scolf
>
>
> On Thu, Oct 20, 2011 at 06:32, Kyriakos Zarifis wrote:
>
>> Hi,
>>
>> pyswitch itself is really not aware of any topology. It only stores state
>> that is relevant to switches separately (i.e. it stores a mapping of mac
>> addresses to local ports for a switch).
>>
>> Now, whether a control packet (like a packet_in) will reach the controller
>> if it's not directly physically connected to it is another issue, and is
>> irrelevant to what NOX application (eg pyswitch) is running. Switches are
>> connected to the controller through a separate control channel, so as long
>> as this channel has been established (which is when the switch first
>> connects to NOX), then the packet_ins will find their way to NOX through
>> that (irrespective of dataplane connectivity, which is established by NOX
>> applications)
>>
>> (another thing to consider is whether the switch-controller connection is
>> in-bound/out-of-bound)
>>
>> Does this make sense?
>>
>> On Wed, Oct 19, 2011 at 5:20 PM, scolfield  wrote:
>>
>>> Hi,
>>>
>>> The pyswitch example can learn topology of networks? Such as a
>>> corporation architecture when
>>> there are hierarchical switches interconnected one to another creating
>>> several "layers" of switches,
>>> at this case, the one openflow controller connected to two distinct
>>> switches, can learn which ports
>>> to send a ping packets, for example?  The packet in messages will be
>>> forwarded automatically through
>>> switches until reach a controller?
>>>
>>> --
>>> scolfield
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] openflow switched nets

[Kyriakos Zarifis]

Hi,

pyswitch itself is really not aware of any topology. It only stores state
that is relevant to switches separately (i.e. it stores a mapping of mac
addresses to local ports for a switch).

Now, whether a control packet (like a packet_in) will reach the controller
if it's not directly physically connected to it is another issue, and is
irrelevant to what NOX application (eg pyswitch) is running. Switches are
connected to the controller through a separate control channel, so as long
as this channel has been established (which is when the switch first
connects to NOX), then the packet_ins will find their way to NOX through
that (irrespective of dataplane connectivity, which is established by NOX
applications)

(another thing to consider is whether the switch-controller connection is
in-bound/out-of-bound)

Does this make sense?

On Wed, Oct 19, 2011 at 5:20 PM, scolfield  wrote:

> Hi,
>
> The pyswitch example can learn topology of networks? Such as a corporation
> architecture when
> there are hierarchical switches interconnected one to another creating
> several "layers" of switches,
> at this case, the one openflow controller connected to two distinct
> switches, can learn which ports
> to send a ping packets, for example?  The packet in messages will be
> forwarded automatically through
> switches until reach a controller?
>
> --
> scolfield
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] (no subject)

[Kyriakos Zarifis]

Hi Ali,

./nox_core -v -i ptcp:myapp
>
>
You need a space between "ptcp:" and "myapp"
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to use discovery component？

[Kyriakos Zarifis]

Hi there,

in order use Link_events in your python component you need to:

1) make your component aware of the Link_event object by importing it
2) register a handler for the event in your component's configure() (to make
your component respond to such events)
3) write a handler (to tell your component how it should respond to such
events)

so, in practice:

# 1
from nox.netapps.discovery.pylinkevent import Link_event
...
# 2
def install(self):
...
self.register_handler(Link_event.static_get_name(),
self.handle_link_event)

# 3
def handle_link_event(self, e):
print "Received link event:", e.__dict__# this will show you the
contents of the event (for example: 'dport': 2, 'dpsrc': 1L, 'dpdst': 2L,
'sport': 2, 'action': 'add')
# do something about the event here


On Tue, Oct 11, 2011 at 3:17 AM, hzy  wrote:

> Hi murphy:
>
> yes, the results are the same.
> the NOX I am using is download from
> http://www.openflow.org/wk/index.php/OpenFlow_Tutorial.
> Never mind, the thing I concern is that how can i deal with the link_event
> in my component.
> I think I should look some codes, like core.py or something else,  I just
> don't know how to start.
> Can you give me some advice?
> best regards
>
> hzy
>
>
> 2011/10/11 Murphy McCauley 
>
>> I don't know anything about pytutorial (it's not one of the mainlin NOX
>> components), so I don't really know what to make of that.
>>
>> You tried implementing getInterface() like below on your my_router class?
>> def getInterface (self):
>>   return str(my_router)
>>
>> And the results were the same?
>>
>> This is unrelated, but you also seem to be using a version of NOX that's
>> over a year old.  The destiny branch in particular has many bug fixes.
>>
>> -- Murphy
>>
>> On Oct 10, 2011, at 7:40 PM, hzy wrote:
>>
>> Hi murphy:
>>
>> Thank you for your reply, but I have added these codes in my component.
>> This time I tried to invoke component pytutorial, so that you can get more
>> information in your computer.
>>
>> So I add following codes in discovery component.
>> self._pytutorial =
>> self.resolve("nox.coreapps.tutorial.pytutorial.pyturorial")
>> print self._pytutorial.mac_to_port
>>
>> 00478|pyrt|ERR:unable to invoke a Python event handler:
>> Traceback (most recent call last):
>>   File "./nox/lib/util.py", line 116, in f
>> event.total_len, buffer_id, packet)
>>   File "./nox/netapps/discovery/discovery.py", line 166, in 
>> discovery.lldp_input_handler(self,dp,inport,reason,len,bid,packet),
>>   File "./nox/netapps/discovery/discovery.py", line 316, in
>> lldp_input_handler
>> print self._pytutorial.mac_to_port
>> AttributeError: 'NoneType' object has no attribute 'mac_to_port'
>>
>> I was confused.
>>
>> In other hand, I accept your advise to handle discovery's Link_even. Since
>> I am a newbie, can you give me some advice how to deal with Link_event in my
>> component?
>>
>> Best regards.
>>
>> hzy
>>
>> 2011/10/10 Murphy McCauley 
>>
>>> Whoops.  I meant:
>>>
>>> def getInterface (self):
>>>   return str(my_router)
>>>
>>> Sorry about that!
>>>
>>> -- Murphy
>>>
>>>
>>> On Oct 10, 2011, at 7:51 AM, Murphy McCauley wrote:
>>>
>>> So first off, maybe you have a reason, but in general, the hope is that
>>> you should have no reason to modify discovery.py.  Rather than modify
>>> discovery.py to explicitly call your component, hopefully you should be able
>>> to simply handle discovery's Link_event.
>>>
>>> If you really do need to modify discovery.py to call your component
>>> explicitly, then as for why your code doesn't work, I don't think I have
>>> enough information to say.  Assuming that your paths are right (you have a
>>> directory/package called my_experiment) and that in my_router.py you have a
>>> class/component called my_router... my best guess is that you didn't
>>> implement getInterface() in my_router in the expected way.  Try adding the
>>> following to your my_router class:
>>>
>>> def getInterface (self):
>>>   return my_router
>>>
>>> Hope that helps.
>>>
>>> -- Murphy
>>>
>>> On Oct 10, 2011, at 6:45 AM, hzy wrote:
>>>
>>> hi murpy:
>>> Thank you for your reply. it works now, but another problem comes up.
>>> This time I want the discovery component invoke the dic_all_path defined
>>> in my modle.
>>>
>>> So I add following codes in discovery component
>>> self._my_router =
>>> self.resolve("nox.coreapps.my_experiment.my_router.my_router")
>>> print self._my_router.dic_all_path
>>>
>>> I also tried these codes
>>> from nox.coreapps.my_experiment import my_router
>>> self._my_router = self.resolve(my_router.my_router
>>> print self._my_router.dic_all_path
>>>
>>> 00206|pyrt|ERR:unable to invoke a Python event handler:
>>> Traceback (most recent call last):
>>>   File "./nox/lib/util.py", line 116, in f
>>> event.total_len, buffer_id, packet)
>>>   File "./nox/netapps/discovery/discovery.py", line 163, in 
>>> discovery.lldp_input_handler(self,dp,inport,

Re: [nox-dev] Multiple Nox with spanning_tree Running the same in the Machine

[Kyriakos Zarifis]

It looks like either the socket was left open from an ungraceful shutdown
last time you ran NOX, or another application happens to be using the port
that jsonmessenger is trying to use.  If I recall, that would be port 2703.

If you run "lsof -i | grep 2703" you should be able to see which application
is using that port. If it is a zombie NOX (or some other program you don't
care about) you can kill it and try rerunning.

Alternatively (if a program you care about is using 2703), you can try to
make jsonmessenger use another different port.
I think the command for that would be "jsonmessenger=tcpport="

On Wed, Sep 28, 2011 at 1:33 PM, Rafael Lopes  wrote:

> When i try to run two nox with the spanning_tree i get this error below.
>
> First: Ok
> openflow@openflowvm:~/nox/build/src$ ./nox_core -v -i ptcp:6634 switch
> spanning_tree routing
> 1|nox|INFO:Starting nox_core
> (/home/openflow/nox/build/src/.libs/lt-nox_core)
> 2|nox|INFO:nox bootstrap complete
>
> Second: Error
> openflow@openflowvm:~/nox/build/src$ ./nox_core -v -i ptcp:6635 switch
> spanning_tree routing
> 1|nox|INFO:Starting nox_core
> (/home/openflow/nox/build/src/.libs/lt-nox_core)
> 2|nox|ERR:Cannot change the state of 'spanning_tree' to INSTALLED:
> 'spanning_tree' has an unmet dependency:
>'jsonmessenger' ran into an error:
>bind: Address already in use
>
> any idea to solve it ?
>
> --
> Rafael Lopes Gomes:
>  - Msc. Candidate in Computer Science at University of Campinas (UNICAMP)
>  - Member of LRC/UNICAMP and GERCOM/UFPA
>  - http://www.lrc.ic.unicamp.br/~rafaellgom
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] NOX & Pronto 3290(2011.08.06)

[Kyriakos Zarifis]

I don't know much about Pronto, but this error is a message from the switch
telling NOX that it couldn't add a flow entry because the flow table was
full. Could that be the case indeed?

2011/9/19 Min-Hyup KANG 

>   Hi, All
>
>
> I'd like to know that it is  compatible between NOX(zaku or destiny) and
> Pronto 3290(2011.08.06 firmware).
>
>
> Currently, I can not operate Simplerouting etc.
>
>
> I don't know exactly why nox is having a below message.
>
> If you have any solution, please let me know.
>
>
> 00175|routeinstaller|DBG:Install flow entry port0007:vlan:pcp:0
> mac84:2b:2b:60:26:6e->84:2b:2b:60:38:03 proto0800
> ip192.168.10.11->192.168.10.10 port8->0 with 1 actions
>
> 00176|openflow-event|ERR:received Openflow error packet from
> dpid=02aa: type=3, code=0, 80 bytes of data
>
> 00177|openflow-event|ERR:received Openflow error packet from
> dpid=02aa: type=3, code=0, 80 bytes of data
>
>
>
>
>
> Best Regards,
> Min-Hyup KANG
>
> 
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Fwd: NOX GUI

[Kyriakos Zarifis]

>
>
> Back to original openflow, when I ping from one VM to another, the GUI
> shows 8 flows in one dot and 0 in the other.. OpenvSwitch works fine,
> showing 2 flows in each dot.
>
>
Weird.. what do these 8 flows look like? Do they make any sense/no sense at
all? Do they have invalid values etc? Also, if you inspect the tables
manually (e.g. dpctl) do they show the right flows or do they show the same?


> Another thing, after some time, the log scrollbar in GUI stops going down.
> It stays in the middle.. Maybe it's a known issue too..
>
>
Right:> I think it's fixed in a local branch, but apparently has not been
pushed
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Fwd: NOX GUI

[Kyriakos Zarifis]

The error message you get when you close the application is a known issue
(it doesn't really affect anything)

You are correct about flowtracer.py. (I didn't remember we had separated the
feature into its own component). Try running that one, I just tested it on
my end.
It won't show anything too meaningful until we figure out why the links are
not drawn. This might require some debugging on your side:
1) First, are you sure there are indeed links there? Have you tried to test
connectivity?
2) If pings etc work, then try to take a look at LAVI's messages to see that
it actually sees the links. (LAVI is the backend that advertises the
topology to the gui).
3) On the gui side, you can add some print statements in "got_topo_msg()" in
the file src/gui/topology.py (around line 755), to make sure that link
advertisement messages are received. I.e. add a "print jsonmsg" and make
sure messages with the field "links" are received.



On Wed, Sep 14, 2011 at 5:04 AM, Lucas Henrique Mauricio <
lhmauri...@poli.ufrj.br> wrote:

> Hello!
>
> I don't have physical access to the computer I'm working on it now but the
> error messages I have are:
> - Something with a qt4 sql library (Solved downloading libqt4-sql-sqlite)
> - When exiting the NOX GUI, it shows an error message telling something
> about it didn't finish a connection (maybe I'm wrong), something will cease
> to work. I don't remember clearly the correct error message. =(
> - When I try to use spanning tree without executing it with nox it gives a
> series of python errors that I think that can be easily solved executing
> spanning_tree.
>
> There is a flowtracer.py but you told me to run sample_routing instead. Is
> it correct?
>
>
>
> 2011/9/13 Murphy McCauley 
>
>> Oh, duh, of course the spanning tree component needs to be running.  Haha,
>> thanks Kyriakos.
>>
>> One more note is that if you run sample_routing, *don't* run pyswitch.
>>
>> -- Murphy
>>
>>
>> On Sep 13, 2011, at 6:15 PM, Kyriakos Zarifis wrote:
>>
>> Hi there,
>>
>> for stp and flowtracer, the respective relevant NOX components need to be
>> running
>> If I recall correctly, the names of these components are 'spanning_tree"
>> and "sample_routing"
>>
>> The haven't been thoroughly tested, but worked fine last time I
>> checked. They won't do much anyway if the links don't show up. Do you get
>> any error messages in the terminal where you started the GUI?
>>
>> On Tue, Sep 13, 2011 at 10:21 PM, Murphy McCauley  wrote:
>>
>>> I had a vague memory about components, so I looked it up.  Maybe this
>>> applies?
>>> http://noxrepo.org/pipermail/nox-dev/2011-August/007951.html
>>>
>>> For links -- did you add "discovery" to your NOX commandline?
>>>
>>> STP and Flowtracer... I am not sure if these are implemented.  You might
>>> take a glance at the code to see if you can tell.  I'm not an expert in the
>>> GUI.  Maybe Kyriakos can jump in here. :)
>>>
>>> -- Murphy
>>>
>>> On Sep 13, 2011, at 9:44 AM, Lucas Henrique Mauricio wrote:
>>>
>>> Hello Murphy.
>>>
>>> You were right about debugging messages as well.. Using -v -v did make
>>> these messages to show up in the GUI.
>>>
>>> But I still have problems with the links and the components..
>>>
>>> STP and Flowtracer are not working as well but maybe I only need to run
>>> some functions with nox, right?
>>>
>>> Thanks
>>>
>>> 2011/9/12 Murphy McCauley 
>>>
>>>> The quick answer about -v -v can be gotten with "./nox_core --help":
>>>>   -v, --verbose   make console log verbose (shows INFO messages
>>>> -- use twice for DBG)
>>>>
>>>> The longer answer is that -v -v puts it into "very verbose" mode.  NOX's
>>>> logging can actually be configured with quite a lot of flexibility through
>>>> several mechanisms, including at runtime... but the GUI doesn't currently
>>>> know anything about that.  In general, you probably DO want all levels of
>>>> log messages to be sent to the GUI so that you can then use the GUI's
>>>> filtering mechanism (which lets you filter them after the fact).  This
>>>> really should be the default for the GUI, and I have a local branch which
>>>> does this, so it's quite possible we'll see it in a future version of NOX.
>>>>
>>>> About

Re: [nox-dev] Fwd: NOX GUI

[Kyriakos Zarifis]

Hi there,

for stp and flowtracer, the respective relevant NOX components need to be
running
If I recall correctly, the names of these components are 'spanning_tree" and
"sample_routing"

The haven't been thoroughly tested, but worked fine last time I
checked. They won't do much anyway if the links don't show up. Do you get
any error messages in the terminal where you started the GUI?

On Tue, Sep 13, 2011 at 10:21 PM, Murphy McCauley  wrote:

> I had a vague memory about components, so I looked it up.  Maybe this
> applies?
> http://noxrepo.org/pipermail/nox-dev/2011-August/007951.html
>
> For links -- did you add "discovery" to your NOX commandline?
>
> STP and Flowtracer... I am not sure if these are implemented.  You might
> take a glance at the code to see if you can tell.  I'm not an expert in the
> GUI.  Maybe Kyriakos can jump in here. :)
>
> -- Murphy
>
> On Sep 13, 2011, at 9:44 AM, Lucas Henrique Mauricio wrote:
>
> Hello Murphy.
>
> You were right about debugging messages as well.. Using -v -v did make
> these messages to show up in the GUI.
>
> But I still have problems with the links and the components..
>
> STP and Flowtracer are not working as well but maybe I only need to run
> some functions with nox, right?
>
> Thanks
>
> 2011/9/12 Murphy McCauley 
>
>> The quick answer about -v -v can be gotten with "./nox_core --help":
>>   -v, --verbose   make console log verbose (shows INFO messages --
>> use twice for DBG)
>>
>> The longer answer is that -v -v puts it into "very verbose" mode.  NOX's
>> logging can actually be configured with quite a lot of flexibility through
>> several mechanisms, including at runtime... but the GUI doesn't currently
>> know anything about that.  In general, you probably DO want all levels of
>> log messages to be sent to the GUI so that you can then use the GUI's
>> filtering mechanism (which lets you filter them after the fact).  This
>> really should be the default for the GUI, and I have a local branch which
>> does this, so it's quite possible we'll see it in a future version of NOX.
>>
>> About the Components section being empty... if I recall correctly (and
>> it's entirely possible that I don't), the Components section is populated by
>> watching the DBG messages about component loading when NOX starts up.  With
>> only one -v, they never get to the GUI.
>>
>> -- Murphy
>>
>> On Sep 12, 2011, at 7:34 PM, Lucas Henrique Mauricio wrote:
>>
>> I figured it out how to solve the missing library. You were right, it's
>> libqt4-sql-sqlite.
>>
>> About this -v -v, what's the point? hehe I'll try tomorrow but I don't
>> understand what it's gonna change.. Could you explain, please?
>>
>> One last thing, what do you think about the fact that components button
>> doesn't show anything?
>>
>> Thanks for your replies!
>>
>> 2011/9/12 Murphy McCauley 
>>
>>> It looks like you're missing Qt's sqlite interface.  Try installing it.
>>>  On Ubuntu I think this is in the libqt4-sql-sqlite package.
>>>
>>> I think to get links to show up, you'll need to run discovery as well,
>>> and you should probably run nox_core with -v -v:
>>> ./nox_core -v -v -i ptcp:2525 monitoring discovery pyswitch
>>>
>>> Hope that helps.
>>>
>>> -- Murphy
>>>
>>> On Sep 12, 2011, at 12:58 PM, Lucas Henrique Mauricio wrote:
>>>
>>> > Hello everybody,
>>> >
>>> > I have NOX running at my host pc and two openvswitch switches running
>>> on two different VirtualBox virtual machines. I created a bridge between the
>>> two VMs and set NOX as controller of this bridge.
>>> >
>>> > At my host, I run "./nox_core -v -i ptcp:2525 monitoring pyswitch" and
>>> "./nox-gui". The NOX GUI shows the two VMs but don't link than, even when I
>>> am pinging one another. When I look at the terminal, I see this:
>>> > root@meier:~/nox/src# ./nox-gui.py
>>> > QSqlDatabase: QSQLITE driver not loaded
>>> > QSqlDatabase: available drivers: QMYSQL3 QMYSQL
>>> > QSqlQuery::exec: database not open
>>> > QSqlQuery::exec: database not open
>>> >
>>> > I think that maybe that's why NOX GUI doesn't show links between
>>> switches and no debugging messages. If I click "component" button, it shows
>>> a list without any components..
>>> >
>>> > What am I doing wrong?
>>> >
>>> > Best regards
>>> >
>>> > -
>>> > Lucas Henrique Mauricio
>>> >
>>> > Universidade Federal do Rio de Janeiro
>>> > Escola Politécnica
>>> > Engenharia Eletrônica e de Computação
>>> > ___
>>> > nox-dev mailing list
>>> > nox-dev@noxrepo.org
>>> > http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>>
>> --
>> Lucas Henrique Mauricio
>>
>> Universidade Federal do Rio de Janeiro
>> Escola Politécnica
>> Engenharia Eletrônica e de Computação
>>
>>
>>
>
>
> --
> Lucas Henrique Mauricio
>
> Universidade Federal do Rio de Janeiro
> Escola Politécnica
> Engenharia Eletrônica e de Computação
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/ma

Re: [nox-dev] Issue about nox-gui.py

[Kyriakos Zarifis]

Hi,

for a temporary resolution, in the file src/gui/log.py , uncomment lines
257-258.
There is a performance issue which has not been resolved, so this feature
was temporarily disabled. When you uncomment this it will work but will also
probably degrade performance.

On Sat, Aug 27, 2011 at 4:16 PM, Chen Gao  wrote:

> Dear All,
>
> ** **
>
> Before I run nox-gui.py, I run 
>
> nox_core –I ptcp: monitoring pyswitch –v –v. 
>
> Then in nox-gui window, the log can be shown. However, when I click
> component, it’s empty. So I try run 
>
> nox_core –I ptcp: monitoring topology discovery pyswitch –v –v
>
> Unfortunately, the component in nox-gui is still empty.
>
> ** **
>
> Could someone tell me how to make running components shown in nox-gui?
> Thanks
>
> ** **
>
> What’s more, about the ENVI, is that I compile it then run enough?
>
> ** **
>
> Thank you 
>
> ** **
>
> Chen
>
> ** **
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Have a openflow interactive component in nox now？

[Kyriakos Zarifis]

Hi,

you are right that a CLI might be helpful, and it is in fact one of the
things that we have in mind as a next feature.
However,  keep in mind that you can already setup flows proactively (before
any packet is received), with NOX programmatically. (e.g. by adding the
relevant code on the datapath_join handler instead of the packet_in
handler). A packet_in is just another event, nothing says that flows should
be added based on that event only.

On Mon, Aug 22, 2011 at 2:32 AM,  wrote:

>
> Hi,
>  I know that the Openvswitch could manage its flowtables by dpctl
> (add/del flows) directly?
>  I want to know there is a similar component to funciton. If it exists,
> I could configure the openflow network more flexible. Such as, setup flows
> before receive a packet from switches. A CLI model is the best, could my
> wish be satisfied?
>  Thank you!
>
>
> Best Regards!
>
>
> 
> ZTE Information Security Notice: The information contained in this mail is 
> solely property of the sender's organization. This mail communication is 
> confidential. Recipients named above are obligated to maintain secrecy and 
> are not permitted to disclose the contents of this communication to others.
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed. If 
> you have received this email in error please notify the originator of the 
> message. Any views expressed in this message are those of the individual 
> sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Nox Sockets

[Kyriakos Zarifis]

Hey,

is the listening socket on the local host? if so, can you try:
self.sock.connect(("localhost",5000))
instead of:
self.sock.connect(("",5000))
?

(I'm not sure I've seen connect take an empty string as an argument for the
host. Do you know that python defaults that to "localhost"?)

On Mon, Aug 15, 2011 at 2:15 PM, chris oleke  wrote:

> Murphy, the thing is I'd pretty much want to maintain the sockets that I'm
> using at the moment since the third party application is tailored to work
> with them. When I send the data from NOX, I have to close the sockets
> because the data won't be received on the other end if the sockets remain
> open. My flow stats are generated every 10 seconds so my aim is to have them
> sent continously. I had previously tried using sock.setblocking(0) but
> encountered an error *"operation already in progress"* so abandoned using
> it.
>
>
> On Sat, Aug 13, 2011 at 2:34 AM, Murphy McCauley  wrote:
>
>> It has been long enough since I've looked at the co-op threading in NOX
>> that I don't immediately know what the problem you're having with the file
>> descriptors going away is.  You're sure you're not calling close() on them?
>>  You could try setting the socket to non-blocking mode with
>> sock.setblocking(0).
>>
>> It might be possible to get asynccore to work, but I think it'd probably
>> be some trouble.  Twisted, on the other hand, should more or less just work.
>>  I think you can probably look at the NOX webservice stuff for a bit of an
>> example, but it shouldn't be much different than any other Twisted code.
>>
>> Or if you would be okay with communicating with the other process via JSON
>> strings, you could use jsonmessenger.  Look in monitoring.py from the
>> monitoring component for an example.
>>
>> Hope that helps.
>>
>> -- Murphy
>>
>> On Aug 12, 2011, at 2:03 PM, chris oleke wrote:
>>
>> Hi
>>
>>
>> Hopefully this is still within the Nox domain. I have a python application
>> that is using sockets to send out flows that I have obtained from a
>> flow_stats_in_event to an application external of Nox. This is how I’m doing
>> it
>> self.sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>> self.sock.connect(("",5000))
>> self.sock.send(repr(flows))
>> self.sock.close()
>>
>> Unfortunately I can only send the flows once before the sockets close
>> after which I get the errors below
>> self.sock.send(repr(flows))
>>   File "/usr/lib/python2.6/socket.py", line 167, in _dummy
>> raise error(EBADF, 'Bad file descriptor')
>> error: [Errno 9] Bad file descriptor
>>
>>
>> It’s obviously as a result of trying to send information out on a socket
>> that’s been closed. I have tried to look at asyncore and see if I can have
>> an asynchronous socket but haven’t had any luck and my application’s seems
>> to lock/freeze the few times I have tried. Is there a way I can have the
>> socket remain connected so I can have flows sent constantly and also be able
>> to receive data when sent from the external application. I would like a
>> demonstration as well if it’s possible.
>>
>>
>> Thanks
>>
>> Chris
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Re : Nox CLI

[Kyriakos Zarifis]

Hi Amar,

there is no CLI for setting up flows through NOX..
In order to do something like that you can use an external tool like dpct or
ovsctl (depending on what kind of switch you are using)

The point of NOX, and any controller, is to do the same thing
programmatically. You install flows by crafting flow_mod packets (in your
code) and sending them to switches. Flow_mod packets are used to
add/modify/remove flow entries on a switch. For adding new flow entries, you
give those flow_mod packets a flow description (match), and the action(s) to
be performed on a packet that arrives on the switch that matches that
description.

If you say your ping goes through, you are probably using a NOX component
that sets up those flow entries. (what kind of switch are you using?)
So you can look at the code of the component you are running to see what it
does to craft those packets and set up flow entries on the switch.
On of the simpler examples of this is in the component "switch" or
"pyswitch"

Hope this helps

On Thu, Aug 11, 2011 at 9:42 PM, amarnath v  wrote:

> Hi Team,
> First of all congrts for developing such a grt controller.
> But i see NOX controller wont support CLI and i tired to work with WEB
> which is not user friendly.
>
> Can you please let me know how to control the flows using NOX.I tired using
> web but it is effecting nox.core.
>
> My topology:
> -
>
> H1  Openflow enabled switch---H2
>  |
>  |
>   NOX Controller
>
> I am doing the ping from H1 to H2 , ping is success and openflow displays
> the flows.
> I captured OFP packets at controller, but now i dont have any idea how to
> set the action for this flows in NOX.
>
>
> Thanks,
> Amar
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Nox on Fedora8

[Kyriakos Zarifis]

Thanks Niky!
If it's ok with you, I'll add your instructions here:
http://noxrepo.org/noxwiki/index.php/Dependencies

On Sun, Jul 24, 2011 at 5:22 AM, Niky Riga  wrote:

> Hi all,
>
> I needed recently to run Nox on PlanetLab hosts running Fedora 8. It took
> me
> a bit to get the process right, so I have written down the steps I
> followed,
> in case others find it useful.
>
> http://groups.geni.net/geni/**wiki/GeniExperimenter/NoxAndF8
>
> I just needed to run the switch controller, so I haven't fully tested that
> all the
> necessary packages are there, for all controllers.
>
> Cheers,
> Niky
>
>
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] A discovery question

[Kyriakos Zarifis]

Exactly, this version is what would make sense to me too :>
(And I also doubt NOX currently does what the page claims)

On Thu, Jul 14, 2011 at 5:50 PM, Murphy McCauley  wrote:

> Okay, I just read that page, and... you're right, that's definitely what it
> says.  It seems to indicate that what it's talking about there is what is
> "currently implemented in Nox's discovery.py".  I think this is false.  I
> won't completely swear to this, but I did just rewrite discovery like two
> weeks ago, so I was all through that code and I am pretty sure there's
> nothing in there that forwards LLDP.  And pyswitch and authenticator both
> bail as soon as they see that the ethertype is 88cc, so neither pyswitch nor
> routing should be forwarding them either.  And, you know, I have never
> actually observed this in Wireshark (not that I have been looking for it!).
>
> I don't immediately see why this would be a good idea anyway.  1) NOX
> doesn't need to forward advertisements to spread its info since it already
> gets it all centrally, 2) OFDP-style advertisements for non-neighbor
> switches would probably be either meaningless or confusing to non-OF
> switches, and 3) doing this would make it much harder to actually figure out
> the direct-neighbor relationships anyway.
>
> So, yeah.  I don't think NOX works exactly how that page describes.  If it
> SHOULD be working that way, hopefully someone will explain why.
>
> What I think that document should actually say to describe how NOX
> presently works is along the lines of:
>
> Switch O (Openflow-enabled) OFDP advertisements out all ports.
> Switch A (not OpenFlow-enabled) will forward the received OFDP
> advertisements out all other ports.
> Switch B (OpenFlow-enabled) will update it's internal connectivity
> information.  Switch B will *not* forward the OFDP advertisement.
>
> That is, only Switch A really changes behavior.  And:
>
> The Take Away
> All Switches in a layer-2 network receive OFDP advertisements from their
> "OpenFlow neighbors" (these may be directly connected OpenFlow switches, or
> they may be the closest OpenFlow switch via one or more intermediate
> non-OpenFlow switches).
> OFDP's EtherType is 0x88cc.
> OFDP advertisements are sent to a "normal" multicast MAC
> (01:23:00:00:00:01).
> OFDP is Advertisement only.
> Non-OpenFlow Switches will forward OFDP advertisements.
> OpenFlow Switches will not forward OFDP advertisements.
>
> -- Murphy
>
> On Jul 14, 2011, at 1:56 PM, Kyriakos Zarifis wrote:
>
> Hm. That was my impression too, but now looking at the doc again, the
> phrase "confused me.
>
>
> 2011/7/14 Murphy McCauley 
>
>> So the normal LLDP multicast address should never be forwarded.  No
>> problem there except that NOX couldn't "see through" intermediate switches
>> there.
>>
>> On the other hand, with the OFDP address... OpenFlow switches still won't
>> forward such messages (NOX looks at them in discovery, but never instructs
>> the switches to forward them).  But non-OF switches will forward them (as
>> far as I understand it, this is the entire point -- so that NOX can "see
>> through" such switches).  So yes, these messages may be broadcast by non-OF
>> hardware on the non-OF portion of their network (always stopping when they
>> hit an OF switch), but it's not actually any worse than any other broadcast
>> like an ARP.  The non-OF portion of the network probably already has to be
>> capable of dealing with broadcasts (via STP or looplessness or whatever) or
>> you have big problems anyway.  Right?
>>
>> -- Murphy
>>
>> On Jul 14, 2011, at 1:29 PM, kk yap wrote:
>>
>> > Oops.. I read the GENI document again, and Murphy is right in that the
>> > multicast address is different here.  My apologies.
>> >
>> > This address will be forwarded by mac bridges though.  Won't this be
>> > risking a broadcast storm?  Am I missing something again?
>> >
>> > Regards
>> > KK
>> >
>> >
>> > On 14 July 2011 13:23, kk yap  wrote:
>> >> I believe OFDP uses LLDP as Kyriakos mentioned.  So, there is no real
>> >> difference here.
>> >>
>> >> As for the question of discovering a "link" between two OpenFlow
>> >> switches connected by a non-OpenFlow switch, the link will be
>> >> discovered if the switch does not process LLDP and thus pass it on.
>> >> Else, the intermediate switch will consume the LLDP packet.
>> >>
>> >> For discovery of on

Re: [nox-dev] A discovery question

[Kyriakos Zarifis]

Hm. That was my impression too, but now looking at the doc again, the phrase
"Switch B (OpenFlow <http://groups.geni.net/geni/wiki/OpenFlow>-enabled)
will update it's internal OFDP table. Switch B will forward the received
OFDP advertisement out all other ports." confused me.

2011/7/14 Murphy McCauley 

> So the normal LLDP multicast address should never be forwarded.  No problem
> there except that NOX couldn't "see through" intermediate switches there.
>
> On the other hand, with the OFDP address... OpenFlow switches still won't
> forward such messages (NOX looks at them in discovery, but never instructs
> the switches to forward them).  But non-OF switches will forward them (as
> far as I understand it, this is the entire point -- so that NOX can "see
> through" such switches).  So yes, these messages may be broadcast by non-OF
> hardware on the non-OF portion of their network (always stopping when they
> hit an OF switch), but it's not actually any worse than any other broadcast
> like an ARP.  The non-OF portion of the network probably already has to be
> capable of dealing with broadcasts (via STP or looplessness or whatever) or
> you have big problems anyway.  Right?
>
> -- Murphy
>
> On Jul 14, 2011, at 1:29 PM, kk yap wrote:
>
> > Oops.. I read the GENI document again, and Murphy is right in that the
> > multicast address is different here.  My apologies.
> >
> > This address will be forwarded by mac bridges though.  Won't this be
> > risking a broadcast storm?  Am I missing something again?
> >
> > Regards
> > KK
> >
> >
> > On 14 July 2011 13:23, kk yap  wrote:
> >> I believe OFDP uses LLDP as Kyriakos mentioned.  So, there is no real
> >> difference here.
> >>
> >> As for the question of discovering a "link" between two OpenFlow
> >> switches connected by a non-OpenFlow switch, the link will be
> >> discovered if the switch does not process LLDP and thus pass it on.
> >> Else, the intermediate switch will consume the LLDP packet.
> >>
> >> For discovery of only OpenFlow switches, it might be best to use a
> >> packet with multicast address (and possibly ethertype) that is
> >> different from LLDP (i.e., 802.11ab).  The change is not hard but note
> >> the consequences.
> >>
> >> Just my two cents worth.
> >>
> >> Regards
> >> KK
> >>
> >> 2011/7/14 Murphy McCauley :
> >>> Right.  Someone correct me if I am wrong here, but really the only
> >>> difference between OFDP and normal LLDP is that OFDP uses a normal
> multicast
> >>> address so that it can see connectivity across non-OpenFlow switches.
> >>> The purpose being... if you have two OpenFlow switches connected via an
> >>> intermediate non-OpenFlow switch, using normal LLDP, you couldn't tell
> that
> >>> the two OpenFlow switches were connected because the intermediate
> switch
> >>> would not forward the LLDP packet.  "OFDP" style LLDP *does* get
> forwarded
> >>> by the intermediate, so you *can* tell that the two OpenFlow switches
> are
> >>> connected.
> >>> -- Murphy
> >>> On Jul 14, 2011, at 1:45 AM, Kyriakos Zarifis wrote:
> >>>
> >>> OFDP is a made-up term used to describe how OF uses LLDP packets to
> perform
> >>> discovery. There is no such thing as an OFDP packet. The packets used
> for
> >>> discovery are LLDP packets.
> >>> On Thu, Jul 14, 2011 at 4:32 AM, wunyuan 
> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> Thanks for your answer.
> >>>>
> >>>> We observe the information from this URL
> >>>> (http://groups.geni.net/geni/wiki/OpenFlowDiscoveryProtocol)
> >>>>
> >>>> this information is that OFDP advertisements are sent to a "normal"
> >>>> multicast MAC (01:23:00:00:00:01), and we find our openflow switch
> send the
> >>>> lldps to this mac.
> >>>>
> >>>> We guess the discovery is the OFDP first.
> >>>>
> >>>> We think our guess may be wrong after we see the discovery.py code.
> >>>>
> >>>> Therefore, we are not sure that the discovery is the LLDP or the OFDP
> now.
> >>>>
> >>>> Bests,
> >>>>
> >>>> Wun-Yuan
> >>>>
> >>>>
> >>>>
> >>>> 於 2

Re: [nox-dev] A discovery question

[Kyriakos Zarifis]

OFDP is a made-up term used to describe how OF uses LLDP packets to perform
discovery. There is no such thing as an OFDP packet. The packets used for
discovery are LLDP packets.

On Thu, Jul 14, 2011 at 4:32 AM, wunyuan  wrote:

> **
> Hi,
>
> Thanks for your answer.
>
> We observe the information from this URL (
> http://groups.geni.net/geni/wiki/OpenFlowDiscoveryProtocol)
>
> this information is that OFDP advertisements are sent to a "normal"
> multicast MAC (01:23:00:00:00:01), and we find our openflow switch send the
> lldps to this mac.
>
> We guess the discovery is the OFDP first.
>
> We think our guess may be wrong after we see the discovery.py code.
>
> Therefore, we are not sure that the discovery is the LLDP or the OFDP now.
>
> Bests,
>
> Wun-Yuan
>
>
>
> 於 2011/7/14 下午 04:03, Kyriakos Zarifis 提到:
>
> Hi,
>
>  I'm not sure if I understand the question, but Discovery uses LLDP
> packets.
> Short description here:
> http://noxrepo.org/noxwiki/index.php/Discovery
>
> On Thu, Jul 14, 2011 at 3:43 AM, wunyuan  wrote:
>
>> Hi,
>>
>> We have a question about the nox discovery.
>>
>> Our NOX version is NOX 0.9.0(zaku) in our openflow enviroment.
>>
>> We monitor a port of a openflow by wireshark, and we observe that the lldp
>> packets are sent to a  multicast MAC (01:23:00:00:00:01).
>>
>> However we see the discovery.py code and find that  it isn't like the
>> OFDP.
>>
>> We also monitor the ports of the other OF switch not directly-connected
>> above openflow switches, but we only see the lldp packets sent by itself and
>> the lldp packets receviced from neighbor.
>>
>> The discovery seem the LLDP.
>>
>> Which one is the discovery, the LLDP or OFDP?
>>
>> Thanks.
>>
>> Wun-Yuan
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] A discovery question

[Kyriakos Zarifis]

Hi,

I'm not sure if I understand the question, but Discovery uses LLDP packets.
Short description here:
http://noxrepo.org/noxwiki/index.php/Discovery

On Thu, Jul 14, 2011 at 3:43 AM, wunyuan  wrote:

> Hi,
>
> We have a question about the nox discovery.
>
> Our NOX version is NOX 0.9.0(zaku) in our openflow enviroment.
>
> We monitor a port of a openflow by wireshark, and we observe that the lldp
> packets are sent to a  multicast MAC (01:23:00:00:00:01).
>
> However we see the discovery.py code and find that  it isn't like the OFDP.
>
> We also monitor the ports of the other OF switch not directly-connected
> above openflow switches, but we only see the lldp packets sent by itself and
> the lldp packets receviced from neighbor.
>
> The discovery seem the LLDP.
>
> Which one is the discovery, the LLDP or OFDP?
>
> Thanks.
>
> Wun-Yuan
> __**_
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/**listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Bandwidth Measurement.

[Kyriakos Zarifis]

Hi,

I think the closest thing that openflow can provide would be information
about how many bytes have been sent on one side and received on the other
side of a link.
So you could infer an approximation of active rates on the link by polling 2
neighboring switches from NOX at some regular intervals.
This can not be very accurate because there are factors like
round-trip-times for the requests/replies from NOX to the 2 switches and
back, these times will be different, also there are packets travelling
between the switches that should be taken into account etc.
But this is definitely a place to start if you want to do such measurements
from NOX.

The "monitoring" component on the destiny branch (netapps/monitoring) does
something like that (it regularly polls all switches for all kinds of
statistics), so it's a good place to look at.

2011/6/29 Min-Hyup KANG 

>   Hi,
>
>
> I would like to measure bandwidth between switches.
>
>
> I am reading openflow spec 1.0, but there are not existing exactly.
>
>
> please can you give me some tips ?
>
>
>
> Best Regards,
> Min-Hyup KANG
>
> 
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] What's wrong? "00001|nox|ERR:Application 'spanning_tree' description not found"

[Kyriakos Zarifis]

By the way, the spanning_tree module has been added in the destiny branch
(ported to use json), so if you pull from destiny it should just work.

to switch to destiny, follow the instructions here:
http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation
(after "git branch -a")

On Wed, Jun 29, 2011 at 3:02 AM, Murphy McCauley  wrote:

> I assume you're using NOX destiny or zaku (these are the two current
> branches
> of NOX).  These branches now use a meta.json file to describe components.
>  The
> spanning tree component was written for an older version of NOX that used a
> meta.xml file.
>
> As far as I can remember, the spanning tree component still works fine --
> you
> just need to convert the meta file.  The nox-convert-meta.py script (in
> src/scripts) is meant for doing this.  You can run it yourself, but I have
> attached its output here as well.
>
> So put the meta.json in the spanning tree directory, and modify Makefile.am
> to
> refer to meta.json instead of meta.xml.  Then run boot.sh, configure, and
> make
> again... hopefully that'll do it!  (As a shortcut, you could try just
> putting
> meta.json in the spanning_tree directory in your build tree.  I think
> that'll
> work too.)
>
> As a sidenote: you mention setting up an STP network, but the spanning tree
> component *does not* implement STP.  It creates a spanning tree entirely
> within the controller and the switches by using OpenFlow.
>
> Hope this helps.
>
> -- Murphy
>
> On Wednesday, June 29, 2011 02:39:44 AM hu.yongsh...@zte.com.cn wrote:
> > Hi,
> > I'm a beginner of Openflow, and want to setup a STP network based on
> > OpenvSwtich and NOX.
> > I compile the spanning_tree module by the instruction of
> > 'http://www.openflow.org/wk/index.php/Basic_Spanning_Tree#Installation'.
> > Compiling success, but when excute command with spanning_tree, there is
> > error like
> >
> > 1|nox|ERR:Application 'spanning_tree' description not found
> >
> > What's wrong? Anybody met this error, pls give me help. thk
> >
> > Best Regards!
> >
> >
> > 
> > ZTE Information Security Notice: The information contained in this mail
> is
> > solely property of the sender's organization. This mail communication is
> > confidential. Recipients named above are obligated to maintain secrecy
> and
> > are not permitted to disclose the contents of this communication to
> > others. This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they are
> > addressed. If you have received this email in error please notify the
> > originator of the message. Any views expressed in this message are those
> > of the individual sender. This message has been scanned for viruses and
> > Spam by ZTE Anti-Spam system.
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] 答复: Error in running ./nox-gui.py

[Kyriakos Zarifis]

By the way, a segfault does occur when you *exit* the program.. It's
something silly that I have to look into at some point, but it doesn't
affect the functionality. Not that I have noticed at least. Is that when you
get it, or does it happen immediately when you run it?


2011/6/28 Murphy McCauley 

> My main system these days is Kubuntu 11.04 ("natty"), so I mostly test with
> what's in there (which should be quite recent).  You should be able to find
> versions for these packages by searching on the Ubuntu packages site:
> http://packages.ubuntu.com/
>
> I routinely build and use NOX from the head of destiny.  The following
> should
> always pull a tarball of this:
> http://noxrepo.org/
> cgi-bin/gitweb.cgi?p=nox;a=snapshot;h=refs/heads/destiny;sf=tgz
>
> Hope that helps.
>
> -- Murphy
>
> On Tuesday, June 28, 2011 08:12:45 PM Tinny Zhu(Mingming) wrote:
> > Thank you for your help. I find it's the version problem of PyQt4. I have
> > to update PyQt4 from 4.4.2 to 4.8.4, and install SIP-4.12.3,
> > libqt4_dev_4.4.3, and the NOX destiny branch is the latest. But when I
> run
> > ./nox-gui.py , the segment fault is happened. It must be still version
> > problem. Who can tell me which the version you are running? Because my
> > Linux cannot connect to internet for 'git'.
> >
> > Thanks
> >Tinny
> >
> > -邮件原件-
> > 发件人: Murphy McCauley [mailto:jam...@nau.edu]
> > 发送时间: 2011年6月27日 15:24
> > 收件人: nox-dev@noxrepo.org
> > 抄送: Tinny Zhu(Mingming); Xiayinben
> > 主题: Re: [nox-dev] Error in running ./nox-gui.py
> >
> > What distribution are you using?
> >
> > You might try changing "QtCore.pyqtSignal(str)" to "QtCore.Signal(str)".
> >
> > -- Murphy
> >
> > On Monday, June 27, 2011 12:14:44 AM Tinny Zhu(Mingming) wrote:
> > > When I input './nox-gui.py', the following error is happened.
> > >
> > >   Traceback (most recent call last):
> > > File "./nox-gui.py", line 20 , in 
> > >
> > >import gui.log as log
> > >
> > > File "/home/nox0.9gui/nox/src/src/gui/log.py", line 9, in 
> > >
> > >   from communication import LoggerInterface, LogHandler
> > >
> > > File "/home/nox0.9gui/nox/src/src/gui/communication.py", line 59, in
> > >  class TopologyInterface (QtCore.QThread, QtGui.QWidget):
> > > File "/home/nox0.9gui/nox/src/src/gui/communication.py", line 82, in
> > > TopologyInterface monitoring_received_signal = QtCore.pyqtSignal(str)
> > > AttributeError: 'module" object has no attribute 'pyqtSignal'
> > >
> > >Thanks
> > >
> > > Tinny
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] gathering status of Openflow Switch

[Kyriakos Zarifis]

Hi,

you are probably using the branch of the repository and not destiny. Take a
look at the first reply above, which explains that the monitoring component
is only on the Destiny branch, and how to get it.

(Using Destiny is suggested at this point, as it is more up-to-date version
of nox with several bug fixes and features. In any case, the example code in
"monitor" which you already looked at probably answers your question.)

2011/6/19 Min-Hyup KANG 

>   Thanks for your kindness.
>
>
> But there is not exsisting monitoring.py of netapps/
>
> so there is existing some derectory in netapps as a below.
>
>
> """"
>
> src/nox/netapps# ls
>
> Makefile.am  __init__.pybindings_storage  discovery hoststate
>  networkstate  routing  switch_management  tablog  topology
>
> Makefile.in  authenticator  data  flow_fetcher  lavi
> route storage  switchstatstests   user_event_log
>
> """"
>
>
> additionally, I re-write some code(0xfff) in monitor.py refering mail.
> as a below,
>
>
> """
>
> def aggregate_timer(self, dpid):
>
> flow = ofp_match()
>
> #flow.wildcards = 0x
>
> flow.wildcards = 0x
>
> self.ctxt.send_aggregate_stats_request(dpid, flow,  0xff)
>
> self.post_callback(MONITOR_TABLE_PERIOD, lambda :
> self.aggregate_timer(dpid))
> """
>
> 1.What does 0xfff mean ?
> and then, I re-run command.
>
> So, I can check below message.
> 00086|openflow-event|DBG:received stats reply from 002320c2f7b4
> Aggregate stats in from datapath 00:23:20:c2:f7:b4
> {'packet_cout' : 39L, 'byte_cout' : 3822L, 'flow_count':2L }
>
>
>
> - 원본 메일 -
>
> *보낸사람*: Kyriakos Zarifis 
> *받는사람* : Min-Hyup KANG 
> *참조* : nox-dev@noxrepo.org
> *날짜*: 2011년 6월 20일 월요일, 15시 34분 01초 +0900
> *제목*: Re: [nox-dev] gathering status of Openflow Switch
> Hi,
>
> I was actually referring to netapps/monitoring/montoring.py, which is a
> more complete (and complicated) monitoring component, but it is the same
> idea. However the one you looked at might actually be a better example
> exactly because it is simpler, but still shows how to create and send switch
> query packets.
> The output you pasted looks okay
>
>
> 2011/6/19 Min-Hyup KANG 
> http://hanmail/mail/MailComposeFrame.daum?TO=kang-min-h...@hanmail.net>
> >
>
>>   Hi,
>>
>>
>> after I found monitoring.py,
>>
>> There is existing /src/nox/coreapps/examples/monitor.py.
>>
>> I think what you mean is /src/nox/coreapps/examples/monitor.py. right ?
>>
>>
>> so, I excuted monitor component.
>>
>>
>> I can check Table stats and Port stats, Aggregate stats as a below.
>>
>>
>> 00072|openflow-event|DBG:received stats reply from 002320ca92e0
>>
>> Table stats in from datapath 00:23:20:ca:92:e0
>>
>> hash2 : 0
>>
>> linear : 2
>>
>> 00073|openflow-event|DBG:received stats reply from 002320ca92e0
>>
>> Port stats in from datapath 00:23:20:ca:92:e0
>>
>> 1 : 4
>>
>> 2 : 4
>>
>> 00074|openflow-event|DBG:received stats reply from 002320ca92e0
>>
>> Aggregate stats in from datapath 00:23:20:ca:92:e0
>>
>> {'packet_count': 0L, 'byte_count': 0L, 'flow_count': 0L}
>>
>>
>>
>>
>> - 원본 메일 -
>>
>> *보낸사람*: Kyriakos Zarifis 
>> http://hanmail/mail/MailComposeFrame.daum?TO=kyr.zari...@gmail.com>
>> >
>> *받는사람* : Min-Hyup KANG 
>> http://hanmail/mail/MailComposeFrame.daum?TO=kang-min-h...@hanmail.net>
>> >
>> *참조* : 
>> nox-dev@noxrepo.org<http://hanmail/mail/MailComposeFrame.daum?TO=nox-dev@noxrepo.org>
>> *날짜*: 2011년 6월 20일 월요일, 00시 35분 26초 +0900
>>
>> *제목*: Re: [nox-dev] gathering status of Openflow Switch
>>  Hi,
>>
>> the 'monitoring' component I was referring to, is under:
>> ** / src / nox / netapps / monitoring / monitoring.py**
>>
>> but on the Destiny branch of the repository (not Zaku which is the master
>> branch).
>> Follow the instructions here
>> http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation (where
>> it says "For a branch other than master"...)
>> to switch to Destiny.
>>
>>>  -> you mean pyswitch can gather status of flow, port  in switch, right
>>> ?
>>>
>>> and I think I should use  ofp_stats_request, ofp_stats_reply,
>>> ofp_desc_stats, ofp_port_stats_request, ofp_ports_stats etc of struct in
>>> openflow.h and core.py
>>>
>>
>> Exactly. You can see some example of how to build some messages in
>> 'monitoring.py'
>>
>>
>>
>>
>>
>>
>>
>> Best Regards,
>> Min-Hyup KANG
>>
>> <http://hanmail/mail/MailComposeFrame.daum?TO=kang-min-h...@hanmail.net>
>>
>
>
>
>
>
>
>
> Best Regards,
> Min-Hyup KANG
>
> 
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] gathering status of Openflow Switch

[Kyriakos Zarifis]

Hi,

I was actually referring to netapps/monitoring/montoring.py, which is a more
complete (and complicated) monitoring component, but it is the same idea.
However the one you looked at might actually be a better example exactly
because it is simpler, but still shows how to create and send switch query
packets.
The output you pasted looks okay


2011/6/19 Min-Hyup KANG 

>   Hi,
>
>
> after I found monitoring.py,
>
> There is existing /src/nox/coreapps/examples/monitor.py.
>
> I think what you mean is /src/nox/coreapps/examples/monitor.py. right ?
>
>
> so, I excuted monitor component.
>
>
> I can check Table stats and Port stats, Aggregate stats as a below.
>
>
> 00072|openflow-event|DBG:received stats reply from 002320ca92e0
>
> Table stats in from datapath 00:23:20:ca:92:e0
>
> hash2 : 0
>
> linear : 2
>
> 00073|openflow-event|DBG:received stats reply from 002320ca92e0
>
> Port stats in from datapath 00:23:20:ca:92:e0
>
> 1 : 4
>
> 2 : 4
>
> 00074|openflow-event|DBG:received stats reply from 002320ca92e0
>
> Aggregate stats in from datapath 00:23:20:ca:92:e0
>
> {'packet_count': 0L, 'byte_count': 0L, 'flow_count': 0L}
>
>
>
>
> - 원본 메일 -
>
> *보낸사람*: Kyriakos Zarifis 
> *받는사람* : Min-Hyup KANG 
> *참조* : nox-dev@noxrepo.org
> *날짜*: 2011년 6월 20일 월요일, 00시 35분 26초 +0900
>
> *제목*: Re: [nox-dev] gathering status of Openflow Switch
> Hi,
>
> the 'monitoring' component I was referring to, is under:
> ** / src / nox / netapps / monitoring / monitoring.py**
>
> but on the Destiny branch of the repository (not Zaku which is the master
> branch).
> Follow the instructions here
> http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation (where
> it says "For a branch other than master"...)
> to switch to Destiny.
>
>>  -> you mean pyswitch can gather status of flow, port  in switch, right ?
>>
>> and I think I should use  ofp_stats_request, ofp_stats_reply,
>> ofp_desc_stats, ofp_port_stats_request, ofp_ports_stats etc of struct in
>> openflow.h and core.py
>>
>
> Exactly. You can see some example of how to build some messages in
> 'monitoring.py'
>
>
>
>
>
>
>
> Best Regards,
> Min-Hyup KANG
>
> 
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] gathering status of Openflow Switch

[Kyriakos Zarifis]

Hi,

the 'monitoring' component I was referring to, is under:
 / src / nox / netapps / monitoring / monitoring.py

but on the Destiny branch of the repository (not Zaku which is the master
branch).
Follow the instructions here
http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation (where it
says "For a branch other than master"...)
to switch to Destiny.

> -> you mean pyswitch can gather status of flow, port  in switch, right ?
>
> and I think I should use  ofp_stats_request, ofp_stats_reply,
> ofp_desc_stats, ofp_port_stats_request, ofp_ports_stats etc of struct in
> openflow.h and core.py
>

Exactly. You can see some example of how to build some messages in
'monitoring.py'
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] gathering status of Openflow Switch

[Kyriakos Zarifis]

Hi,

no, pyswitch does not show information about establish flows. You need to
write a component that does that by sending query packets from NOX to the
switch. (or, if you prefer, you can modify pyswitch to send such queries)
You can look at the 'monitoring' component in the netapps folder, which
gather statistics from switches, as an example for how to construct and send
such query packets. From what I can tell, you are mostly interested in the
"flow_stats" message

2011/6/18 Min-Hyup KANG 

>   Hi. all
>
>
> I would like to gather through pyswitch.py a little status information of
> flow in Openflow Switch(v.10)
>
>
> I think I should use Openflow protocol that can gather their some status of
> flow between OpenflowSwitch and NOX controller.
>
>
> so Is it possible with pyswitch.py ?
>
>
> or Should I write a new C++ component ?
>
>
> Thanks,
>
>
>
> Best Regards,
> Min-Hyup KANG
>
> 
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Res: Issues in Ubuntu 10.04 with boost_filesystem-mt

[Kyriakos Zarifis]

According to http://noxrepo.org/noxwiki/index.php/Dependencies ,
I think the one one that was missing specifically, was libboost-test-dev


On Tue, Jun 14, 2011 at 2:39 PM, fernando farias wrote:

> you also can to try libboost-all-dev !
>
> Fernando N. N. Farias
>
> Electrical Engineer PhD. Student
> Member of the Research Group on Computer Networks and Multimedia
> Communications - GERCOM/UFPA
> Optical Research Team - GERCOM
> Federal University of Pará
>
>
>
>
> "Primeiro eles o ignoram.
> Depois, riem de você.
> Chega um ponto em que lutam contra voce.
> Ate o dia em que você vence." Gandhi
>
>
> --
> *De:* Srini Seetharaman 
> *Para:* nox-dev 
> *Enviadas:* Terça-feira, 14 de Junho de 2011 18:25:47
> *Assunto:* [nox-dev] Issues in Ubuntu 10.04 with boost_filesystem-mt
>
> Hi
> I am trying to compile the latest head of NOX-Zaku on an Ubuntu 10.04
> machine. I didn't receive any errors when I ran boot.sh. But, when I
> ran configure, I got the following error:
>
> checking whether the Boost::UnitTestFramework library is available... yes
> configure: error: Could not link against boost_filesystem-mt !
>
> I don't see any solution for others that have faced similar issues in
> the past. Do I need to run configure with additional command-line
> options or should I be installing any other package?
>
> Thanks
> Srini.
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Installing a flow using Nox onto a Openflow Switch

[Kyriakos Zarifis]

Hey,

I'm actually not sure that there's a general model, it depends a lot on
_when_ you want to install flows. NOX is essentially an event programming
platform, meaning that it will typically do things when other things happen:
It will generally edit flows when a signal is sent from the network. (or
maybe when a timer expires, but technically it's the same, as the timer
would be triggered by a similar network event). Such events could be
connections from new switches, link state changes, new traffic arrival
(packet_in), etc.

If you want to edit flow tables manually, in real time and at random times,
not triggered by such events, then a tool like dpctl/ofctl might make more
sense.

You *could* write a NOX component that gets external input (through
messenger and/or the console.py script, or the GUI), which would make the
component run a bit of code. It's basically the same principle, you'd be
'injecting' a custom event to NOX, and it's handler would install the flow
you want. But this might be a bit more complicated and not worth the effort,
if all you need is to install a flow entry, which you can do with ofctl. If
you want to share your goal in more detail maybe I could think of a more
specific answer

On Thu, Jun 2, 2011 at 12:57 PM, Balaji Venkataraman wrote:

> Thanks for your reply, can you please share with us any links or working
> model of such an application. It will be very useful to understand how to
> develop this and use it.
>
> Thanks and Regards,
> Balaji
>
>
> On Thu, Jun 2, 2011 at 12:17 PM, Kyriakos Zarifis 
> wrote:
>
>> Hi,
>>
>> NOX does not currently have a command line or a way to manage flow tables
>> non-programmatically. (However, it is something worth considering for the
>> future, as it looks like a few people have expressed interest in something
>> like that. It can be a command line or a more interactive way through the
>> GUI.)
>>
>> For now, you'd have to write your own application like you said  (or use
>> ofctl)
>>
>>
>> On Thu, Jun 2, 2011 at 12:09 PM, Balaji Venkataraman 
>> wrote:
>>
>>> I was about to ask the same question, I'm using openvswitch and able to
>>> apply flows using ovs-ofctl from command line in the switch environment. How
>>> can one do the same from the NOX? Do we need to write our own application
>>> for using openflow or does NOX have any way of configuring the flow to the
>>> switch?
>>>
>>> Thanks and Regards,
>>> Balaji
>>>
>>>
>>> On Thu, Jun 2, 2011 at 11:23 AM, Kyriakos Zarifis >> > wrote:
>>>
>>>> If you want to proactively install flow entries a reasonable place to
>>>> put the code that does it might be the handler of datapath_join, in your
>>>> component. This code runs when a new switch connects to NOX, and the
>>>> switch's information is passed to the handler through the event.
>>>>
>>>> If that doesn't work for want you want to do, maybe you can describe
>>>> when exactly you want to install flows
>>>>
>>>>
>>>> On Thu, Jun 2, 2011 at 11:05 AM, kashyap TA wrote:
>>>>
>>>>> Hi All,
>>>>> Yes, I tried doing a component, but there is one problem. As
>>>>> long as I understand the python component, it get a data packet and from
>>>>> that it get some info and then progemas a flow.
>>>>>
>>>>> In my case, All I need to do it program a flow in the switch using the
>>>>> NOX where I say if it is from a particular port say "portA" with a mac
>>>>> address"ab:cd:de:ef" and vlan "10" then forward it to "portB" on else 
>>>>> flood
>>>>> to all the ports. I am not sure we can just install flows into the box 
>>>>> with
>>>>> out getting a datat packet. The swith is a openflow hardware enabled 
>>>>> switch.
>>>>>
>>>>>
>>>>> Please let me know. If anybody has a sample flow it would be great.
>>>>> Please do let me know.
>>>>>
>>>>> Thanks and Regards
>>>>> Kashyap
>>>>> On Thu, May 26, 2011 at 4:41 PM, Baohua Yang wrote:
>>>>>
>>>>>> NOX doesn't provide a CLI, so you might have to write a APP to setup
>>>>>> your routing rules.
>>>>>> See here for more information of how to write a simple APP.
>>>>>> http://noxrepo.org/noxwiki/
>>>>>>
&g

Re: [nox-dev] Installing a flow using Nox onto a Openflow Switch

[Kyriakos Zarifis]

Hi,

NOX does not currently have a command line or a way to manage flow tables
non-programmatically. (However, it is something worth considering for the
future, as it looks like a few people have expressed interest in something
like that. It can be a command line or a more interactive way through the
GUI.)

For now, you'd have to write your own application like you said  (or use
ofctl)

On Thu, Jun 2, 2011 at 12:09 PM, Balaji Venkataraman wrote:

> I was about to ask the same question, I'm using openvswitch and able to
> apply flows using ovs-ofctl from command line in the switch environment. How
> can one do the same from the NOX? Do we need to write our own application
> for using openflow or does NOX have any way of configuring the flow to the
> switch?
>
> Thanks and Regards,
> Balaji
>
>
> On Thu, Jun 2, 2011 at 11:23 AM, Kyriakos Zarifis 
> wrote:
>
>> If you want to proactively install flow entries a reasonable place to put
>> the code that does it might be the handler of datapath_join, in your
>> component. This code runs when a new switch connects to NOX, and the
>> switch's information is passed to the handler through the event.
>>
>> If that doesn't work for want you want to do, maybe you can describe when
>> exactly you want to install flows
>>
>>
>> On Thu, Jun 2, 2011 at 11:05 AM, kashyap TA  wrote:
>>
>>> Hi All,
>>> Yes, I tried doing a component, but there is one problem. As long
>>> as I understand the python component, it get a data packet and from that it
>>> get some info and then progemas a flow.
>>>
>>> In my case, All I need to do it program a flow in the switch using the
>>> NOX where I say if it is from a particular port say "portA" with a mac
>>> address"ab:cd:de:ef" and vlan "10" then forward it to "portB" on else flood
>>> to all the ports. I am not sure we can just install flows into the box with
>>> out getting a datat packet. The swith is a openflow hardware enabled switch.
>>>
>>>
>>> Please let me know. If anybody has a sample flow it would be great.
>>> Please do let me know.
>>>
>>> Thanks and Regards
>>> Kashyap
>>> On Thu, May 26, 2011 at 4:41 PM, Baohua Yang wrote:
>>>
>>>> NOX doesn't provide a CLI, so you might have to write a APP to setup
>>>> your routing rules.
>>>> See here for more information of how to write a simple APP.
>>>> http://noxrepo.org/noxwiki/
>>>>
>>>>  On Thu, May 26, 2011 at 1:09 PM, kashyap TA wrote:
>>>>
>>>>>  Hi,
>>>>>I am running nox on my linux machine and I have a openflow enabled
>>>>> hardware switch. I am able to initiate a connection between the Nox
>>>>> Controller and the hardware switch. I need to push some flows on to the
>>>>> Switch from the NOX controller. Can I do that? and if so how ? I am not 
>>>>> able
>>>>> to find any help guide. I am new to Nox controller. Can some body help.
>>>>>
>>>>> I just need to push a flow which says, if the packet comes from a
>>>>> particular port, push it out on a particular port.
>>>>>
>>>>>
>>>>> Please do let me know.
>>>>>
>>>>>
>>>>> Thanks and Regards
>>>>> Kashyap
>>>>>  ___
>>>>> nox-dev mailing list
>>>>> nox-dev@noxrepo.org
>>>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Best wishes!
>>>> Baohua
>>>>
>>>>
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Installing a flow using Nox onto a Openflow Switch

[Kyriakos Zarifis]

If you want to proactively install flow entries a reasonable place to put
the code that does it might be the handler of datapath_join, in your
component. This code runs when a new switch connects to NOX, and the
switch's information is passed to the handler through the event.

If that doesn't work for want you want to do, maybe you can describe when
exactly you want to install flows

On Thu, Jun 2, 2011 at 11:05 AM, kashyap TA  wrote:

> Hi All,
> Yes, I tried doing a component, but there is one problem. As long
> as I understand the python component, it get a data packet and from that it
> get some info and then progemas a flow.
>
> In my case, All I need to do it program a flow in the switch using the NOX
> where I say if it is from a particular port say "portA" with a mac
> address"ab:cd:de:ef" and vlan "10" then forward it to "portB" on else flood
> to all the ports. I am not sure we can just install flows into the box with
> out getting a datat packet. The swith is a openflow hardware enabled switch.
>
>
> Please let me know. If anybody has a sample flow it would be great. Please
> do let me know.
>
> Thanks and Regards
> Kashyap
> On Thu, May 26, 2011 at 4:41 PM, Baohua Yang  wrote:
>
>> NOX doesn't provide a CLI, so you might have to write a APP to setup your
>> routing rules.
>> See here for more information of how to write a simple APP.
>> http://noxrepo.org/noxwiki/
>>
>>  On Thu, May 26, 2011 at 1:09 PM, kashyap TA wrote:
>>
>>>  Hi,
>>>I am running nox on my linux machine and I have a openflow enabled
>>> hardware switch. I am able to initiate a connection between the Nox
>>> Controller and the hardware switch. I need to push some flows on to the
>>> Switch from the NOX controller. Can I do that? and if so how ? I am not able
>>> to find any help guide. I am new to Nox controller. Can some body help.
>>>
>>> I just need to push a flow which says, if the packet comes from a
>>> particular port, push it out on a particular port.
>>>
>>>
>>> Please do let me know.
>>>
>>>
>>> Thanks and Regards
>>> Kashyap
>>>  ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>>
>> --
>> Best wishes!
>> Baohua
>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Cannot find "nox-gui.py"

[Kyriakos Zarifis]

That's right, the message was showing because NOX needs to be running with
the monitoring component for the GUI to function, and it worked because that
component is in sample_routing's component dependency chain

On Thu, Jun 2, 2011 at 10:03 AM, andrea simeoni
wrote:

> I solved the problem by running the following
>
> ./nox-gui -p 6633
> ./nox_core -i ptcp:6633 sample_routing
>
> Now everything seems being working :)
>
> 2011/6/2 andrea simeoni 
>
>> Thank you for answering Kyriakos,
>>
>> I got the Destiny branch and can see now the script and Gui folder.
>> A this point I start NOX with a random component and setup a Mininet
>> network controlled by NOX;
>> now the command "./nox-gui.py"   outputs the following:
>>
>> Retrying connection to NOX...
>> Retrying connection to NOX...
>> Retrying connection to NOX...
>> ..
>>
>> What is the problem?  I also tried to specify my localhost ip address
>>
>> Can you help me?
>>
>>
>>
>> 2011/6/2 Kyriakos Zarifis 
>>
>>> Hey Andrea,
>>>
>>> the gui is currently only available on the Destiny branch, not Zaku.
>>>
>>> If you're interested in grabbing the code from Destiny:
>>> http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation
>>>
>>> On Thu, Jun 2, 2011 at 2:02 AM, andrea simeoni <
>>> andreasimeon...@gmail.com> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I've recently installed "NOX 0.9.0 zaku", and I'm looking for the
>>>> "nox-guy.py" file.
>>>> The noxrepo page says it' s under the /src folder, but there is nothing.
>>>> Maibe the gui is not available in my NOX release?
>>>>
>>>> Any suggestions?
>>>>
>>>> Best regards
>>>>
>>>> --
>>>> Andrea Simeoni
>>>>
>>>> ___
>>>> nox-dev mailing list
>>>> nox-dev@noxrepo.org
>>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>>
>>>>
>>>
>>
>>
>> --
>> Andrea Simeoni
>>
>
>
>
> --
> Andrea Simeoni
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Cannot find "nox-gui.py"

[Kyriakos Zarifis]

Hey Andrea,

the gui is currently only available on the Destiny branch, not Zaku.

If you're interested in grabbing the code from Destiny:
http://noxrepo.org/noxwiki/index.php/NOX_Installation#Installation

On Thu, Jun 2, 2011 at 2:02 AM, andrea simeoni wrote:

> Hi guys,
>
> I've recently installed "NOX 0.9.0 zaku", and I'm looking for the
> "nox-guy.py" file.
> The noxrepo page says it' s under the /src folder, but there is nothing.
> Maibe the gui is not available in my NOX release?
>
> Any suggestions?
>
> Best regards
>
> --
> Andrea Simeoni
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] problem in installation in NOX

[Kyriakos Zarifis]

Hey Ahmad,

the executable will be in the build directory  (nox/build/src/)

On Wed, Jun 1, 2011 at 6:14 AM, ahmad numan  wrote:

> I am trying to install NOX on Linux powered Octeon board. I am able to
> successfully configure and build the NOX but after building there is no
> nox_core in /nox/src directory. I have tried many times but cannot get
> nox_core in /nox/src directory. How can i use it as controller to openflow
> switch?
> Thanks
>
> Ahmed Bilal
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Installing a flow using Nox onto a Openflow Switch

[Kyriakos Zarifis]

Hi there,

yes, you can edit the flow table programmatically from NOX
please take a look at this:
http://noxrepo.org/noxwiki/index.php/FAQ#How_can_I_edit_the_flow_table_of_a_switch.3F

and also the rest of the info on the wiki should be useful.
Let us know if this helps or you have more questions.

On Thu, May 26, 2011 at 1:09 PM, kashyap TA  wrote:

> Hi,
>I am running nox on my linux machine and I have a openflow enabled
> hardware switch. I am able to initiate a connection between the Nox
> Controller and the hardware switch. I need to push some flows on to the
> Switch from the NOX controller. Can I do that? and if so how ? I am not able
> to find any help guide. I am new to Nox controller. Can some body help.
>
> I just need to push a flow which says, if the packet comes from a
> particular port, push it out on a particular port.
>
>
> Please do let me know.
>
>
> Thanks and Regards
> Kashyap
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] how to add a flow entry through nox to the openflow switch

[Kyriakos Zarifis]

Hi,

which NOX components are you running? You need do have some component(s)
that will install flow entries on the switch for the ping to go through
have a look here:
http://noxrepo.org/noxwiki/index.php/FAQ#What_does_the_traversal_of_a_packet_through_a_NOX_controlled_network_look_like.3F


2011/4/26 linbo 

>  Hi ，all
>  I want to verify the  openflow and controller work well or not，but I get
> something wrong.
> here is my problem:
> 1、the openflow switch has connetected to nox ，and the topology is as
> follow：
>  openflow-controller:eth0 -> 192.168.1.1/24
> openflow-switch:eth0 -> 192.168.1.2/24
> openflow-switch:eth1 -> no IP (would act as a switch port)
> openflow-switch:eth2 -> no IP (would act as a switch port)
> openflow-host1:eth0 -> 192.168.2.1/24
> openflow-host2:eth0 -> 192.168.2.2/24
>
>
> 2、when i ping host1 from host2  ，I can‘t see any ping replies coming.
>
> i check out the flow table of the switch ，and  the flow table of the
> swtich is empty。
> so how can I add  a flow entry through nox to the openflow switch to let
> the ping work welll
>
> Thank you！
>
> 2011-04-26
> --
> linbo
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] # of times Flows_stats_in event handler should be triggered

[Kyriakos Zarifis]

Hi Hamid,

I don't think I've come across cases where I get multiple replies for a
single flow stat request. What switch are you using? Are you sure you're
only sending a single request? Did you try to troubleshoot with wireshark,
and if so
do you actually see one request and a couple replies?

On Mon, Apr 18, 2011 at 4:38 PM, Hamid Bazzaz  wrote:

> Hi folks,
>
> I am registering a handler for the Flows_stats_in_event handler in my NOX
> application and would like to do certain processing upon receiving the flow
> stats from each switch in my topology. What happens is that every time I
> send a request to fetch the flow stats of my switches, the event handler is
> triggered a few times for each switch. I wonder how many trigger of the
> event handler I should be expecting for a single flow stats request. Is it
> the case that stats for a single flows might get divided into separate
> events? If so, when can I know for sure that all the flow stats of a single
> switch has arrived?
>
> Thanks,
> --Hamid
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] CONTINUE vs. STOP in Disposition methods?

[Kyriakos Zarifis]

just as a follow-up, this
http://noxrepo.org/noxwiki/index.php/Disposition
also explains how to control the event processing chain


On Thu, Apr 14, 2011 at 5:42 PM, Hamid Bazzaz  wrote:

> I see. Thanks for clarifying this Martin!
>
> --Hamid
>
>
> On Thu, Apr 14, 2011 at 5:41 PM, Martin Casado  wrote:
>
>>  CONTINUE = continue to call handlers in the call chain
>> STOP = don't call any additional handlers for this event
>>
>> Hello,
>>
>> I am curious what's the difference between returning STOP vs. CONTINUE in
>> the Disposition methods. Specifically, should we return STOP or CONTINUE in
>> case of some errors happening? I believe I have seen both cases in different
>> sample codes and I haven't been able to completely understand the
>> difference.
>>
>> Thanks,
>> --Hamid
>>
>>
>> ___
>> nox-dev mailing 
>> listnox-dev@noxrepo.orghttp://noxrepo.org/mailman/listinfo/nox-dev
>>
>>
>>
>> --
>> ~~~
>> Martin Casado
>> Nicira Networks, Inc.www.nicira.com | www.openvswitch.org
>> cell: 650-776-1457
>> ~~~
>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Which NOX module should be used for wireless networks testing

[Kyriakos Zarifis]

That's right, you'd have to update the STP module meta file to the current
meta format (json). The transition is pretty straightforward: just take a
look at a meta.xml of any module and the corresponding meta.json in zaku
I have actually included and tried out the module on my local branch but
haven't pushed to the repo destiny yet, but you should be able to add the
module on your NOX installation..
Then it should work fine with, say, pyswitch.
As for interoperation with routing, it's not immediately clear if it would
not break - like you said, I think the fact that routing doesn't FLOOD
packets would probably break it. (Maybe you could give it a try, and/or give
a try hacking routing in order to FLOOD instead?)

On Wed, Apr 13, 2011 at 1:19 PM, sachin sharma wrote:

>
> Hi,
> I had tried integrate this STP implementation in NOX version 0.9 (Zaku)
> which is compatible  with openflow 1.0. But could not because the structure
> of xml file etc are different, which i could not understand that how to
> integrate it. But I was successful in integrating that in 0.5 version.
>
>
> I did not test this STP with routing module but i have gone through the
> code and read this release. and found that this STP release creates the
> spanning tree for OFP_FLOOD packets.
>
> As i understood from the routing module code, it does not send this packet
> for searching the unknown destintation. It searches by explicitly sending
> the packet to each and every output port except incoming port.
> However if this spanning tree implementation takes care above to create
> loop free environment, than may be this implementation is also able to
> recover from loops. (but i m not sure about that)
>
> Thanks,
> Sachin
> --- On *Thu, 14/4/11, Kyriakos Zarifis * wrote:
>
>
> From: Kyriakos Zarifis 
>
> Subject: Re: [nox-dev] Which NOX module should be used for wireless
> networks testing
> To: "sachin sharma" 
> Cc: "James Murphy McCauley" , nox-dev@noxrepo.org
> Date: Thursday, 14 April, 2011, 1:38 AM
>
>
> Hey Sachin
>
> do you know why this STP module would not work with zaku? I'm asking
> because I have actually used it (not too thoroughly to be honest) and didn't
> immediately see any issues.
> Is it the fact that routing does not use OFP_FLOOD, so it wouldn't work
> with routing, or is it an issue with the STP module itself?
>
> On Wed, Apr 13, 2011 at 1:00 PM, sachin sharma 
> http://mc/compose?to=sharon_sac...@yahoo.co.in>
> > wrote:
>
> Hi Murphy,
> I know this basic spanning tree implementation but this is only compatible
> with NOX version 0.5.
>
> I am using openflow version 1.0 in openwrt linux which does not support 0.5
> version. So. do u have a spanning tree implementation which is compatible
> with the NOX supporting openflow version 1.0
>
>
> I have  one doubt that whether routing loops (Routing Module at NOX) can be
> prevented by this implementation. Because routing module  does not flood the
> packets by (OFP_FLOOD) but it transmits the packet to each and every port
> except incoming port explicitly when it does not know the destination.
>
> thanks,
> Sachin
>
>
> --- On *Thu, 14/4/11, James "Murphy" McCauley 
> http://mc/compose?to=jam...@nau.edu>
> >* wrote:
>
>
> From: James "Murphy" McCauley 
> http://mc/compose?to=jam...@nau.edu>
> >
> Subject: Re: [nox-dev] Which NOX module should be used for wireless
> networks testing
> To: "sachin sharma" 
> http://mc/compose?to=sharon_sac...@yahoo.co.in>
> >
> Cc: nox-dev@noxrepo.org <http://mc/compose?to=nox-dev@noxrepo.org>
> Date: Thursday, 14 April, 2011, 1:07 AM
>
>
> You might want to take a look at the spanning_tree component:
> http://www.openflow.org/wk/index.php/Basic_Spanning_Tree
>
> -- Murphy
>
> On Thu, 2011-04-14 at 01:01 +0530, sachin sharma wrote:
> >
> >
> > Hi,
> >
> >
> > I am interested to test openflow in wireless networks where loops are
> > present in topology. I have tested openflow in wired network where i
> > found that loops in topology prevent openflow to work properly.
> > However, this problem can be solved if switch itself has STP
> > implemented.
> >
> >
> >
> >
> > But now I am interested to measure OpenFlow performance in wireless
> > network such that loop problem should not occur.  I am actually
> > interested in OLSR/DSDV like protocol.
> >
> >
> > I think, I can not use routing (implemented in NOX) as when topology
> > module does not know about the destination. packet is transmitted to
> > each and every port except incoming port. This

Re: [nox-dev] Which NOX module should be used for wireless networks testing

[Kyriakos Zarifis]

Hey Sachin

do you know why this STP module would not work with zaku? I'm asking because
I have actually used it (not too thoroughly to be honest) and didn't
immediately see any issues.
Is it the fact that routing does not use OFP_FLOOD, so it wouldn't work with
routing, or is it an issue with the STP module itself?

On Wed, Apr 13, 2011 at 1:00 PM, sachin sharma wrote:

> Hi Murphy,
> I know this basic spanning tree implementation but this is only compatible
> with NOX version 0.5.
>
> I am using openflow version 1.0 in openwrt linux which does not support 0.5
> version. So. do u have a spanning tree implementation which is compatible
> with the NOX supporting openflow version 1.0
>
>
> I have  one doubt that whether routing loops (Routing Module at NOX) can be
> prevented by this implementation. Because routing module  does not flood the
> packets by (OFP_FLOOD) but it transmits the packet to each and every port
> except incoming port explicitly when it does not know the destination.
>
> thanks,
> Sachin
>
>
> --- On *Thu, 14/4/11, James "Murphy" McCauley * wrote:
>
>
> From: James "Murphy" McCauley 
> Subject: Re: [nox-dev] Which NOX module should be used for wireless
> networks testing
> To: "sachin sharma" 
> Cc: nox-dev@noxrepo.org
> Date: Thursday, 14 April, 2011, 1:07 AM
>
>
> You might want to take a look at the spanning_tree component:
> http://www.openflow.org/wk/index.php/Basic_Spanning_Tree
>
> -- Murphy
>
> On Thu, 2011-04-14 at 01:01 +0530, sachin sharma wrote:
> >
> >
> > Hi,
> >
> >
> > I am interested to test openflow in wireless networks where loops are
> > present in topology. I have tested openflow in wired network where i
> > found that loops in topology prevent openflow to work properly.
> > However, this problem can be solved if switch itself has STP
> > implemented.
> >
> >
> >
> >
> > But now I am interested to measure OpenFlow performance in wireless
> > network such that loop problem should not occur.  I am actually
> > interested in OLSR/DSDV like protocol.
> >
> >
> > I think, I can not use routing (implemented in NOX) as when topology
> > module does not know about the destination. packet is transmitted to
> > each and every port except incoming port. This give rise to problem of
> > looping.
> >
> >
> > I cannot use MAC learning also because it does flooding where there is
> > also a chances of looping.
> >
> >
> > So, what to use?
> >
> >
> > Can you please suggest me that which NOX module I should use for this
> > testing.
> >
> >
> >
> >
> > Thanks in replying,
> > Sachin
> > ___
> > nox-dev mailing list
> > nox-dev@noxrepo.org 
> > http://noxrepo.org/mailman/listinfo/nox-dev
>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] getting switch port number connected to a host

[Kyriakos Zarifis]

Hey,

take a look at the API provided by pybindings_storage:

void get_names_by_mac(const ethernetaddr &mac, const Get_names_callback
&cb);
and then
void get_location_by_name(int64_t locationname, Name::Type name_type, const
Get_locations_callback &cb);

would something like this do it for you?  (Location holds dpid and port
info)

On Tue, Apr 5, 2011 at 1:25 PM, karim torkmen wrote:

> Hi,
> I am trying to retrieve the topology of an openflow network through
> pybindings_storage.
> Untill now, I succeed to get the different connections between the switches
> i.e the tuple (src_dpid,src_port,dst_dpid,dst_port) through the method
> get_all_links() which seems to return just teh links between the switches.
> But, I still need to have a tuple of the type (host_mac_address,
> dst_dpid,dst_port).
> Any idea about how to get this information.
> Thanks a lot for your help.
> Regards,
> Karim
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] problem running a new component

[Kyriakos Zarifis]

Hey Karim,

Your component is using pybindings_storage, so it needs to be running. If
you don't want to call it manually, you need to define pybindings_storage as
a dependency for your component, so that it is deployed automatically.
You do that in the meta.json file of try_topology.

On Mon, Apr 4, 2011 at 4:26 AM, karim torkmen wrote:

> Hi,
> I am developing a new component called "try_topology" that uses  the
> "bindings_storage" component.
> When I run it with this command :
> - ./nox_core -v  -i ptcp:6633 pybindings_storage try_topology
> It returns no errors. However, by calling just the "try_topolgy" component,
> I get the following error:
>
> 00042|nox|ERR:Cannot change the state of 'try_topology' to INSTALLED:
> 'try_topology' ran into an error:
>cannot import a Python module 'nox.coreapps.try_topology.try_topology':
>Traceback (most recent call last):
>  File
> "/home/karim/nox/build/src/nox/coreapps/try_topology/try_topology.py", line
> 3, in 
>from nox.netapps.bindings_storage.pybindings_storage import
> pybindings_storage
>  File
> "/home/karim/nox/build/src/nox/netapps/bindings_storage/pybindings_storage.py",
> line 25, in 
>_pybindings_storage = swig_import_helper()
>  File
> "/home/karim/nox/build/src/nox/netapps/bindings_storage/pybindings_storage.py",
> line 21, in swig_import_helper
>_mod = imp.load_module('_pybindings_storage', fp, pathname,
> description)
>ImportError:
> /home/karim/nox/build/src/nox/netapps/bindings_storage/_pybindings_storage.so:
> undefined symbol:
> vigil::applications::Bindings_Storage::get_all_names(vigil::applications::Name::Type,
> boost::function std::allocator >&)> const&)
>
> Any Idea about this error.
> Thanks a lot,
> Karim
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] 00005|nox|ERR:Application

[Kyriakos Zarifis]

Hey,

you only need to rebuild NOX the first time you introduce a new python
component (after following the instructions on the wiki), so that the links
are created to the build/src/ directory. After that, you can simply run NOX
each time you edit your python component.

On Thu, Mar 31, 2011 at 11:32 PM, Bill Liao  wrote:

> On Fri, Apr 1, 2011 at 5:29 AM, Kyriakos Zarifis 
> wrote:
> > Hi Karim,
> > did you rerun ../configure and make after you edited configure.ac and
> > Makefile.am?
> >
> > On Thu, Mar 31, 2011 at 7:42 AM, karim torkmen  >
> > wrote:
> >>
> >> Hi,
> >> I developed a component when I try to run it, I get the following error
> >> message :
> >>
> >> 
> >> 1|nox|INFO:Starting nox_core (/nox/build/src/.libs/lt-nox_core)
> >> 2|nox|DBG:Application installation report:
> >> 3|nox|DBG:built-in DSO deployer:
> >>Current state: INSTALLED
> >>Required state: INSTALLED
> >>Dependencies:
> >>
> >> 4|nox|DBG:built-in event dispatcher:
> >>Current state: INSTALLED
> >>Required state: INSTALLED
> >>Dependencies:
> >>
> >> 5|nox|ERR:Application 'try_topology' description not found.
> >> ***
> >> To add my component I tried two methods:
> >> The first one is through executing the script : nox-new-c-app.py
> >> The second one is by editing meta.json, configure.ac and Makefile.am.
> >> Unfortunately, none of them was able to make me run my component.
> >>
> >> Thank you for your help.
> >> Regards,
> >> Karim
> >>
> >>
> >> ___
> >> nox-dev mailing list
> >> nox-dev@noxrepo.org
> >> http://noxrepo.org/mailman/listinfo/nox-dev
> >
> >
> > ___
> > nox-dev mailing list
> > nox-dev@noxrepo.org
> > http://noxrepo.org/mailman/listinfo/nox-dev
> >
> >
>
> Hi, Kyriakos
>   Sorry to interrupt. But I'm wondering is it necessary to re-make
> after building a new python component.
>   As far as I know after reading some source, there is no such
> requirement right?
>   The python component is managed by PyRt, just as Dso-deployer. So,
> for c++ component, maybe we should make to produce the *.so dynamic
> library, but what will MAKE produce for new python component?
>
>   Regards
>   wliao
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] 00005|nox|ERR:Application

[Kyriakos Zarifis]

Hi Karim,

did you rerun ../configure and make after you edited configure.ac and
Makefile.am?

On Thu, Mar 31, 2011 at 7:42 AM, karim torkmen wrote:

> Hi,
> I developed a component when I try to run it, I get the following error
> message :
>
> 
> 1|nox|INFO:Starting nox_core (/nox/build/src/.libs/lt-nox_core)
> 2|nox|DBG:Application installation report:
> 3|nox|DBG:built-in DSO deployer:
>Current state: INSTALLED
>Required state: INSTALLED
>Dependencies:
>
> 4|nox|DBG:built-in event dispatcher:
>Current state: INSTALLED
>Required state: INSTALLED
>Dependencies:
>
> 5|nox|ERR:Application 'try_topology' description not found.
> ***
> To add my component I tried two methods:
> The first one is through executing the script : nox-new-c-app.py
> The second one is by editing meta.json, configure.ac and Makefile.am.
> Unfortunately, none of them was able to make me run my component.
>
> Thank you for your help.
> Regards,
> Karim
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Have any application in NOX supports multicast?

[Kyriakos Zarifis]

On Wed, Mar 30, 2011 at 11:38 PM, Jen-Wei Hu  wrote:

> Dear Kyriakos,
>
> Thanks for your quickly help. Last week, I found in lib/packet have some
> files, such as arp or icmp. That time, I think may not follow them to do
> similar thing. But after your explanation, I think we are wrong and must to
> do it. The other thing is we also record which ports contain vedio
> streaming, is it right?
>

Do you mean keep track of the multicast sources? I guess that depends on the
implementation. You might not necessarily have to do that. (In traditional
multicast with shared trees, the routers only care about which of their
ports lead to interested multicast listeners, and don't necessarily hold any
state about the sources.) But yes, since there's a centralized controller
with the view of the topology, it mightmake sense to register the sources'
locations with the controller, and create the trees in a more static way
(meaning, in traditional MC a join message would propagate all the way up to
a Rendezvous Point, but with NOX you could probably grab the IGMP join at
the leaf, and figure out how to connect the leaf to your tree in NOX)


>
> Thanks
>
> Jen-Wei
>
> On Thu, Mar 31, 2011 at 2:29 PM, Kyriakos Zarifis 
> wrote:
>
>> Hi,
>>
>> although that would take some effort, it is perfectly doable to hold that
>> information on your component. You wouldn't have to use v1.1 tables or
>> anything like that, all the state would be on your controller. While there
>> are several packet types of packets included in the packet parsing library
>> of NOX, IGMP messages are unfortunately one of them. So in order to extract
>> the Join/Leave Group information, you would have to parse them manually (or
>> add a relevant igmp.py in lib/packet/, following the paradigm of the other
>> packet classes. such an addition would be welcome).
>>
>>
>> On Wed, Mar 30, 2011 at 11:20 PM, Jen-Wei Hu  wrote:
>>
>>> Dear Murphy & KK,
>>>
>>> Thanks for your kindly reply and help. Just like KK mentioned, we might
>>> need an IGMP multicast. So, in this point, we must do something on NOX. That
>>> is, we need to implement a data structure that do the same thing as Group
>>> table for recording which ports have IGMP request. Is is right, please clear
>>> me!
>>>
>>> Thanks
>>>
>>> Jen-Wei
>>>
>>> On Mon, Mar 28, 2011 at 9:22 AM, kk yap  wrote:
>>>
>>>> Hi Jen-Wei,
>>>>
>>>> OpenFlow 1.1 (implemented) is released, so it is quite final for me.
>>>>
>>>> Also, if you are not constrained to using the group semantics (in
>>>> OpenFlow 1.1), you can do multicast by listing all the ports you want
>>>> to multicast to in the flow_mod command.
>>>>
>>>> If you are looking for IGMP multicast support, then you are looking
>>>> for someone to do some work.
>>>>
>>>> Regards
>>>> KK
>>>>
>>>> On 27 March 2011 17:41, James "Murphy" McCauley  wrote:
>>>> > So this is certainly not an official statement of any sort, but I
>>>> would
>>>> > not expect to see OpenFlow 1.1 support in NOX for a while.  I believe
>>>> > there's some consensus that supporting both 1.0 and 1.1 well will
>>>> > require some nontrivial API changes (and we're due for some API
>>>> changes
>>>> > anyway), and there will be a focus on getting some of that right
>>>> rather
>>>> > than incrementally updating NOX as has been done for previous OpenFlow
>>>> > versions.
>>>> >
>>>> > And before we even have 1.1 compatibility, I really would not hazard a
>>>> > guess about what we'd be releasing supporting multicast.  Sorry!
>>>> >
>>>> > Hopefully we'll have more of an idea about this in the coming months,
>>>> as
>>>> > well as more actual OpenFlow 1.1 implementations.
>>>> >
>>>> > (Also, as far as my limited understanding goes, OpenFlow 1.1 is still
>>>> > not final...)
>>>> >
>>>> > -- Murphy
>>>> >
>>>> > On Sat, 2011-03-26 at 11:33 +0800, Jen-Wei Hu wrote:
>>>> >> Hi all,
>>>> >>
>>>> >> We are glad to hear the version 1.1 of OpenFlow is released because
>>>> >> this version create a Group table for supporting multicast. Although
>>>> >> we use the NOX that support OpenFlow 1.0, would any plan to develop
>>>> an
>>>> >> application or example which supports multicast? Or give us
>>>> >> some advices to do it? Thank you!
>>>> >>
>>>> >> Bests,
>>>> >>
>>>> >> Jen-Wei
>>>> >> ___
>>>> >> nox-dev mailing list
>>>> >> nox-dev@noxrepo.org
>>>> >> http://noxrepo.org/mailman/listinfo/nox-dev
>>>> >
>>>> >
>>>> > ___
>>>> > nox-dev mailing list
>>>> > nox-dev@noxrepo.org
>>>> > http://noxrepo.org/mailman/listinfo/nox-dev
>>>> >
>>>>
>>>
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev
>>>
>>>
>>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Have any application in NOX supports multicast?

[Kyriakos Zarifis]

Hi,

although that would take some effort, it is perfectly doable to hold that
information on your component. You wouldn't have to use v1.1 tables or
anything like that, all the state would be on your controller. While there
are several packet types of packets included in the packet parsing library
of NOX, IGMP messages are unfortunately one of them. So in order to extract
the Join/Leave Group information, you would have to parse them manually (or
add a relevant igmp.py in lib/packet/, following the paradigm of the other
packet classes. such an addition would be welcome).

On Wed, Mar 30, 2011 at 11:20 PM, Jen-Wei Hu  wrote:

> Dear Murphy & KK,
>
> Thanks for your kindly reply and help. Just like KK mentioned, we might
> need an IGMP multicast. So, in this point, we must do something on NOX. That
> is, we need to implement a data structure that do the same thing as Group
> table for recording which ports have IGMP request. Is is right, please clear
> me!
>
> Thanks
>
> Jen-Wei
>
> On Mon, Mar 28, 2011 at 9:22 AM, kk yap  wrote:
>
>> Hi Jen-Wei,
>>
>> OpenFlow 1.1 (implemented) is released, so it is quite final for me.
>>
>> Also, if you are not constrained to using the group semantics (in
>> OpenFlow 1.1), you can do multicast by listing all the ports you want
>> to multicast to in the flow_mod command.
>>
>> If you are looking for IGMP multicast support, then you are looking
>> for someone to do some work.
>>
>> Regards
>> KK
>>
>> On 27 March 2011 17:41, James "Murphy" McCauley  wrote:
>> > So this is certainly not an official statement of any sort, but I would
>> > not expect to see OpenFlow 1.1 support in NOX for a while.  I believe
>> > there's some consensus that supporting both 1.0 and 1.1 well will
>> > require some nontrivial API changes (and we're due for some API changes
>> > anyway), and there will be a focus on getting some of that right rather
>> > than incrementally updating NOX as has been done for previous OpenFlow
>> > versions.
>> >
>> > And before we even have 1.1 compatibility, I really would not hazard a
>> > guess about what we'd be releasing supporting multicast.  Sorry!
>> >
>> > Hopefully we'll have more of an idea about this in the coming months, as
>> > well as more actual OpenFlow 1.1 implementations.
>> >
>> > (Also, as far as my limited understanding goes, OpenFlow 1.1 is still
>> > not final...)
>> >
>> > -- Murphy
>> >
>> > On Sat, 2011-03-26 at 11:33 +0800, Jen-Wei Hu wrote:
>> >> Hi all,
>> >>
>> >> We are glad to hear the version 1.1 of OpenFlow is released because
>> >> this version create a Group table for supporting multicast. Although
>> >> we use the NOX that support OpenFlow 1.0, would any plan to develop an
>> >> application or example which supports multicast? Or give us
>> >> some advices to do it? Thank you!
>> >>
>> >> Bests,
>> >>
>> >> Jen-Wei
>> >> ___
>> >> nox-dev mailing list
>> >> nox-dev@noxrepo.org
>> >> http://noxrepo.org/mailman/listinfo/nox-dev
>> >
>> >
>> > ___
>> > nox-dev mailing list
>> > nox-dev@noxrepo.org
>> > http://noxrepo.org/mailman/listinfo/nox-dev
>> >
>>
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] correspondence mac address port number

[Kyriakos Zarifis]

Oh I see - the bindings_storage module would hold that information

from nox.netapps.bindings_storage.pybindings_storage import
pybindings_storage

self.bindings = self.resolve(pybindings_storage)

and then you can use the module's API as defined in netapps/bindings_storage
for example self.bindings.get_all_links() would give you a list with tuples
of the form (src_dpid, src_port, dst_dpid, dst_port)

you can take a look at the code of Glen Gibb's spanning tree
module<http://www.openflow.org/wk/index.php/Basic_Spanning_Tree>,
which is the only example that comes to my mind that uses the python binding
storage API

On Tue, Mar 29, 2011 at 3:36 AM, karim torkmen wrote:

>  On 03/29/2011 12:29 PM, Kyriakos Zarifis wrote:
>
> Hi Karim,
>
>  the second parameter of install_datapath_flow() is a python dictionary
> that describes the flow for which you are setting up an entry. This is where
> you specify the MAC address(es). Create a dictionary, populate as you want
> (the keys for the source and destination addresses are 'dl_src' and 'dl_dst'
> respectively. - missing key/value pair equals wildcard for that field), and
> pass it to install_datapath_flow.
>
>  If you take a look at src/nox/lib/core.py, which defines the python API,
> you'll find some information about this in the definition of
> install_datapath_flow()
>
> On Tue, Mar 29, 2011 at 3:03 AM, karim torkmen 
> wrote:
>
>> Hi,
>> I want to set-up statically a path using openflow but the
>> install_datapath_flow() method does not accept mac address as parameter,  so
>> I need to know the correspondence between mac addresses and port numbers in
>> a switch so that I can choose the out_port that is correspondent to a mac
>> address.
>> Is there any method that allows it ?
>> Thanks a lot,
>> Karim
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>>
>
>  Thanks Kyriakos :)
> My question was not very well formulated ;)
> I meant in order to set a path I need to know the topology of the openFlow
> network, e.g. port 1 of switch 1 is linked to port 1 of switch 2 etc. in
> order to decide how to populate the switching table.
> Is there any method to get this information ?
> Thanks a lot
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] correspondence mac address port number

[Kyriakos Zarifis]

Hi Karim,

the second parameter of install_datapath_flow() is a python dictionary that
describes the flow for which you are setting up an entry. This is where you
specify the MAC address(es). Create a dictionary, populate as you want (the
keys for the source and destination addresses are 'dl_src' and 'dl_dst'
respectively. - missing key/value pair equals wildcard for that field), and
pass it to install_datapath_flow.

If you take a look at src/nox/lib/core.py, which defines the python API,
you'll find some information about this in the definition of
install_datapath_flow()

On Tue, Mar 29, 2011 at 3:03 AM, karim torkmen wrote:

> Hi,
> I want to set-up statically a path using openflow but the
> install_datapath_flow() method does not accept mac address as parameter,  so
> I need to know the correspondence between mac addresses and port numbers in
> a switch so that I can choose the out_port that is correspondent to a mac
> address.
> Is there any method that allows it ?
> Thanks a lot,
> Karim
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] some confusions about the inport parameter

[Kyriakos Zarifis]

Hi Karim,

'inport' actually refers to a different thing in each case:

 * send_openflow(dpid, bufid, buf, openflow.OFPP_FLOOD, inport)
>
send_openflow is used to inject a packet in the network, and send it out the
'dpids's port(s) described the 4th parameter. The switch should treat the
packet as if it arrived on 'inport'. The packet actually arrives through the
openflow channel, but you use this for things like openflow.OFPP_TABLE,
where the packet will be forwarded based on the flow_table matches, in which
case it needs to have arrived on a physical port.


> * install_datapath_flow(dpid, flow, 5, 0, actions, bufid,
> openflow.OFP_DEFAULT_PRIORITY, inport, packet)
>
Here it is indeed what you said: it is the input port to match for this flow
entry we are installing. (after installing this entry, packets matching
'flow' arriving on 'inport' all be treated according to 'actions')

>
> Do they design the port of communication between the controller and the
> switch, or the port from which a switch received a packet and that has after
> to forward it to the controller.
> In the first case it seems that the inport is the port between the
> controller and the switch, however the second case seems to be the port from
> which a switch received a packet.
> Thanks a lot.
> Regards,
> Karim
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] links capacities tracking

[Kyriakos Zarifis]

Hi Harry,

if you use the destiny branch, the GUI there offers some relevant
functionality. The main idea is that the 'monitoring' component periodically
polls statistics from switches, including traffic sent/received. One of the
things it does is that it tries to estimate the current utilization based on
these values for neighboring switches, the link capacity and the collection
period. (However I'm not convinced that the numbers it reports are currently
correct and some testing is definitely due)

On Mon, Mar 28, 2011 at 9:09 AM, Harry  wrote:

> Hi all,
> Do you have any idea how can I track the capacity of a link in mininet and
> the total traffic passing through that link?
>
> Thanks in advance!
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] Blocking Modules

[Kyriakos Zarifis]

Hey Aaron,

yes, I think this code would block NOX. For non-blocking communication with
external processes, you should do one of the following:

a) use Twisted: you'll have to implement an interface for communication with
twisted in your module and your external app. This might be easier if your
external app is also in python. I did this a while back and can provide you
with some reference code. But there's also plenty examples online.
b) use the 'messenger' component: send your message from your external app
to the messenger's socket (this won't block) and have the messenger dispatch
it to your component. For reference, the GUI in the destiny branch is using
the messenger (or specifically 'jsonmessenger') to communicate with NOX

On Sun, Mar 27, 2011 at 5:01 PM, Aaron Rosen  wrote:

> Hello,
>
> I'm trying to get some threading working in a nox module but I've read on
> the mailing list that the python threading does not work well due to the
> global locking (and thats what I'm seeing to.. ). Anyways I was wondering If
> there is any reason why this short module wouldn't work?
>
> I've connected my openflow software switch to have a dpid of 1 with
> --datapath-id=0001
>
> Though when I send command over a socket to this module I'm getting
>
> 00037|nox|ERR:no datapath with id 0001 registered at nox
>
> Since this code is all in a while loop could that be causing the OF switch
> not to connect?
>
>
> Here is my code:
>
> http://pastebin.com/7WVNADwy
>
> Thanks!
>
> Aaron
>
>
>
> --
> Aaron O. Rosen
> Masters Student - Network Communication
> 306B Fluor Daniel
> 843.425.9777
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Re: [nox-dev] nox controller configuration for load balancing

[Kyriakos Zarifis]

Hi ,

NOX does not provide load balancing functionality by default; you would need
to write your own application.
A high level description of the functionality that you'd have to program on
NOX in order to achieve network-layer load balancing is: Listen for incoming
requests from the clients and set up flows to one of the servers for each
one of them: The requests are destined to the same IP, the OF switch
forwards incoming requests to NOX, NOX picks a server and sets up a rule on
the switch for the specific flow.

If you haven't done so, I'd suggest taking a look
here to
familiarize yourself with NOX. You'll also find some instructions on writing
your own NOX components, although a good practice is to look at existing
code and copy/hack it. If you look at the routing component and understand
how it works, it might be easier to hack that than to write a new component

On Sat, Mar 19, 2011 at 3:28 AM, Hilman Fathurrahman  wrote:

> I want to do a simple test using openflow for load balancing between 2
>
> server
>
> Topology :
>
> clients  internet  OF switch  NOX contoller
>   |   |
>   server1server2
>
>
> How do i configure nox contoller ?
> Thanks for your help
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev