headers
Harkeerat Bedi | 2 Jan 2012 09:00
Favicon

Regarding implementing Click on Linksys routers

Hello all,

I am currently using Click as part of my research project. I have created a
few Click elements which I am able to run on my computer in Linux in
user-level. I am interested in porting/running my Click implementation on a
commercial router, like Linksys WRT54G. I was trying to look for tutorials
and/or documentation regarding this subject, but was not able to find any.
Is there a standard way for performing such a task? Or, can anyone help me
with some documentation or links which I can use for the same?

I am a novice in this area and any help would be highly appreciated. Thank
you in advance.

Regards,
Harkeerat Bedi
Permalink | Reply | 3 comments |
headers
Bart Braem | 3 Jan 2012 10:39
Picon

Re: Regarding implementing Click on Linksys routers

Hello,

You should first look into tutorials for running a custom Linux distribution on your routers e.g., with OpenWRT.
Once you can install your own code on the routers, installing and running Click should be similar to other
software running on your router.

best regards,
Bart

On 02 Jan 2012, at 09:00, Harkeerat Bedi wrote:

> Hello all,
> 
> I am currently using Click as part of my research project. I have created a
> few Click elements which I am able to run on my computer in Linux in
> user-level. I am interested in porting/running my Click implementation on a
> commercial router, like Linksys WRT54G. I was trying to look for tutorials
> and/or documentation regarding this subject, but was not able to find any.
> Is there a standard way for performing such a task? Or, can anyone help me
> with some documentation or links which I can use for the same?
> 
> I am a novice in this area and any help would be highly appreciated. Thank
> you in advance.
> 
> Regards,
> Harkeerat Bedi
> _______________________________________________
> click mailing list
> click <at> amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
(Continue reading)

Permalink | Reply | 0 comments |
headers
Roberto Riggio | 3 Jan 2012 11:48
Favicon

Re: Regarding implementing Click on Linksys routers

Hi,

give a look at OpenWRT, it is a linux distribution for wireless routers 
such as the Linksys wrt54g. It comes with an extensive package 
repository which also include a click package compiled with the wireless 
elements for userspace.

After you flashed you router wih openwrt your will be able to install 
click with:

opkg update && opkg install click

Anyway you will probably want to learn how to compile YOUR version of 
click with YOUR elements. In order to do so, follow the documentation:

http://wiki.openwrt.org/doc/start

R.

On 02/01/2012 09:00, Harkeerat Bedi wrote:
> Hello all,
>
> I am currently using Click as part of my research project. I have created a
> few Click elements which I am able to run on my computer in Linux in
> user-level. I am interested in porting/running my Click implementation on a
> commercial router, like Linksys WRT54G. I was trying to look for tutorials
> and/or documentation regarding this subject, but was not able to find any.
> Is there a standard way for performing such a task? Or, can anyone help me
> with some documentation or links which I can use for the same?
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Harkeerat Bedi | 4 Jan 2012 09:51
Favicon

Re: Regarding implementing Click on Linksys routers

Thank you both Roberto and Bart for your feedback and the link. It's highly
appreciated. I will look into this.

Regards,
Harkeerat Bedi

On Tue, Jan 3, 2012 at 4:48 AM, Roberto Riggio <
roberto.riggio <at> create-net.org> wrote:

> Hi,
>
> give a look at OpenWRT, it is a linux distribution for wireless routers
> such as the Linksys wrt54g. It comes with an extensive package
> repository which also include a click package compiled with the wireless
> elements for userspace.
>
> After you flashed you router wih openwrt your will be able to install
> click with:
>
> opkg update && opkg install click
>
> Anyway you will probably want to learn how to compile YOUR version of
> click with YOUR elements. In order to do so, follow the documentation:
>
> http://wiki.openwrt.org/doc/start
>
> R.
>
> On 02/01/2012 09:00, Harkeerat Bedi wrote:
> > Hello all,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Josh J | 7 Jan 2012 21:25
Picon

Re: click router package - multicast. fatal error: linux/skbuff.h: No such file or directory

Hi,

Any suggestions on how to compile the mulicast click-package ?

https://github.com/kohler/click-packages

Thanks,
Josh

On Wed, Dec 14, 2011 at 10:46 AM, Josh J <joshjdevl <at> gmail.com> wrote:

> Hi,
>
> I have the latest click router code compiled and installed on ubuntu. I am
> trying to install the multicast package, though receive fatal error:
> linux/skbuff.h: No such file or directory
>
> If I search for skbuff.h I can find it in
> /usr/src/linux-headers-2.6.35-30/include/linux/skbuff.h
> /usr/src/linux-headers-2.6.35-30-generic/include/linux/skbuff.h
> /usr/local/include/click-linuxmodule/include1/linux/skbuff.h
>
> Though click build is looking in
> make[2]: Entering directory `/usr/src/linux-headers-2.6.35-30-generic'
>
> Any ideas?
>
>
> make -R CLICK_PACKAGE_MAKING=userlevel multicast.uo
> make[1]: Entering directory
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eddie Kohler | 9 Jan 2012 18:48
Picon
Gravatar

Re: click router package - multicast. fatal error: linux/skbuff.h: No such file or directory

Hi Josh,

Sorry for not getting back to you earlier. This was a problem introduced 
recently in mainline Click. I just checked in what I think is a fix. Try 
updating your Click, re-installing it, and then building the multicast 
package.

Best,
Eddie

On 1/7/12 3:25 PM, Josh J wrote:
> Hi,
>
> Any suggestions on how to compile the mulicast click-package ?
>
> https://github.com/kohler/click-packages
>
> Thanks,
> Josh
>
> On Wed, Dec 14, 2011 at 10:46 AM, Josh J<joshjdevl <at> gmail.com>  wrote:
>
>> Hi,
>>
>> I have the latest click router code compiled and installed on ubuntu. I am
>> trying to install the multicast package, though receive fatal error:
>> linux/skbuff.h: No such file or directory
>>
>> If I search for skbuff.h I can find it in
>> /usr/src/linux-headers-2.6.35-30/include/linux/skbuff.h
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eddie Kohler | 9 Jan 2012 18:57
Picon
Gravatar

Re: click-elem2man crashes in PlanetLab Europe nodes

Hi Christos,

Well, badly compiled perls stink. I rewrote this code; maybe that will 
allow installation. In future if you still have problems what you should 
just do is disable the installation of man pages, by editing 
doc/Makefile.in.

Eddie

On 12/16/11 1:04 PM, Christos Tsilopoulos wrote:
> Hello,
>
> I 've been trying to install click in several Planetlab Europe (PLE)
> nodes without success. I 've tried with both v2.0.1 and the latest from
> git. The source compiles (make works) but failed to be installed. The
> output I get during make install is the following
>
> make[1]: Entering directory `/home/auebple_PSI/click-git/doc'
>     INSTALLMANPAGES /usr/local/share/man
>     CLICK-ELEM2MAN -d /usr/local/share/man/mann
> Modification of a read-only value attempted at ./click-elem2man line 231.
> make[1]: *** [install-man] Error 25
>
> If I understand correctly, the crash occurs while executing the
> click-elem2man perl script. It reports line 231 which is the first line
> of this function
>
> sub nroff_manref ($$$$) {
>       map { $_ = "\"$_\"" if (s/\"/\\(dq/g) }  <at> _; /* LINE 231 */
>       my($x);
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eddie Kohler | 9 Jan 2012 19:05
Picon
Gravatar

Re: Patch for nanosecond scheduling precision in ns-3-click

Hi Lalith,

This change looks generally good, but surely ns defines some version 
variables that we can use to detect whether "cursimnode->curtime" is a 
timespec or a timeval. If it doesn't, then please add one: #define 
NS_CURTIME_IS_TIMESPEC 1. Then Click can be made to work cleanly with 
either, for instance:

#if NS_CURTIME_IS_TIMESPEC
   *ts = cursimnode->curtime;
#else
   ts->tv_sec = cursimnode->curtime.tv_sec;
   ts->tv_nsec = cursimnode->curtime.tv_usec * 1000;
#endif

The timer scheduling code in routerthread.cc would also need a fork: #if 
CLICK_NS && NS_CURTIME_IS_TIMESPEC /timespec-code/ #elif CLICK_NS 
/timeval-code/ #endif.

Make sense?

Sascha, did you end up trying this?
Eddie

On 12/31/11 7:46 AM, Lalith Suresh wrote:
> Hello all,
>
> After Sascha raised this issue on the ns-3-users list [1], I tried
> making a quick patch to make Click's NS code use timespec, and make
> the corresponding changes on the ns-3 side as well.
(Continue reading)

Permalink | Reply | 8 comments |
headers
Eddie Kohler | 9 Jan 2012 19:19
Picon
Gravatar

Re: Alignment issue

Hi Markku, Cliff,

On reflection, I think the right answer here is to degrade the 
Classifier error to a warning. I did this, and added more context to 
describe the different ways to fix the error.

Eddie

On 11/18/11 11:01 AM, Cliff Frey wrote:
> if you modify click-align.cc to specify that the FromOcteon element
> produces packets that are (4,2) aligned, then you won't get the extra
> Align() element.
>
> If you really want to do what you are asking for, you could likely add
> -DHAVE_INDIFFERENT_ALIGNMENT to CXXFLAGS/CFLAGS, but I'm not positive if
> that would work.  I'd definitely recommend just keeping click-align.cc up
> to date with your elements.
>
> Cliff
>
> On Fri, Nov 18, 2011 at 12:45 AM, Markku Savela<Markku.Savela <at> vtt.fi>wrote:
>
>> When configuring for mips 64, it does not set the
>>
>>   HAVE_INDIFFERENT_ALIGNMENT
>>
>> in include/click/config.h.
>>
>> This is fine, but it does trouble me that click doesn't
>> even run the configuration without it being passed through
(Continue reading)

Permalink | Reply | 1 comment |
headers
Eddie Kohler | 9 Jan 2012 19:22
Picon
Gravatar

Re: Cross compile click packages

Hi Sascha, sorry for my own late reply.

Well, this code used to work; that is why Click separately checks for 
dynamic linking on the build & host compilers. To figure out this error 
I'd need to see the config.log.

Unfortunately click-mkmindriver does not work with packages.

Eddie

On 12/3/11 6:36 PM, Sascha Alexander Jopen wrote:
> Hey,
>
> sorry for this really late reply.
>
> Cross compiling click packages with your modifications of the build
> system seems to work. I managed to compile and run several packages for
> a mipsel architecture.
>
> However this will only work with --enable-tools=host.
> --enable-tools=mixed leads to the following error during the configure
> phase. I currently use different cxx libraries on the build and host
> systems. But even when using the standard gcc cxx library, i couldn't
> compile mixed tools.  Both the build system and the target system do
> support dynamic linking, so this might be a problem with mixed
> build/host include and library directories.
>
> checking dlfcn.h usability... no
> checking dlfcn.h presence... yes
> configure: WARNING: dlfcn.h: present but cannot be compiled
(Continue reading)

Permalink | Reply | 2 comments |

Gmane