Re: [nox-dev] need support for these features in NOX
The enqueue action is supported in destiny. Flow stats are possible (there has been some recent discussion about it on the list, I believe). I'm not sure what you mean by queue statistics. Matches support wildcards to the extent offered by OpenFlow 1.0. I'm actually not sure about fragments. If I recall correctly, this is more a function of the switch rather than the controller. I'm not sure what you mean by supporting those errors. The controller receives error the messages, so... yes? You also haven't mentioned whether you're interested in the Python or the C++ API, and support differs somewhat across languages. -- Murphy On Jan 15, 2012, at 7:55 PM, Sheili Mittal wrote: Hi Murphy, Thanks for this quick response, I needed that data urgently. Can you please confirm are the below mentioned features supported in destiny branch? I saw destiny branch is unstable on NOX site so I used 0.9 zaku. Thanks Regards, Sheili Mittal From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 09:22 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] need support for these features in NOX The most recent branch is destiny. -- Murphy On Jan 15, 2012, at 7:49 PM, Sheili Mittal wrote: Hi, I am using NOX 0.9 zaku, following is not supporting in this, Can anyone please confirm in which branch of NOX all the following supported:- 1) Action Enqueue 2) Flow statistics 3) Queue statistics 4) Wilcard ( ANY and other wildcard of openflow 1.0) 5) L3 matching on IP fragment 6) Error message – OFPET_FLOW_MOD_FAILED OFPET_PORT_MOD_FAILED OFPET_QUEUE_OP_FAILED Regards, Sheili DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] NOX for 64 bit
destiny is routinely run on both 32 and 64 bit systems. -- Murphy On Jan 16, 2012, at 12:52 AM, Sheili Mittal wrote: Hi, Can you please confirm are the branch available on git (0.9 zaku) and destiny supported for 64 bit machine also? Are the version we downloading from git is for 32bit and 64 bit both? Thanks Regards, Sheili Mittal DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ 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 for 64 bit
Thanks Murphy Please confirm for NOX 0.9 zaku as well? Regards, Sheili From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 14:29 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX for 64 bit destiny is routinely run on both 32 and 64 bit systems. -- Murphy On Jan 16, 2012, at 12:52 AM, Sheili Mittal wrote: Hi, Can you please confirm are the branch available on git (0.9 zaku) and destiny supported for 64 bit machine also? Are the version we downloading from git is for 32bit and 64 bit both? Thanks Regards, Sheili Mittal DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ---___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] NOX for 64 bit
Probably no major problems, but there might be minor ones. I honestly don't remember; I have not run zaku in quite some time. Unless you're already running it, there are only a few good reasons to run zaku now. -- Murphy On Jan 16, 2012, at 1:01 AM, Sheili Mittal wrote: Thanks Murphy Please confirm for NOX 0.9 zaku as well? Regards, Sheili From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 14:29 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX for 64 bit destiny is routinely run on both 32 and 64 bit systems. -- Murphy On Jan 16, 2012, at 12:52 AM, Sheili Mittal wrote: Hi, Can you please confirm are the branch available on git (0.9 zaku) and destiny supported for 64 bit machine also? Are the version we downloading from git is for 32bit and 64 bit both? Thanks Regards, Sheili Mittal DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] need support for these features in NOX
Hi Murphy, I am using Python APIs. Please see inline. Regards, Sheili From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 14:28 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] need support for these features in NOX The enqueue action is supported in destiny. Is the dentiny branch safe to test all openflow 1.0 functionalities? , I saw its unstable. Flow stats are possible (there has been some recent discussion about it on the list, I believe). I will search for that. I'm not sure what you mean by queue statistics. According to openflow 1.0 spec , we can add any packet to a queue with its action enqueue in flow entry , so there is a functionality to get its statistics also. Following parameters are in openflow 1.0 spec, which I want to access - Transmit Packets 64 Transmit Bytes 64 Transmit Overrun Errors 64 Matches support wildcards to the extent offered by OpenFlow 1.0. When I am using wildcard then NOX (0.9) giving me error :- (error:unsupported flow attribute) I'm actually not sure about fragments. If I recall correctly, this is more a function of the switch rather than the controller. There are parameters to make flow entry with ip fragment fields ( to match IP packets against these fields), that I haven''t found in NOX 0.9 zaku, it is present in ovs-ofctl. I'm not sure what you mean by supporting those errors. The controller receives error the messages, so... yes? You also haven't mentioned whether you're interested in the Python or the C++ API, and support differs somewhat across languages. -- Murphy On Jan 15, 2012, at 7:55 PM, Sheili Mittal wrote: Hi Murphy, Thanks for this quick response, I needed that data urgently. Can you please confirm are the below mentioned features supported in destiny branch? I saw destiny branch is unstable on NOX site so I used 0.9 zaku. Thanks Regards, Sheili Mittal From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 09:22 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] need support for these features in NOX The most recent branch is destiny. -- Murphy On Jan 15, 2012, at 7:49 PM, Sheili Mittal wrote: Hi, I am using NOX 0.9 zaku, following is not supporting in this, Can anyone please confirm in which branch of NOX all the following supported:- 1) Action Enqueue 2) Flow statistics 3) Queue statistics 4) Wilcard ( ANY and other wildcard of openflow 1.0) 5) L3 matching on IP fragment 6) Error message - OFPET_FLOW_MOD_FAILED OFPET_PORT_MOD_FAILED OFPET_QUEUE_OP_FAILED Regards, Sheili DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or
[nox-dev] FW: need support for these features in NOX
Changing color so that you can identify inline text. Regards, Sheili From: Sheili Mittal Sent: 16 January 2012 15:03 To: 'Murphy McCauley' Cc: nox-dev@noxrepo.org Subject: RE: [nox-dev] need support for these features in NOX Hi Murphy, I am using Python APIs. Please see inline. Regards, Sheili From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 14:28 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] need support for these features in NOX The enqueue action is supported in destiny. Is the dentiny branch safe to test all openflow 1.0 functionalities? , I saw its unstable. Flow stats are possible (there has been some recent discussion about it on the list, I believe). I will search for that. I'm not sure what you mean by queue statistics. According to openflow 1.0 spec , we can add any packet to a queue with its action enqueue in flow entry , so there is a functionality to get its statistics also. Following parameters are in openflow 1.0 spec, which I want to access - Transmit Packets 64 Transmit Bytes 64 Transmit Overrun Errors 64 Matches support wildcards to the extent offered by OpenFlow 1.0. When I am using wildcard then NOX (0.9) giving me error :- (error:unsupported flow attribute) I'm actually not sure about fragments. If I recall correctly, this is more a function of the switch rather than the controller. There are parameters to make flow entry with ip fragment fields ( to match IP packets against these fields), that I haven''t found in NOX 0.9 zaku, it is present in ovs-ofctl. I'm not sure what you mean by supporting those errors. The controller receives error the messages, so... yes? You also haven't mentioned whether you're interested in the Python or the C++ API, and support differs somewhat across languages. -- Murphy On Jan 15, 2012, at 7:55 PM, Sheili Mittal wrote: Hi Murphy, Thanks for this quick response, I needed that data urgently. Can you please confirm are the below mentioned features supported in destiny branch? I saw destiny branch is unstable on NOX site so I used 0.9 zaku. Thanks Regards, Sheili Mittal From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 09:22 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] need support for these features in NOX The most recent branch is destiny. -- Murphy On Jan 15, 2012, at 7:49 PM, Sheili Mittal wrote: Hi, I am using NOX 0.9 zaku, following is not supporting in this, Can anyone please confirm in which branch of NOX all the following supported:- 1) Action Enqueue 2) Flow statistics 3) Queue statistics 4) Wilcard ( ANY and other wildcard of openflow 1.0) 5) L3 matching on IP fragment 6) Error message - OFPET_FLOW_MOD_FAILED OFPET_PORT_MOD_FAILED OFPET_QUEUE_OP_FAILED Regards, Sheili DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- DISCLAIMER:
[nox-dev] What is the main difference between “route” and “routing” in NOX
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] questions regarding OFPAT_STRIP_VLAN
Dear All, We're working on test suite, which should implement all OF 1.0 features. If somebody add OFPAT_STRIP_VLAN, modify IP and TOS fileds to nox sources? Thanks Alexander ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Measuring delay of links between switches
Hi, so I decided to go with a statsmanager component that measures delay and packet loss for every link found by the discovery component. To measure delay, I will send ICMP echo requests and measure the RTT for the links to the switches and then send a packet from the controller to switchA to switchB back to the controller. As a first approach this should be fine. The first problem I have is: How do I get the IPs of the switches to send the ICMP echo requests to? NOX talks to these switches via the control channel and I want to simply send an ICMP echo request to this IP. Is there any way to get this piece of information? The stats reply that I get from a datapath_join event doesn't contain it and I could not find anything else that might give me the needed information. Your help is very much appreciated. Best regards Bernd Wittefeld On 12.01.2012 15:34, Bernd Wittefeld wrote: Hi Kyriakos, yes I know of the propagation delays of the control channels. I thought of measuring these by simple ICMP Echo Requests and extracting the RTT from that. Assuming that we have symmetric channels, I can get an estimate of these delays and use them in the delay calculation. The processing time on the switches should be a part of the overall delay in my opinion, as the packets travelling through the network must also take this time to be processed. The question now is: which way is the best to implement this: patching the discovery module, as the infrastructure for periodical packets on every link is already there, or writing an own component which can be rather complex as there are some details that cannot be solved easily in my opinion. The LLDP packets are filtered out and processed. A similar concept would be needed in this component. Then is the question: what type of packets would be used and how would they be sent through the network? Maybe creating a simple packet with the dst IP of the controller and an action on the dst switch to forward the whole packet to the controller would work as long as the flows being installed do not interfere with the normal switch processing. Best regards Bernd On 11.01.2012 23:42, Kyriakos Zarifis wrote: 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 mailto: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
Re: [nox-dev] questions regarding OFPAT_STRIP_VLAN
Do you mean support creating flows using the OFPAT_STRIP_VLAN, OFPAT_SET_NW_SRC, OFPAT_SET_NW_DST, and OFPAT_SET_NW_TOS action types? If so, all of these should be available if you are using the destiny branch. -- Murphy On Jan 16, 2012, at 8:15 AM, Alexander Cheskis wrote: Dear All, We're working on test suite, which should implement all OF 1.0 features. If somebody add OFPAT_STRIP_VLAN, modify IP and TOS fileds to nox sources? Thanks Alexander ___ 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] attribute '_handleSigchld'
Hi Vjeko, I'm facing a similar issue. I recently upgraded twisted to 11.0 and found that an older (customized) version of nox crashes with the same error. Can you tell me to which class in '/usr/lib/python2.6/dist-packages/twisted/internet/base.py' should I add the _handleSigchld function? Thanks, -- Nikhil On Fri, Aug 6, 2010 at 1:58 PM, Vjekoslav Brajkovic bal...@cs.washington.edu wrote: Hi Tim! You are correct. After adding the following function definition to '/usr/lib/python2.6/dist-packages/twisted/internet/base.py', the problem seems to be gone. def _handleSigchld(self, signum, frame, _threadSupport=platform.supportsThreads()): from twisted.internet.process import reapAllProcesses if _threadSupport: self.callFromThread(reapAllProcesses) else: self.callLater(0, reapAllProcesses) Thanks a bunch! Vjeko On Fri, Aug 06, 2010 at 04:30:28PM -0400, tim.upthegr...@gatech.edu wrote: Hi Vjekoslav, I had this issue before after doing a fresh install on a Debian sid machine using the openflow-1.0 branch. What I found is, the function _handleSigchld has been moved-around/removed from more recent versions of TwistedPython. The fix I found was to go grab Twisted 8.0 and install it. I haven't tested the controller in a production setup yet, but the source compiles and I can run a simple switch without getting any error messages. Give that a shot and see if it works. Best of luck, Tim Upthegrove Georgia Institute of Technology College of Computing (406)-437-1493 - Vjekoslav Brajkovic bal...@cs.washington.edu wrote: Hello. After I upgraded my system, I've been having trouble starting NOX. This is the error message: 2|nox|ERR:Cannot change the state of 'python' to INSTALLED: 'python' ran into an error: Unable to construct a Python component: Traceback (most recent call last): File ./nox/coreapps/pyrt/pyoxidereactor.py, line 364, in instance return pyoxidereactor(ctxt) File ./nox/coreapps/pyrt/pyoxidereactor.py, line 133, in __init__ signal.signal(signal.SIGCHLD, self._handleSigchld) AttributeError: 'pyoxidereactor' object has no attribute '_handleSigchld' Any clues to why this might be happening? Thanks! Vjeko ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] attribute '_handleSigchld'
I believe you can safely just remove the offending line from pyoxidereactor (the signal.signal(signal.SIGCHLD, self._handleSigchld) one). If not, the current version of pyoxidereactor (from the destiny branch) should fix this in a way which doesn't require you to modify your system's Twisted installation. -- Murphy On Jan 16, 2012, at 1:38 PM, Nikhil Handigol wrote: Hi Vjeko, I'm facing a similar issue. I recently upgraded twisted to 11.0 and found that an older (customized) version of nox crashes with the same error. Can you tell me to which class in '/usr/lib/python2.6/dist-packages/twisted/internet/base.py' should I add the _handleSigchld function? Thanks, -- Nikhil On Fri, Aug 6, 2010 at 1:58 PM, Vjekoslav Brajkovic bal...@cs.washington.edu wrote: Hi Tim! You are correct. After adding the following function definition to '/usr/lib/python2.6/dist-packages/twisted/internet/base.py', the problem seems to be gone. def _handleSigchld(self, signum, frame, _threadSupport=platform.supportsThreads()): from twisted.internet.process import reapAllProcesses if _threadSupport: self.callFromThread(reapAllProcesses) else: self.callLater(0, reapAllProcesses) Thanks a bunch! Vjeko On Fri, Aug 06, 2010 at 04:30:28PM -0400, tim.upthegr...@gatech.edu wrote: Hi Vjekoslav, I had this issue before after doing a fresh install on a Debian sid machine using the openflow-1.0 branch. What I found is, the function _handleSigchld has been moved-around/removed from more recent versions of TwistedPython. The fix I found was to go grab Twisted 8.0 and install it. I haven't tested the controller in a production setup yet, but the source compiles and I can run a simple switch without getting any error messages. Give that a shot and see if it works. Best of luck, Tim Upthegrove Georgia Institute of Technology College of Computing (406)-437-1493 - Vjekoslav Brajkovic bal...@cs.washington.edu wrote: Hello. After I upgraded my system, I've been having trouble starting NOX. This is the error message: 2|nox|ERR:Cannot change the state of 'python' to INSTALLED: 'python' ran into an error: Unable to construct a Python component: Traceback (most recent call last): File ./nox/coreapps/pyrt/pyoxidereactor.py, line 364, in instance return pyoxidereactor(ctxt) File ./nox/coreapps/pyrt/pyoxidereactor.py, line 133, in __init__ signal.signal(signal.SIGCHLD, self._handleSigchld) AttributeError: 'pyoxidereactor' object has no attribute '_handleSigchld' Any clues to why this might be happening? Thanks! Vjeko ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ 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
Here's an overview of the routing component http://noxrepo.org/noxwiki/index.php/Routing On Mon, Jan 16, 2012 at 2:41 AM, 王楠 wangnan8...@gmail.com 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] NOX for 64 bit
Hi Murphy, If I use following for NOX then would it be ok? , I have doubt because we are getting for amd only not for intel separately. My processor is of Intel. http://releases.ubuntu.com/lucid/ ubuntu-10.04.3-desktop-amd64.iso http://releases.ubuntu.com/lucid/ubuntu-10.04.3-desktop-amd64.iso Can you please tell what are you using and tested with NOX destiny? Along with that please confirm is it safe to use destiny branch for all features of openflow 1.0, as saw it unstable branch? Thanks Regards, Sheili Mittal From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 15:00 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX for 64 bit Probably no major problems, but there might be minor ones. I honestly don't remember; I have not run zaku in quite some time. Unless you're already running it, there are only a few good reasons to run zaku now. -- Murphy On Jan 16, 2012, at 1:01 AM, Sheili Mittal wrote: Thanks Murphy Please confirm for NOX 0.9 zaku as well? Regards, Sheili From: Murphy McCauley [mailto:jam...@nau.edu] Sent: 16 January 2012 14:29 To: Sheili Mittal Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX for 64 bit destiny is routinely run on both 32 and 64 bit systems. -- Murphy On Jan 16, 2012, at 12:52 AM, Sheili Mittal wrote: Hi, Can you please confirm are the branch available on git (0.9 zaku) and destiny supported for 64 bit machine also? Are the version we downloading from git is for 32bit and 64 bit both? Thanks Regards, Sheili Mittal DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . --- DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ---___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
