ORBIT-USER: aodv

Tue Oct 24 17:45:41 EDT 2006

Hi Hari,

Yeah, I checked those things, it's running just fine, the issues i'm
having are with the ips. Apparently, aodv tries to work with the 192.168
.200 environment, so I decided to configure the ath0's in the
192.168.200.x, and the nodes find each other, but then when aodv tries to
connect to 10.2.5.1 (what is this machine?) it gets in troubles...
this is the execution at node 192.168.200.4

node1-2:/usr/src/aodv-uu-0.9.1# ./aodvd -i ath0
17:43:09.420 aodv_socket_init: RAW send socket buffer size set to 219136
17:43:09.421 aodv_socket_init: Receive buffer size set to 219136
17:43:09.421 main: In wait on reboot for 15000 milliseconds. Disable with
"-D".
17:43:09.421 hello_start: Starting to send HELLOs!

17:43:23.212 rt_table_insert: Inserting 192.168.200.3 (bucket 0) next hop
192.168.200.3
17:43:23.213 nl_send_add_route_msg: Send ADD/UPDATE ROUTE to kernel:
192.168.200.3:192.168.200.3
17:43:23.213 rt_table_insert: New timer for 192.168.200.3, life=2100
17:43:23.213 hello_process: 192.168.200.3 new NEIGHBOR!
17:43:24.422 wait_on_reboot_timeout: Wait on reboot over!!

17:44:30.182 nl_callback: Sending RERR for unsolicited message from
192.168.200.200 to dest 10.2.5.1
17:44:30.182 rerr_create: Assembling RERR about 10.2.5.1 seqno=0
17:44:30.182 aodv_socket_send: AODV msg to 255.255.255.255 ttl=1 size=12
17:44:30.388 aodv_socket_process_packet: Received RERR
17:44:30.388 rerr_process: ip_src=192.168.200.3
17:44:30.388 log_pkt_fields: rerr->dest_count:1 rerr->flags=-
17:44:30.388 rerr_process: unreachable dest=10.2.5.1 seqno=0
17:44:30.388 rerr_process: Ignoring UDEST 10.2.5.1

On Tue, 24 Oct 2006, Haris Kremo wrote:

> what Pandurang means is whether the interface is available to the
> operating system, which you check using iwconfig command
>
> if the interface is not listed, executing modprobe ath_pci loads the
> driver and makes it  available to be configured using iwconfig (mode,
> channel, rate...) and ifconfig (IP address, mask...)
>
> if you use some of ruby scripts these operations are abstracted
> through the script, but for debugging purposes one has to do these
> steps manually
>
> H.
>
> On 10/24/06, Vanessa Frias-martinez <vf2001 at cs.columbia.edu> wrote:
> >
> > i tried, but got an "ignoring unknown interface ath0=ath0" message...
> >
> > On Tue, 24 Oct 2006, Pandurang Kamat wrote:
> >
> > > Have you brought the interface up and configured it ?
> > >
> > > -Pandurang
> > >
> > > Vanessa Frias-martinez wrote:
> > > > that's what i meant from my previous email, i tried ath0 too and got the
> > > > same error:
> > > >
> > > > ./aodvd -i ath0
> > > > 15:05:09.984 get_if_info: Could not get address of ath0 : Cannot assign
> > > > requested address
> > > >
> > > >
> > > > On Tue, 24 Oct 2006, Sachin Ganu wrote:
> > > >
> > > >> No it is ath0 (wireless interface) eth0 and eth1 are the wired
> > > >> interfaces used for user data and control respectively
> > > >>
> > > >> The script given on the UsingAODV page also reads ath0..
> > > >>
> > > >> Please try with ath0
> > > >>
> > > >> On 10/24/06, Vanessa Frias-martinez <vf2001 at cs.columbia.edu> wrote:
> > > >>> Hi!
> > > >>>
> > > >>> i'm trying to execute aodv in the nodes of a sandbox. i read the
> > > >>> usingAODV page and from what i understand, the device is eth0 right? or is
> > > >>> ath0 a typo? i've tried the two of them and always get:
> > > >>>
> > > >>> node1-1:/usr/src/aodv-uu-0.9.1# ./aodvd -i eth0
> > > >>> 14:28:28.549 get_if_info: Could not get address of eth0 : Cannot assign
> > > >>> requested address
> > > >>>
> > > >>> i also tried eth1 and got a long error output...any idea?
> > > >>> thanks!
> > > >>>
> > > >>> node1-1:/usr/src/aodv-uu-0.9.1# ./aodvd -i eth1
> > > >>> 14:18:34.221 aodv_socket_init: RAW send socket buffer size set to 219136
> > > >>> 14:18:34.222 aodv_socket_init: Receive buffer size set to 219136
> > > >>> 14:18:34.222 main: In wait on reboot for 15000 milliseconds. Disable with
> > > >>> "-D".
> > > >>> 14:18:34.222 hello_start: Starting to send HELLOs!
> > > >>> 14:18:34.222 nl_callback: Got NOROUTE msg from kernel for 10.12.0.10
> > > >>> 14:18:34.222 rreq_create: Assembled RREQ 10.12.0.10
> > > >>> 14:18:34.222 log_pkt_fields: rreq->flags: rreq->hopcount=0 rreq->rreq_id=0
> > > >>> 14:18:34.222 log_pkt_fields: rreq->dest_addr:10.12.0.10 rreq->dest_seqno=0
> > > >>> 14:18:34.222 log_pkt_fields: rreq->orig_addr:10.12.1.1 rreq->orig_seqno=2
> > > >>> 14:18:34.222 aodv_socket_send: AODV msg to 255.255.255.255 ttl=2 size=24
> > > >>> 14:18:34.222 rreq_route_discovery: Seeking 10.12.0.10 ttl=2
> > > >>> 14:18:34.542 route_discovery_timeout: 10.12.0.10
> > > >>> 14:18:34.542 route_discovery_timeout: Seeking 10.12.0.10 ttl=4 wait=320
> > > >>> 14:18:34.542 rreq_create: Assembled RREQ 10.12.0.10
> > > >>> 14:18:34.542 log_pkt_fields: rreq->flags: rreq->hopcount=0 rreq->rreq_id=1
> > > >>> 14:18:34.542 log_pkt_fields: rreq->dest_addr:10.12.0.10 rreq->dest_seqno=0
> > > >>> 14:18:34.542 log_pkt_fields: rreq->orig_addr:10.12.1.1 rreq->orig_seqno=3
> > > >>> 14:18:34.542 aodv_socket_send: AODV msg to 255.255.255.255 ttl=4 size=24
> > > >>> 14:18:35.021 route_discovery_timeout: 10.12.0.10
> > > >>> 14:18:35.021 route_discovery_timeout: Seeking 10.12.0.10 ttl=6 wait=480
> > > >>> 14:18:35.021 rreq_create: Assembled RREQ 10.12.0.10
> > > >>> 14:18:35.021 log_pkt_fields: rreq->flags: rreq->hopcount=0 rreq->rreq_id=2
> > > >>> 14:18:35.022 log_pkt_fields: rreq->dest_addr:10.12.0.10 rreq->dest_seqno=0
> > > >>> 14:18:35.022 log_pkt_fields: rreq->orig_addr:10.12.1.1 rreq->orig_seqno=4
> > > >>> 14:18:35.022 aodv_socket_send: AODV msg to 255.255.255.255 ttl=6 size=24
> > > >>> 14:18:35.662 route_discovery_timeout: 10.12.0.10
> > > >>>
> > > >>>
> > >
> >
>