unsubscribe On Thu, Mar 24, 2011 at 10:28 AM, <[email protected]> wrote:
> Send nox-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://noxrepo.org/mailman/listinfo/nox-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nox-dev digest..." > > > Today's Topics: > > 1. Re: setting nox configuration files (James "Murphy" McCauley) > 2. The specification about nox (linbo) > 3. Re: The specification about nox (James "Murphy" McCauley) > 4. Re: nox fails to build on ubuntu 11.04 (tablog.cc fails to > compile) (James "Murphy" McCauley) > 5. Re: Problem about sending first packet of a flow in Python > (Kyle Wang) > 6. Installing datapath flow with pyswitch.py (Harry) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 23 Mar 2011 16:17:05 -0700 > From: "James \"Murphy\" McCauley" <[email protected]> > Subject: Re: [nox-dev] setting nox configuration files > To: John Meylor <[email protected]> > Cc: [email protected] > Message-ID: <1300922225.20808.116.camel@meowth> > Content-Type: text/plain; charset="UTF-8" > > So for reference, the log formatting looks like: > <num>|<module>|<level>:message > > The log settings are in the form: > <module>:<facility>:<level> > > module is the name of a component or other module. Something like "nox" > or "pyrt" or "pyswitch", for example. "ANY" is a special string which > matches every module. > > facility is the logging facility. The ones currently in NOX are > "syslog" and "console". Again, "ANY" is a special string which matches > all facilities. > > level is the minimum log level that you want logged. From most to least > significant, these are: EMER, ERR, WARN, INFO, DBG. > > You can include multiple of these. For example: > --verbose=ANY:ANY:DBG --verbose=pyswitch:ANY:EMER > > .. should turn on debug level logging for everything except pyswitch, > which will only log emergency info. > > -v (or --verbose) is basically a shortcut for ANY:ANY:DBG in current > versions of NOX, I believe. In future versions, I think it will be more > like ANY:ANY:INFO. Including it twice (-v -v) will give the older > ANY:ANY:DBG behavior. > > > At the moment, the only way to specify this stuff is through the > commandline. The code to let you specify it in nox.json has been > written, but I don't think I've pushed it yet. It'll show up in destiny > in the next couple weeks. Basically, it adds a "logging" key which > contains an array of maps which contain combinations of the keys > "module", "facility", and "level". So for example, if you wanted to do > the same as the commandline above, your nox.json might look like: > { > "nox" : { > "logging" : [ > { "level" : "DBG" }, > { "module" : "pyswitch", "level" : "EMER" } > ] > ... more stuff ... > } > } > > > I don't know if you were interested in OTHER stuff in the main config > file too. I think the only other thing in there is the event ordering > stuff, which is described on the wiki, I believe. > > > Hope that helps. > > -- Murphy > > On Wed, 2011-03-23 at 14:33 -0400, John Meylor wrote: > > I'm looking for information on setting configuration files and verbosity > levels for nox. The flag options are mentioned in the help menu, but I can't > find any further information on the required JSON syntax and flags. > > > > Thanks > > John > > > > ./nox_core --help > > Other options: > > -c, --conf=FILE set configuration file > > -n, --info=FILE set controller info file > > -v, --verbose set maximum verbosity level (for console) > > -v, --verbose=CONFIG configure verbosity > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > > ------------------------------ > > Message: 2 > Date: Thu, 24 Mar 2011 12:23:12 +0800 > From: "linbo" <[email protected]> > Subject: [nox-dev] The specification about nox > To: "nox-dev" <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="gb2312" > > > Is there any specification about nox ?Just like that about openflow > Thanks. > > 2011-03-24 > > > > linbo > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://noxrepo.org/pipermail/nox-dev/attachments/20110324/a27fd855/attachment-0001.htm > > > > ------------------------------ > > Message: 3 > Date: Wed, 23 Mar 2011 21:23:47 -0700 > From: "James \"Murphy\" McCauley" <[email protected]> > Subject: Re: [nox-dev] The specification about nox > To: linbo <[email protected]> > Cc: nox-dev <[email protected]> > Message-ID: <1300940627.20808.435.camel@meowth> > Content-Type: text/plain; charset="UTF-8" > > Nope. I think it's easier to specify a protocol than a software > platform or whatever you want to call NOX, and I don't think a real > specification has ever been much of a priority. I think the closest > thing we have is the doxygen documentation. > > -- Murphy > > On Thu, 2011-03-24 at 12:23 +0800, linbo wrote: > > > > Is there any specification about nox ?Just like that about openflow > > Thanks. > > > > 2011-03-24 > > > > ______________________________________________________________________ > > linbo > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > > ------------------------------ > > Message: 4 > Date: Wed, 23 Mar 2011 21:47:20 -0700 > From: "James \"Murphy\" McCauley" <[email protected]> > Subject: Re: [nox-dev] nox fails to build on ubuntu 11.04 (tablog.cc > fails to compile) > To: David Meyer <[email protected]> > Cc: [email protected] > Message-ID: <1300942040.20808.482.camel@meowth> > Content-Type: text/plain; charset="UTF-8" > > I think you have boost_filesystem 1.44 or above installed. I believe > NOX currently works fine with semi-recent versions up to 1.40, and > possibly has very minor problems with 1.42 (maybe only on 64 bit?). I > think these versions are what are in recent Ubuntu, even up through > 11.04b3. > > Potential ways of fixing this: > > 1) Roll back to boost_filesystem 1.40/1.42 (I'm not sure how you even > got 1.44 unless you did this manually, since I don't think Ubuntu has it > packaged in any repository yet). > > 2) Set the preprocessor macro BOOST_FILESYSTEM_VERSION to 2. > > 3) Manually edit tablog.cc. I count three errors: lines 369, 420, and > 426. Each of these calls a function and passes in fs::native as the > last argument. I think you can just remove that argument. > > Hope that helps. > > -- Murphy > > On Fri, 2011-03-18 at 17:13 -0700, David Meyer wrote: > > On 2.6.35-28-server #49-Ubuntu SMP Tue Mar 1 14:55:37 UTC 2011 x86_64 > GNU/Linux: > > ... > > ./../../src/nox/netapps/ -fno-omit-frame-pointer -fno-strict-aliasing > > -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral > > -Wformat-security -g -O2 -MT rttlog_la-rttlog.lo -MD -MP -MF > > .deps/rttlog_la-rttlog.Tpo -c > > ../../../../../src/nox/netapps/tablog/rttlog.cc -fPIC -DPIC -o > > .libs/rttlog_la-rttlog.o > > ../../../../../src/nox/netapps/tablog/tablog.cc: In member function > > ?std::string vigil::tablog::field_value(vigil::tablog::tablog_type, > > void*)?: > > ../../../../../src/nox/netapps/tablog/tablog.cc:214: warning: format > > ?%llu? expects type ?long long unsigned int?, but argument 3 has type > > ?long unsigned int? > > ../../../../../src/nox/netapps/tablog/tablog.cc: In member function > > ?void vigil::tablog::dump_file(const char*, bool, std::string)?: > > ../../../../../src/nox/netapps/tablog/tablog.cc:369: error: invalid > > conversion from ?bool (*)(const std::string&)? to ?void*? > > ../../../../../src/nox/netapps/tablog/tablog.cc:369: error: > > initializing argument 2 of ?boost::filesystem3::path::path(const > > Source&, typename > > boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename > > boost::decay<Source>::type>, void>::type*) [with Source = const > > char*]? > > ../../../../../src/nox/netapps/tablog/tablog.cc: In member function > > ?boost::filesystem3::path vigil::tablog::get_int_path(const char*, > > int)?: > > ../../../../../src/nox/netapps/tablog/tablog.cc:420: error: invalid > > conversion from ?bool (*)(const std::string&)? to ?void*? > > ../../../../../src/nox/netapps/tablog/tablog.cc:420: error: > > initializing argument 2 of ?boost::filesystem3::path::path(const > > Source&, typename > > boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename > > boost::decay<Source>::type>, void>::type*) [with Source = const > > char*]? > > ../../../../../src/nox/netapps/tablog/tablog.cc:426: error: invalid > > conversion from ?bool (*)(const std::string&)? to ?void*? > > ../../../../../src/nox/netapps/tablog/tablog.cc:426: error: > > initializing argument 2 of ?boost::filesystem3::path::path(const > > Source&, typename > > boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename > > boost::decay<Source>::type>, void>::type*) [with Source = const > > char*]? > > make[9]: *** [tablog_la-tablog.lo] Error 1 > > make[9]: *** Waiting for unfinished jobs.... > > mv -f .deps/rttlog_la-rttlog.Tpo .deps/rttlog_la-rttlog.Plo > > mv -f .deps/flowlog_la-flowlog.Tpo .deps/flowlog_la-flowlog.Plo > > make[9]: Leaving directory > `/usr/local/src/nox/build/src/nox/netapps/tablog' > > make[8]: *** [all] Error 2 > > ... > > > > > > Anyone else seeing this? config.log attached. > > > > Thnx, > > > > Dave > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > > ------------------------------ > > Message: 5 > Date: Thu, 24 Mar 2011 21:56:01 +0800 > From: Kyle Wang <[email protected]> > Subject: Re: [nox-dev] Problem about sending first packet of a flow in > Python > To: Murphy McCauley <[email protected]> > Cc: nox-dev <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="gb2312" > > Hi Murphy McCauley, > > Thank your for your reply. As for the questions, 1) Yes, I am dealing with > multiple openvswitches indeed, 2) Yes, they aren't getting to their > intended > destination. All the flow entries for each openvswitch are added > simultaneously when the first packet of a flow is detected, and I want to > use "*self.send_openflow(dpid, bufid, buf, openflow.OFPP_TABLE, inport)*" > to > send this first packet out from the openvswitch which reports this packet. > > > On Wed, Mar 23, 2011 at 6:33 PM, Murphy McCauley <[email protected]> wrote: > > > Hi. Got a couple questions for you. > > > > 1) Are you dealing with multiple switches? > > > > 2) By "dropped" do you just mean they aren't getting to their intended > > destination? If they're supposed to be traversing multiple switches, do > you > > know where along the path they're getting lost? > > > > -- Murphy > > > > On Mar 23, 2011, at 1:56 AM, Kyle Wang wrote: > > > > Hi, > > > > I am experiencing a problem with the first 2 packets of a flow being > > dropped. In my Python program, I used: > > self.send_openflow(dpid, bufid, buf, openflow.OFPP_TABLE, inport) > > to send the first packet after setting the entry with > > self.install_datapath_flow(dpid, flow, CACHE_TIMEOUT, > > openflow.OPF_FLOW_PERMANENT, actions, None, > openflow.OFP_DEFAULT_PRIORITY, > > inport, None) > > > > With the current code, the first packets of a flow are being dropped. Am > I > > doing this correctly or am I missing something used to send the first > > packets correctly. > > > > Thank you for your time and help. > > > > Sincerely, > > > > Kyle > > > > -- > > God Helps Those Who Help Themselves. > > > > Kyle Wang ?? ?? > > ==================================================== > > Ph.D. Student, Department of Automation, Tsinghua University > > Address: Room 3-421, FIT, Tsinghua University, Beijing, China, 100084 > > Phone: 86-1500-123-6466(m) 86-10-6277-2656(o) > > Email: [email protected] > > ==================================================== > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > > > > > > -- > God Helps Those Who Help Themselves. > > Kyle Wang ?? ?? > ==================================================== > Ph.D. Student, Department of Automation, Tsinghua University > Address: Room 3-421, FIT, Tsinghua University, Beijing, China, 100084 > Phone: 86-1500-123-6466(m) 86-10-6277-2656(o) > Email: [email protected] > ==================================================== > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://noxrepo.org/pipermail/nox-dev/attachments/20110324/bb5d13ad/attachment-0001.htm > > > > ------------------------------ > > Message: 6 > Date: Thu, 24 Mar 2011 21:28:23 +0700 > From: Harry <[email protected]> > Subject: [nox-dev] Installing datapath flow with pyswitch.py > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > Hi all, > Anyone could clear me this issue: > I'm playing with the *pyswitch* component built on NOX. I start a single > switch (ovsk switch) network in mininet with 3 hosts (h2,h3,h4), then > start NOX controller with pyswitch. > I ping from h2 to h3, log messages show that the controller successfully > installed datapath flow for the first 3 packets (ARP & ICMP) between h2 > & h3. > Then I exit the controller, of course, I still ping from h2 to h3 > (because datapath flows have been installed on the switch). > *But when I restart the controller and do the ping h2->h3 again, why > does the controller reinstall the datapath flows on the switch? The > datapath flows on the switch seem to be cleared when I restart the > controller. * > > Thank you very much! > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://noxrepo.org/pipermail/nox-dev/attachments/20110324/da6c415f/attachment.htm > > > > ------------------------------ > > _______________________________________________ > nox-dev mailing list > [email protected] > http://noxrepo.org/mailman/listinfo/nox-dev > > > End of nox-dev Digest, Vol 35, Issue 33 > *************************************** > -- With regards, Vishnu D H
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev
