[nox-dev] Queue configuration
Hi,
Does OVS support queue configuration for the physical ports of a switch? I
have ovs-openflowd running in userspace on a Linux box (32-bit Ubuntu 10.10)
and I send it an Openflow message of type OFPT_QUEUE_GET_CONFIG_REQUEST from
the controller (NOX 0.9 Zaku). The OVS installation I am using is the latest
version, checked out from git a couple of days back.
Here is a code snippet, from my NOX code, showing how I send the request:
Disposition datapath_join_handler(const Event e)
{
const Datapath_join_event dpi = assert_castconst
Datapath_join_event(e);
lg.dbg(New datapath joined %s with %d ports\n,
dpi.datapath_id.string().c_str(), dpi.ports.size());
std::vectorPort::const_iterator iter;
for(iter = dpi.ports.begin(); iter != dpi.ports.end(); iter++)
{
std::cout(*iter)std::endl;
}
struct ofp_queue_get_config_request ofqc;
ofqc.header.version = OFP_VERSION;
ofqc.header.type = OFPT_QUEUE_GET_CONFIG_REQUEST;
ofqc.header.length = htons(sizeof (struct
ofp_queue_get_config_request));
ofqc.port = htons(1);
send_openflow_command(dpi.datapath_id, ofqc.header, true);
return CONTINUE;
}
I get the following output at the controller:
samehdi@ubuntu:~/Networks-Research/nox/build/src$ ./nox_core -i ptcp:6633
qostest
NOX 0.9.0(zaku)~full~beta (nox_core), compiled Feb 23 2011 18:49:20
Compiled with OpenFlow 0x01
3(eth2): 00:21:9b:79:db:08 speed: 1000 config: 0 state: 0 curr: 2a0
advertised: 2af supported: 2af peer: 0
2(eth1): 00:50:04:b1:f5:09 speed: 64 config: 0 state: 0 curr: 208
advertised: 28f supported: 28f peer: 0
fffe(br0): 12:d2:5b:7f:58:2d speed: a config: 0 state: 0 curr: 82
advertised: 0 supported: 0 peer: 0
1(eth0): 00:01:02:13:48:20 speed: a config: 0 state: 1 curr: 201 advertised:
28f supported: 28f peer: 0
1|openflow-event|ERR:received Openflow error packet from
dpid=00232084d7d2: type=1, code=1, 12 bytes of data
The error type and code are for OFPET_BAD_REQUEST and OFP_BAD_TYPE, so I am
wondering whether OVS supports queue configuration.
---
Regards,
Syed Akbar Mehdi,
School of EECS (SEECS),
National University of Sciences and Technology (NUST),
Pakistan.
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] NOX Error
Thanks Murphy, Kyriakos. That is exactly the problem. Actually the data I am using has about 1400 TCP connection initiations. Whenever a SYNACK is received, I set the flow specifically for that connection with an idle timeout of 1 sec. The data is for almost a whole day and most of these flows are short-lived. I dumped the flow table at one point while the datapath was complaining with the flow table full message and there were 57 flows. The spec does not say anything about the maximum number of flows in a table (or at least I could not find that). Also, all the flows that I am adding are going into table 1, which might be because of the fact that all of them have the same priority. Regards, Akbar On Wed, Jan 12, 2011 at 7:15 PM, Murphy McCauley jam...@nau.edu wrote: I think type 3 code 0 is failure to add a flow because you already have too many, but you can look it up in the OpenFlow specification. The data that goes with an error depends on the error. In the case of failure to add a flow, I think it just returns the flow mod message to you (or at least the beginning of it). In zaku, I think the data just gets thrown away, but I recently pushed a patch that lets you retrieve it in destiny. I have a vague memory that the data count might also include the error packet size or something, so if you're using C++ you should watch out for that (I think in Python you can just len() the buffer and get the right answer). -- Murphy On Jan 12, 2011, at 5:45 AM, Syed Akbar Mehdi wrote: Hi, While running some captured network data through an openflow switch running on a Linux box, I get the following error messages at the controller: 00015|openflow-event|ERR:received Openflow error packet from dpid=002320b77f72: type=3, code=0, 80 bytes of data What is meant by the type = 3, code = 0 ? Also does the 80 bytes mean that the packet at the switch that caused it to send this error to the controller was 80 bytes in size? -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
[nox-dev] Event handling order
Hi, Is there some way to impose an order between various components with regards to how an event is handled? e.g. if I want to say that Component A should always get a Packet_in_event before Component B, is that possible? -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Event handling order
Thanks Kyriakos. This is exactly what I was looking for. On Thu, Dec 23, 2010 at 12:41 AM, Kyriakos Zarifis kyr.zari...@gmail.comwrote: Hi Syed, please take a look here http://noxrepo.org/noxwiki/index.php/FAQ#How_can_I_affect_the_order_that_different_components_handle_events.3F On Wed, Dec 22, 2010 at 9:34 PM, Syed Akbar Mehdi akbar.me...@seecs.nust.edu.pk wrote: Hi, Is there some way to impose an order between various components with regards to how an event is handled? e.g. if I want to say that Component A should always get a Packet_in_event before Component B, is that possible? -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Is flow mod event misleading?
I see. So the Barrier( ) is more of an operation which ensures that all messages until that point have been taken care of (usually without dropping). The spec gives the impression that it is more equivalent to a transaction commit (the barrier reply message actually carries a xid). Probably that should be clarified in there. Thanks. -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. On Mon, Dec 20, 2010 at 12:42 PM, kk yap yap...@stanford.edu wrote: Oops.. typos. One can interpret finish processing as having dropped. I am *not* suggesting we do, but this is apparently not an impossibility. It is a rare event nonetheless. On 19 December 2010 23:41, kk yap yap...@stanford.edu wrote: Hi Syed, One can interpret finish processing as having dropped. I am suggesting we do, but this is apparently not a impossibility. It is a rare event nonetheless. Regards KK On 19 December 2010 23:37, Syed Akbar Mehdi akbar.me...@seecs.nust.edu.pk wrote: Hi KK, Thanks for detailed explanation. However this conflicts somewhat with the OpenFlow Spec v1.0. In section 5.3.7 (page 36) of the OpenFlow1.0 spec it is written that: Upon receipt, the switch must finish processing all previously received messages before executing any messages beyond the Barrier Request. -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. On Mon, Dec 20, 2010 at 12:18 PM, kk yap yap...@stanford.edu wrote: Hi Syed, The barrier function is only there to tell you that a preceding message is processed (i.e., the command is carried out, dropped or error code is returned). So, you can imagine if you want to check the flow mod is inserted or not, you can do the following: 1) send flow mod 2) send barrier request 3) send flow stat after receiving barrier reply This ensures that the flow mod is processed by the switch already. Switch can choose to process messages out of order of what is received, except for the barrier message. Hope this is clearer. Regards KK On 19 December 2010 22:53, Syed Akbar Mehdi akbar.me...@seecs.nust.edu.pk wrote: Hi KK, You say that: Meaning, it is perfectly okay for a switch to send a reply to the barrier and ignore the flow mod before that. How is the barrier reply useful then, if it does not guarantee this? -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. On Mon, Dec 20, 2010 at 10:38 AM, kk yap yap...@stanford.edu wrote: Hi Derek, Some comments inline. Hope they help. Regards KK On 19 December 2010 21:10, Derek Cormier derek.corm...@lab.ntt.co.jp wrote: I noticed that the flow mod event fires in response to a successful NOX API call for adding a flow. It gives the impression that it was successfully added to the switch, but, this is not always the case. For example, if I send two identical ofp_flow_mod requests with the OFPFF_CHECK_OVERLAP flag set, then I will still get a flow mod, even though one triggers an error and is not added to the switch's table. A flow mod event is triggered whenever a flow_mod is sent by a component. As you have noticed, multiple comments can be sending flow mods and this is a way for a component to see all the flow mods sent. That's all. It does not imply NOX has sent the message, and even less if the switch has received it or processed it. I'm guessing the reason for this is speed. Since OpenFlow switches do not reply to flow mod requests, there are a couple ways I can think of to confirm if a flow was added: 1. Send a barrier message after each add flow message. If a reply is received and no error message was received, then it was added. Most of the time, you are right. While OpenFlow messages are carried over TCP and SSL connections, there is no guarantee that a switch will honor all the messages. Meaning, it is perfectly okay for a switch to send a reply to the barrier and ignore the flow mod before that. This is really because a switch can be overwhelmed by control messages and at some point it might discard messages. Your flow mod might just be the unlucky message dropped. 2. Store an internal copy of the flow table in the NOX component and check for potential errors before adding. Yes. This is prudent but unfortunately tedious. This allows assume you emulate the entire switch functionality in the controller. By the way, you still will not have any guarantees about the switch inserting the flow mod, as I have explained above. Both of these solutions have problems if other components are also adding
Re: [nox-dev] Is flow mod event misleading?
Hi KK, Thanks for detailed explanation. However this conflicts somewhat with the OpenFlow Spec v1.0. In section 5.3.7 (page 36) of the OpenFlow1.0 spec it is written that: Upon receipt, the switch must finish processing *all* previously received messages before executing any messages beyond the Barrier Request. -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. On Mon, Dec 20, 2010 at 12:18 PM, kk yap yap...@stanford.edu wrote: Hi Syed, The barrier function is only there to tell you that a preceding message is processed (i.e., the command is carried out, dropped or error code is returned). So, you can imagine if you want to check the flow mod is inserted or not, you can do the following: 1) send flow mod 2) send barrier request 3) send flow stat after receiving barrier reply This ensures that the flow mod is processed by the switch already. Switch can choose to process messages out of order of what is received, except for the barrier message. Hope this is clearer. Regards KK On 19 December 2010 22:53, Syed Akbar Mehdi akbar.me...@seecs.nust.edu.pk wrote: Hi KK, You say that: Meaning, it is perfectly okay for a switch to send a reply to the barrier and ignore the flow mod before that. How is the barrier reply useful then, if it does not guarantee this? -- Regards, Syed Akbar Mehdi, School of EECS (SEECS), National University of Sciences and Technology (NUST), Pakistan. On Mon, Dec 20, 2010 at 10:38 AM, kk yap yap...@stanford.edu wrote: Hi Derek, Some comments inline. Hope they help. Regards KK On 19 December 2010 21:10, Derek Cormier derek.corm...@lab.ntt.co.jp wrote: I noticed that the flow mod event fires in response to a successful NOX API call for adding a flow. It gives the impression that it was successfully added to the switch, but, this is not always the case. For example, if I send two identical ofp_flow_mod requests with the OFPFF_CHECK_OVERLAP flag set, then I will still get a flow mod, even though one triggers an error and is not added to the switch's table. A flow mod event is triggered whenever a flow_mod is sent by a component. As you have noticed, multiple comments can be sending flow mods and this is a way for a component to see all the flow mods sent. That's all. It does not imply NOX has sent the message, and even less if the switch has received it or processed it. I'm guessing the reason for this is speed. Since OpenFlow switches do not reply to flow mod requests, there are a couple ways I can think of to confirm if a flow was added: 1. Send a barrier message after each add flow message. If a reply is received and no error message was received, then it was added. Most of the time, you are right. While OpenFlow messages are carried over TCP and SSL connections, there is no guarantee that a switch will honor all the messages. Meaning, it is perfectly okay for a switch to send a reply to the barrier and ignore the flow mod before that. This is really because a switch can be overwhelmed by control messages and at some point it might discard messages. Your flow mod might just be the unlucky message dropped. 2. Store an internal copy of the flow table in the NOX component and check for potential errors before adding. Yes. This is prudent but unfortunately tedious. This allows assume you emulate the entire switch functionality in the controller. By the way, you still will not have any guarantees about the switch inserting the flow mod, as I have explained above. Both of these solutions have problems if other components are also adding flows. Does anyone have any other ideas? In my mind, the obvious way to do this is hard and evil. You have to send the flow mods, cache it in the controller and periodically dump the flow table to check that it is there. This can be done in conjunction with other operations like stat gathering, but the operation can be very stressful to a switch. It would be nice if the OpenFlow protocol had responses to flow mod requests that could be optionally turned on/off for speed. We have been through this discussion a few times in OpenFlow. And current result is that we still don't have it in the spec, even for the upcoming OpenFlow v1.1. -Derek ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
[nox-dev] Setting up flows at startup
Hi, I am writing Nox components using C++. I want to install some 'default' flows at startup (e.g. if I want to say that all ARP packets should be sent to the controller). I understand that I should probably put the relevant code in either configure() or install() (which one should it be?). How do I get the IDs of all datapaths that are connected to the controller when initialize() or configure() is called for a component? Regards, Akbar ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] Setting up flows at startup
Thanks Murphy. This makes more sense, since datapaths may connect and leave at various times. On Thu, Dec 16, 2010 at 4:38 PM, Murphy McCauley jam...@nau.edu wrote: Welcome to nox-dev, Akbar. You should actually do this when the switches connect (in response to the datapath join event) rather than at NOX/component startup, as the switches won't have connected at that point. -- Murphy On Dec 16, 2010, at 3:19 AM, Syed Akbar Mehdi wrote: Hi, I am writing Nox components using C++. I want to install some 'default' flows at startup (e.g. if I want to say that all ARP packets should be sent to the controller). I understand that I should probably put the relevant code in either configure() or install() (which one should it be?). How do I get the IDs of all datapaths that are connected to the controller when initialize() or configure() is called for a component? Regards, Akbar ___ 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] Forwarding to controller ... datapath crashes
Hi, I having problems with setting a flow with action to forward packets to the controller, while running a virtual network using NOX(0.9.0 Zaku) and OpenFlowVMS (v1.0). I ran a simple test using the hub component in NOX. I changed the value of action.port on line 90 of hub.cc to OFPP_CONTROLLER instead of OFPP_FLOOD. I then used this updated hub in a simple virtual network created using OpenFlowVMS, consisting of two hosts connected to a single datapath. When I try to ping one host from the other, the controller gets the packet and tries to install a flow on the datapath with the OFPP_CONTROLLER port in the action.port field. At this time the datapath crashes. Here is the output I get in the virtual machine: qemu:~# ofdatapath: lib/ofpbuf.c:168: ofpbuf_prealloc_headroom: Assertion `size = ofpbuf_headroom(b)' failed. Dec 16 12:06:31|2|fault|EMER|Caught signal 6. 0x0805793f 0xe400 (__kernel_sigreturn+0x0) 0xb7e8fd88 (abort+0x188) 0xb7e87590 (__assert_fail+0xf0) 0x0805a789 0x0805a7ae (ofpbuf_push_uninit+0x1e) 0x08051223 (dp_output_control+0x53) 0x08052191 0x0805331c (dp_run+0x3bc) 0x080545b5 (main+0x545) 0xb7e7a455 (__libc_start_main+0xe5) modprobe: FATAL: Could not load /lib/modules/2.6.27-rc1/modules.dep: No such file or directory Dec 16 12:06:31|00014|netdev|ERR|ioctl(SIOCGIFFLAGS) on tap0 device failed: No such device Dec 16 12:06:31|00015|port_watcher|WARN|could not get flags for tap0 Dec 16 12:06:31|00016|rconn|INFO|unix:/tmp/ofsw: connection closed by peer Dec 16 12:06:32|00017|rconn|INFO|unix:/tmp/ofsw: connecting... Dec 16 12:06:32|00018|vconn_unix|ERR|/tmp/vconn-unix.1030.2: connection to /tmp/ofsw failed: Connection refused Dec 16 12:06:32|00019|rconn|WARN|unix:/tmp/ofsw: connection failed (Connection refused) Dec 16 12:06:32|00020|rconn|INFO|unix:/tmp/ofsw: waiting 2 seconds before reconnect Dec 16 12:06:34|00021|rconn|INFO|unix:/tmp/ofsw: connecting... Regards, Akbar ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] problem with swig
I encountered the same configure: error: Could not link against !. Try installing the libboost-all-dev as well as boost-build packages. Maybe this is overkill but, in my case it made this error go away. sudo aptitude install boost-build libboost-all-dev --Akbar On Mon, Dec 6, 2010 at 9:06 PM, majum...@cse.unl.edu wrote: Output of uname -a: Linux Ubuntu10VM 2.6.32-26-generic #48-Ubuntu SMP Wed Nov 24 09:00:03 UTC 2010 i686 GNU/Linux Output of cat /etc/issue: Ubuntu 10.04.1 LTS \n \l Can you send the config.log file from your build directory, as well as the output from uname -a and cat /etc/issue ? -- Murphy On Dec 6, 2010, at 6:51 AM, Abhishek Majumdar wrote: I still got that configure : error: could not link against ! Thanks Abhishek Majumdar On 12/6/2010 8:43 AM, Murphy McCauley wrote: The information on that page is long out of date. The noxrepo wiki (http://noxrepo.org/noxwiki) is much more in line with reality. The packages listed on that page are for Debian, and the NOX it has you fetch is no longer 0.6.0. Please try the following (copy/pasted from the noxrepo wiki), and then re-run ../configure: sudo apt-get install autoconf automake g++ libtool swig make git-core libboost-test-dev libboost-filesystem-dev libssl-dev libpcap-dev python-twisted python-simplejson python-dev -- Murphy On Dec 6, 2010, at 6:36 AM, majum...@cse.unl.edu wrote: BTW I'm using the tutorial given at http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup So I'm using NOX 0.6 Thanks Abhishek Can you please post the results of running apt-get install swig and also the results of running ../configure ? Also, which version of NOX are you using? -- Murphy On Dec 5, 2010, at 11:44 PM, Abhishek Majumdar wrote: Its Linux Ubuntu10Vm 2.6.32-25-generic. I separately installed everything and in /nox/build when i do ../configure it recognizes and then gives configure: error: Could not link against ! Thanks Abhishek Majumdar On 12/5/2010 10:35 PM, kk yap wrote: Hi Abhishek, Let's see... Try make install and ldconfig? Jokes aside, please let us know your OS, distro, etc. for anyone to give advice. It works perfectly on Ubuntu (Lucid Lynx) for me. In fact, we have a pseudo-package that installs the requisites using apt-get. Regards KK On 5 December 2010 20:24, Abhishek Majumdarmajum...@cse.unl.edu wrote: When I try to install the pre-requisites, it says swig package cannot be found. I separately installed libboost, it can now detect, but cannot link i guess. please help ASAP. -- Thanks Abhishek Majumdar ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
Re: [nox-dev] problem with swig
Actually in my case, libboost-dev did not work. I had to use libboost-all-dev to make the error go away. On Tue, Dec 7, 2010 at 6:45 AM, Murphy McCauley jam...@nau.edu wrote: Glad to hear it! Did you try it with just libboost-dev, or did you use libboost-all-dev? If it's the former, I'd like to update the wiki (if it's the latter, I'll have to look into it more). :) -- Murphy On Dec 6, 2010, at 3:28 PM, Abhishek Majumdar wrote: It works now. Thanks a lot. Abhishek Majumdar On 12/6/2010 2:13 PM, Murphy McCauley wrote: Yeah, I think this will probably work. apt-get install libboost-dev might also do the trick (and not be overkill). -- Murphy On Dec 6, 2010, at 12:07 PM, Syed Akbar Mehdi wrote: I encountered the same configure: error: Could not link against !. Try installing the libboost-all-dev as well as boost-build packages. Maybe this is overkill but, in my case it made this error go away. sudo aptitude install boost-build libboost-all-dev --Akbar On Mon, Dec 6, 2010 at 9:06 PM, majum...@cse.unl.edu wrote: Output of uname -a: Linux Ubuntu10VM 2.6.32-26-generic #48-Ubuntu SMP Wed Nov 24 09:00:03 UTC 2010 i686 GNU/Linux Output of cat /etc/issue: Ubuntu 10.04.1 LTS \n \l Can you send the config.log file from your build directory, as well as the output from uname -a and cat /etc/issue ? -- Murphy On Dec 6, 2010, at 6:51 AM, Abhishek Majumdar wrote: I still got that configure : error: could not link against ! Thanks Abhishek Majumdar On 12/6/2010 8:43 AM, Murphy McCauley wrote: The information on that page is long out of date. The noxrepo wiki (http://noxrepo.org/noxwiki) is much more in line with reality. The packages listed on that page are for Debian, and the NOX it has you fetch is no longer 0.6.0. Please try the following (copy/pasted from the noxrepo wiki), and then re-run ../configure: sudo apt-get install autoconf automake g++ libtool swig make git-core libboost-test-dev libboost-filesystem-dev libssl-dev libpcap-dev python-twisted python-simplejson python-dev -- Murphy On Dec 6, 2010, at 6:36 AM, majum...@cse.unl.edu wrote: BTW I'm using the tutorial given at http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup So I'm using NOX 0.6 Thanks Abhishek Can you please post the results of running apt-get install swig and also the results of running ../configure ? Also, which version of NOX are you using? -- Murphy On Dec 5, 2010, at 11:44 PM, Abhishek Majumdar wrote: Its Linux Ubuntu10Vm 2.6.32-25-generic. I separately installed everything and in /nox/build when i do ../configure it recognizes and then gives configure: error: Could not link against ! Thanks Abhishek Majumdar On 12/5/2010 10:35 PM, kk yap wrote: Hi Abhishek, Let's see... Try make install and ldconfig? Jokes aside, please let us know your OS, distro, etc. for anyone to give advice. It works perfectly on Ubuntu (Lucid Lynx) for me. In fact, we have a pseudo-package that installs the requisites using apt-get. Regards KK On 5 December 2010 20:24, Abhishek Majumdarmajum...@cse.unl.edu wrote: When I try to install the pre-requisites, it says swig package cannot be found. I separately installed libboost, it can now detect, but cannot link i guess. please help ASAP. -- Thanks Abhishek Majumdar ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
