| 384 | | The Click router supports kernel-level operation. The principles are the same, but the setup is a bit more involved. To use kernel-level Click, you will probably want first to develop and debug your setup at the user level. Then, follow the steps above, with these differences: |
| 385 | | |
| 386 | | * Before running '''createsliver''', modify your rspec to delete the '''execute''' tags on your routers. You may also want to add a '''hardware_type''' tag to specify a particular hardware configuration so your performance comparisons are valid and so the next step doesn't take too long. |
| 387 | | |
| 388 | | * After running '''createsliver''', you need to rebuild the kernel on your routers and then build Click with its corresponding kernel module. Log into each router, and run '''sh /local/build-click-kernel.sh''' to patch and build your new kernel. This process will take a while, after which the machine will reboot, and you'll need to log back in. Now build Click with '''sh /local/build-click.sh'''. |
| 389 | | |
| 390 | | * Run '''extractClickConfig.py''' as before (or create your Click configuration by hand), but you'll need to edit the '''deployClick.sh''' script to run Click at the kernel level. You do this by changing '''/usr/local/bin/click <file>''' to '''/usr/local/sbin/click-install <file>''' each time it occurs (four times in the example experiment above). |
| | 384 | The Click router supports kernel-level operation. The principles are the same, but the setup is a bit more involved. To use kernel-level Click, you will probably want first to develop and debug your setup at the user level. Drop us a line at [mailto:help@geni.net] for help setting up Click in kernel mode. |
