ORBIT-USER: Fail when perform Click-install (Tutorial about Virtual Mobility SS)
Sanjit Krishnan Kaul
sanjitkaul at gmail.com
Mon Feb 26 11:05:31 EST 2007
I cannot reproduce your error. Can u send me the tar.gz of your vmss
directory on my e-mail id (sanjit at winlab.rutgers.edu) or leave it where I
have access.
Click routes on the basis of the rule one specifies. In our case it is
mostly based on Ethernet addresses. The rules are determined by the
configuration one specifies.
To run the current setup you don't need to.
_____
From: owner-orbit-user at winlab.rutgers.edu
[mailto:owner-orbit-user at winlab.rutgers.edu] On Behalf Of Arinto Murdopo
Sent: Monday, February 26, 2007 4:55 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Sorry for late reply, I had extracurricular activities in the weekend.
I got that error every time when I run CreateMobilitySetup script. However,
I can install the script properly for the specified nodes.
Although I try to redirect the output of CreateMobilitySetup to a textfile
(in this case is res.txt), this error is not logged into res.txt.
Oiya, one more question, do I need to set the ESSID, IP address, and the
wireless communication channel of virtual node and grid node when running
the spatial switching code? In my understanding, the Click code send the
packet from one grid node to another grid node base on the MAC address of
the destination grid node. Is that true?
Thank you
Thank
On 2/24/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
Your understanding of synchronization is correct. In your example the nodes
are not synchronized properly. Also, the timer doesn't start at the same
time for both nodes.
When are you getting the error u specified? Is it repeatable?
_____
From: owner-orbit-user at winlab.rutgers.edu
[mailto:owner-orbit-user at winlab.rutgers.edu] On Behalf Of Arinto Murdopo
Sent: Friday, February 23, 2007 8:25 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Okie, it works well eith the actual name of click file. :D
Aniway, I found error when executing the CreateMobilitySetup script
here it is
CreateMobilitySetup >> res.txt
sh: line 1: ,00:0F:EA:7C:C3:A8: command not found
I attach the CreateMobilitySetup script and also the resulting file res.txt.
However, I'm able to load and execute the click file via click-install
command. Now I'm waiting for the result.
By the way, I have question about synchronizing the node.
Suppose for node A, I finish the click-install command at time t1 and for
node B, I finish the click-install command at time t2.
If t1 does not equal to t2, does it mean that they are not synchronized
properly? Does the timer for spatial switching for this two nodes start not
at the same time (since when click-install finished, the experiment is
started) ?
thank you for the explanation. I want to clarify my doubt, that's why I ask
those questions.
Arinto
On 2/23/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
Don't do click-install mob*.click. Use the actual name of the click file
instead.
_____
From: owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> [mailto:owner-
<mailto:orbit-user at winlab.rutgers.edu> orbit-user at winlab.rutgers.edu] On
Behalf Of Arinto Murdopo
Sent: Thursday, February 22, 2007 10:49 PM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Hi Sanjit
I can execute the installation correctly when I do ssh directly to specified
nodes. Here is the example
node1-19:~# modprobe ath_pci
node1-19:~# ifconfig eth0 up
node1-19:~# ifconfig ath0 up
node1-19:~# /bin/sh /root/click-config.sh
node1-19:~# click-install mob*.click
node1-19:~#
However, when I do this via shell script, here is the output, the
click-install command still produce error. Any idea why this error happen?
Or do I need to put delay between
node1-19:~# /bin/sh /root/click-config.sh
and
node1-19:~# click-install mob*.click.
Here is the output error from the shell script (setup.sh)
click-uninstall
modprobe -r ath_pci
ath_pci: Device or resource busy
modprobe_ath_pci
ifconfig eth0 up
ifconfig ath0 up
/bin/sh /root/click-config.sh
click-install mob*.click
insmod: a module named click already exists
click-install: '/sbin/insmod /usr/local/lib/click.o' failed
Here I attach the setup files.
setup.sh is used to setup each node
Setup_Nodes_Script.sh is used to execute setup.sh in specified nodes.
Thank you
Arinto
On 2/23/07, Arinto Murdopo <arinto at gmail.com> wrote:
Thanks, I'll try it!!
arinto
On 2/23/07, Sanjit Krishnan Kaul < sanjitkaul at gmail.com
<mailto:sanjitkaul at gmail.com> > wrote:
I think I know what is going wrong here!
Please open the file CreateMobilitySetup
and replace the line
cp ./database/node?-?.txt ./EthernetAddresses
by
cp ./database/node*-*.txt ./EthernetAddresses
Save the file and re-run CreateMobilitySetup. Upload and install the newly
generated click-script!
_____
From: owner- <mailto:orbit-user at winlab.rutgers.edu>
orbit-user at winlab.rutgers.edu [mailto:owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> ] On Behalf Of Arinto Murdopo
Sent: Thursday, February 22, 2007 11:50 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Here they are...
Thank you
Arinto
On 2/23/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
Can you please mail the click script and VM*.txt.
_____
From: owner- <mailto:orbit-user at winlab.rutgers.edu>
orbit-user at winlab.rutgers.edu [mailto:owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> ] On Behalf Of Arinto Murdopo
Sent: Thursday, February 22, 2007 11:29 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Here is the output of that command
node1-19:~# click-install mob_node_src_generated_Node_1_19.click
mob_node_src_generated_Node_1_19.click:70: While configuring ' FromHost at 39
:: FromHost':
too many arguments; expected 'string, IP address prefix, [keywords]'
mob_node_src_generated_Node_1_19.click:3: While configuring 'ee ::
EtherEncap':
argument 2 takes Ethernet address (source address)
Router could not be initialized!
If the result is like that, I think there is something wrong with the click
configuration file generated by configuration file generator
(CreateMobilitySetup utility). The 2nd line states that the error exists in
line 70 and line 4 states an error also exists in line 3.
I'll try to run that command inside a sandbox. Maybe I generate the file
wrongly.
Thank you for the explanation
Arinto
On 2/23/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
Just do
Click-install mob_node_src_generated_Node_1_19.click
Instead of click-install *.click
_____
From: owner- <mailto:orbit-user at winlab.rutgers.edu>
orbit-user at winlab.rutgers.edu [mailto:owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> ] On Behalf Of Arinto Murdopo
Sent: Thursday, February 22, 2007 10:55 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Hi Sanjit
Here is the output of ls -l *.click
node1-19:~# ls -l *.click
-rw-r--r-- 1 root root 2013 Dec 12 2004 ap.click
-rw-r--r-- 1 root root 172 Dec 13 2004 dump2.click
-rw-r--r-- 1 root root 1775 Feb 22 10:43
mob_node_src_generated_Node_1_19.click
Here is the error message
click-install mob*.click
insmod: a module named proclikefs already exists
click-install: '/sbin/insmod /usr/local/lib/proclikefs.o' failed
mob_node_src_generated_Node_1_19.click:70: While configuring ' FromHost at 39
:: FromHost':
too many arguments; expected 'string, IP address prefix, [keywords]'
mob_node_src_generated_Node_1_19.click:3: While configuring 'ee ::
EtherEncap':
argument 2 takes Ethernet address (source address)
Router could not be initialized!
So there are 3 click files. However my installation command is
click-install mob*.click
which only install the generated click files. Besides that I also perfome
click-uninstall to uninstall previous Click kernel module.
Any idea what's happening here? Thank you for your explanation.
Arinto
On 2/22/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
I meant on the node. Just want to make sure that you don't have more than a
click script in your current directory when you run the click-install
command.
_____
From: owner- <mailto:orbit-user at winlab.rutgers.edu>
orbit-user at winlab.rutgers.edu [mailto:owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> ] On Behalf Of Arinto Murdopo
Sent: Thursday, February 22, 2007 1:07 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
Hi Sanjit
Do you mean in the nodes or in the console? I run it in the node.
However, since my slot is over, I cannot take the output of that command.
Actually I just send the generated Click configuration file to specific
nodes using
scp EthernetAddresses/mob_node_src_generated_Node_12_9.click setup.sh
root at node12-9:~
The EthernetAddresses/mob_node_src_generated_Node_12_9.click itself is
generated from CreateMobilitySetup utility.
thank you
arinto
On 2/22/07, Sanjit Krishnan Kaul <sanjitkaul at gmail.com> wrote:
Please send the output of
$ ls *.click
where you are running the commands from.
_____
From: owner- <mailto:orbit-user at winlab.rutgers.edu>
orbit-user at winlab.rutgers.edu [mailto:owner- orbit-user at winlab.rutgers.edu
<mailto:orbit-user at winlab.rutgers.edu> ] On Behalf Of Arinto Murdopo
Sent: Wednesday, February 21, 2007 10:32 AM
To: orbit-user at winlab.rutgers.edu
Subject: Re: ORBIT-USER: Fail when perform Click-install (Tutorial about
Virtual Mobility SS)
And here what I got when I tried to install in Virtual Grid
-----------------SETUP NODE 18-1------------------
click-uninstall
modprobe -r ath_pci
modprobe_ath_pci
Warning: loading /lib/modules/2.4.26/net/ath_hal.o will taint the kernel:
non-GPL license - Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted
modules
Module ath_hal loaded, with warnings
Module ath_pci loaded, with warnings
ifconfig eth0 up
ifconfig ath0 up
/bin/sh /root/click-config.sh
click-install mob*.click
insmod: a module named proclikefs already exists
click-install: '/sbin/insmod /usr/local/lib/proclikefs.o' failed
mob_server_src_generated_VM2.click:40: unknown element class 'ee_VM2_ALLVM'
mob_server_src_generated_VM2.click:37: 'whichVM_cl :: Classifier' has no
output 1
mob_server_src_generated_VM2.click:40: ' Strip at 11 :: Strip' input 0 unused
mob_server_src_generated_VM2.click:37: 'whichVM_cl :: Classifier' output 0
unused
Router could not be initialized!
Any idea what happen with the router? Thank you for your explanations, I'm
not familiar with Click and I think by asking through mailing list is the
fastest way to accelerate my learning curve.. Thank you all :D
arinto
On 2/21/07, Arinto Murdopo <arinto at gmail.com> wrote:
Dear All
I receive errors when I tried to install the Click-configuration file in
tutorial about Virtual Mobility Spatial Switching T_T
Here is the output.
click-install mob*.click
insmod: a module named proclikefs already exists
click-install: '/sbin/insmod /usr/local/lib/proclikefs.o' failed
Last time I managed to install this correctly. Is that because I'm using my
own customized image? I'm using my own customized image tmp/node-
1-1-2007-02-15-11-49-27.ndz
which is click-2.4.26-20051204.ndz with additional iperf (the intergrated
iperf doesn't work, so I install new iperf and save the node)
Thank you
Arinto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://orbit-lab.org/pipermail/orbit-user/attachments/20070226/66214f9f/attachment.htm
More information about the orbit-user
mailing list