This is a sign that the driver can't talk to the interface mote-- thatis, the mote running IPBaseStation.
Be sure that the mote you're using for this purpose has the latest version of IPBaseStation, is connected to the device referenced (/dev/ttyUSB0 in this case) and has the correct baud rate (you might try putting in 57600 and 115200 manually, if you're unsure about which is correct). What happens when the interface boots up and the driver starts is the driver sends a message to the interface mote configuring several parameters; the interface replys with an ack. If the driver doesn't get the ack, it aborts. However, I think that if the serial stack replies too quickly the ack sometimes gets dropped; that's why there's a timeout. If you do a 'cvs up', I've increased the timeout from 50 -> 200ms; that may fix the problem and seems worth a try... Steve On Fri, Jan 30, 2009 at 7:54 PM, Ansar Jamil <[email protected]> wrote: > Hi, > > I face following problem when try to do interfacing between the mote and > PC. > > r...@ansar-desktop:/svn/code/b6lowpan/support/sdk/c/lib6lowpan/tunnel# > ./serial_tun /dev/ttyUSB0 telosb > 11:46:46.190634: INFO: Read config from 'serial_tun.conf' > 11:46:46.190759: INFO: Proxying neighbor advertisements to eth3 > 11:46:46.190781: INFO: Using channel 13 > 11:46:46.194440: INFO: created tunnel device: tun0 > 11:46:46.243787: INFO: send me SIGUSR1 to dump the topology to a > 'nwgraph.dot' in the cwd > 11:46:52.243927: FATAL: configuring interface failed! aborting! > > I tried solution given by Alessandro by changing the flag however the same > error happened. I need some advice to solve this problem? > > Thanks > Best Regards > Ansar > > > --- On Thu, 1/29/09, Stephen Dawson-Haggerty <[email protected]> > wrote: > > > From: Stephen Dawson-Haggerty <[email protected]> > > Subject: Re: [Tinyos-help] b6lowpan: tunnel problems > > To: "alessandro ludovici" <[email protected]> > > Cc: [email protected] > > Date: Thursday, January 29, 2009, 11:54 AM > > Changing the config_stated flag is a workaround; you should > > try reflashing > > the interface mote with a new version of IPBaseStation. > > Basically, the > > driver sends a packet to the interface mote to set its > > channel and address, > > and waits for a reply; the fatal error means you're not > > getting it. If it > > still works after you change that flag, you may have an > > older version > > installed. > > > > Other then that, the behavior you describe is normal. > > Basically, the router > > needs to wait until it hears from a mote to add a routing > > table entry so it > > can route to it. > > > > If you update to the latest verion in contrib, there's > > a scheme for > > generating traffic that will improve convergence time and > > you can usually > > ping motes immediate after they boot. > > > > Steve > > > > On Thu, Jan 29, 2009 at 3:52 AM, alessandro ludovici < > > [email protected]> wrote: > > > > > Hi, > > > I have the following problem with b6lowpan. When I > > give the command "sudo > > > ./serial_tun /dev/ttyUSB0 telosb", I get the > > following: > > > > > > 12:29:46.785336: INFO: Read config from > > 'serial_tun.conf' > > > 12:29:46.785611: INFO: Proxying neighbor > > advertisements to eth1 > > > 12:29:46.785702: INFO: Using channel 13 > > > 12:29:46.897116: INFO: created tunnel device: tun0 > > > 12:29:46.930991: INFO: send me SIGUSR1 to dump the > > topology to a > > > 'nwgraph.dot' in the cwd > > > 12:29:50.302466: INFO: interface device successfully > > initialized > > > 12:30:15.556531: WARN: tun_input: dropping packet with > > IPv6 options > > > 12:30:22.843423: WARN: tun_input: dropping packet with > > IPv6 options > > > > > > and till here everything seems to be ok, but when I > > give a ping6 command I > > > receive a "connect: Network is unreachable". > > After a while I receive the > > > followings: > > > > > > Cannot find device "eth1" > > > Cannot find device "eth1" > > > 12:30:42.512530: INFO: nw_get_route: computing new > > routes > > > > > > The I ping the devices and everything works fine. The > > serial_tun.con has > > > "proxy eth1" as default entry. I give in the > > terminal the ifconfig command > > > and no eth1 device is found so I've changed the > > serial_tun.conf to "proxy > > > eth0" (eth0 is the only Ethernet device > > recognized by ifconfig). However it > > > does not work eith eth0. > > > > > > Furthermore I have changed in the serial_tun. c the > > value of "volatile > > > sig_atomic_t config_success" (line 146) from 0 to > > 1. This because I get a > > > fatal error when starting the tunneling. Changing the > > value the fatal error > > > has disappeared. > > > > > > What is wrong? Maybe there is a bug? > > > > > > _______________________________________________ > > > Tinyos-help mailing list > > > [email protected] > > > > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > > _______________________________________________ > > Tinyos-help mailing list > > [email protected] > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
