Hi,
Continuing with the ip-driver issue, now I have it working, I do not
know why, this is what I did...
After I typed...
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip/driver# ./ip-driver
-c ../serial_tun.conf /dev/ttyUSB0 telosb
I did...
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip# ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:5a:47:d8:8d
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:29 Base address:0xc000
eth2 Link encap:Ethernet HWaddr 00:21:00:da:bf:a4
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:ff:feda:bfa4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5138 errors:1 dropped:0 overruns:0 frame:109030
TX packets:6410 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2802499 (2.8 MB) TX bytes:3715723 (3.7 MB)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:175 errors:0 dropped:0 overruns:0 frame:0
TX packets:175 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14804 (14.8 KB) TX bytes:14804 (14.8 KB)
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::64/128 Scope:Link
inet6 addr: fec0::64/128 Scope:Site
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:336 (336.0 B) TX bytes:632 (632.0 B)
Then, I erase the both ipv6 address of the tun0 interface, thats cuase
those are indicating that the complete address is the network prefix, I
think thats not correct...
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip# /sbin/ip -6 addr
del fe80::64 dev tun0
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip# /sbin/ip -6 addr
del fec0::64 dev tun0
and then...
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip# /sbin/ip -6 addr
add fec0::64/64 dev tun0
then when I tried to ping again, its says that the network is
unreachable... well... I restart the ip-driver, the ifconfig of tun0 was
the first again (with both ipv6 addresses), then I tried again ping6 and
it finally works...
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip/driver# ./ip-driver
-c ../serial_tun.conf /dev/ttyUSB0 telosb
2010-01-15T12:56:41.791PYT: INFO: Read log level: INFO
2010-01-15T12:56:41.792PYT: INFO: Read config from '../serial_tun.conf'
2010-01-15T12:56:41.792PYT: INFO: Proxying neighbor advertisements to
eth2
2010-01-15T12:56:41.792PYT: INFO: Using channel 15
2010-01-15T12:56:41.792PYT: INFO: Retries: 5
2010-01-15T12:56:41.793PYT: INFO: telnet console server running on port
6106
2010-01-15T12:56:41.795PYT: INFO: created tun device: tun0
2010-01-15T12:56:42.096PYT: INFO: interface device successfully
initialized
2010-01-15T12:56:42.096PYT: INFO: starting radvd on device tun0
2010-01-15T12:56:55.427PYT: INFO: Starting to proxy for 0x7
2010-01-15T12:57:31.467PYT: INFO: interface device successfully
initialized
2010-01-15T12:57:43.590PYT: INFO: interface device successfully
initialized
r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip# ping6 fec0::7 (mote
with UDPEcho)
PING fec0::7(fec0::7) 56 data bytes
64 bytes from fec0::7: icmp_seq=1 ttl=65 time=83.3 ms
64 bytes from fec0::7: icmp_seq=2 ttl=65 time=82.9 ms
64 bytes from fec0::7: icmp_seq=5 ttl=65 time=88.1 ms
64 bytes from fec0::7: icmp_seq=7 ttl=65 time=89.2 ms
64 bytes from fec0::7: icmp_seq=8 ttl=65 time=87.7 ms
64 bytes from fec0::7: icmp_seq=9 ttl=65 time=85.7 ms
64 bytes from fec0::7: icmp_seq=10 ttl=65 time=184 ms
64 bytes from fec0::7: icmp_seq=11 ttl=65 time=82.5 ms
If the tun0 address is fec0::64/128 why it can ping to fec0::7/64
or /128???? /128 means that the entire address is the net prefix...
I think that address have to be fec0::64/64...
Can anybody help me with this???
I am a little worry for bothering, but there is not much documentation
about this issue in this mailing list, and this can be a way to help
other people to...
Thanks in advance...
Aldo Insfran.
On Fri, 2010-01-15 at 14:31 +0100, Jordi Soucheiron wrote:
> you could try to enable the verbose output of the ip driver. It may
> help to locate the problem.
>
> 2010/1/15 Aldo Javier <[email protected]>:
> > Hi all,
> >
> > Thanks Giuseppe!!!, I do not have the serial_tun.conf problem anymore...
> > I can run the driver... flash the UDPEcho and the IPBaseStation...
> > but I still have this problem... :(
> >
> > r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip/driver# ./ip-driver
> > -c ../serial_tun.conf /dev/ttyUSB0 telosb
> > 2010-01-15T09:43:05.993PYT: INFO: Read config from '../serial_tun.conf'
> > 2010-01-15T09:43:05.993PYT: INFO: Proxying neighbor advertisements to
> > eth0
> > 2010-01-15T09:43:05.994PYT: INFO: Using channel 15
> > 2010-01-15T09:43:05.994PYT: INFO: Retries: 5
> > 2010-01-15T09:43:05.994PYT: INFO: telnet console server running on port
> > 6106
> > 2010-01-15T09:43:06.043PYT: INFO: created tun device: tun0
> > 2010-01-15T09:43:06.351PYT: INFO: interface device successfully
> > initialized
> > 2010-01-15T09:43:06.351PYT: INFO: starting radvd on device tun0
> > 2010-01-15T09:43:22.977PYT: FATAL: send failed: Network is unreachable
> > 2010-01-15T09:43:24.106PYT: FATAL: send failed: Network is unreachable
> > 2010-01-15T09:43:26.361PYT: FATAL: send failed: Network is unreachable
> > 2010-01-15T09:43:30.874PYT: FATAL: send failed: Network is unreachable
> > 2010-01-15T09:43:39.885PYT: FATAL: send failed: Network is unreachable
> >
> > Seems the mote with the UDPEcho is not in the same net as the base
> > station, or problems with the battery, I checked the battery and it is
> > not the problem... In addition the leds of the bas station shows that it
> > is receiving packets from the wireless interface, cause the green led is
> > on... and then it seem to respond cause the red led lights...
> >
> > the base station ip is: fec0::64
> > and the ip of the mote with the UDPEcho is supposed fec0::7...
> >
> > Can it be a problem with the code that comes with the tinyos-2.x from
> > CVS...??? when I used ubuntu 8.10 I downloaded tinyos-2.x-contrib from
> > CVS and it used to work fine...
> >
> > Thanks in advance...
> >
> > Best Regards...
> >
> > Aldo Insfran.
> >
> >> Hi,
> >>
> >> ip-driver looks for serial_tun.conf in the current working directory.
> >> The serial_tun.conf deployed by default is in the directory
> >> $TOSROOT/support/sdk/c/blip , so you should run:
> >>
> >> cd $TOSROOT/support/sdk/c/blip
> >> driver/ip-driver /dev/ttyUSB0 telosb
> >>
> >> (notice the "driver/" before "ip-driver") Or, if you prefer, you
> >> should explicitly where to look for serial_tun.conf by running:
> >>
> >> cd $TOSROOT/support/sdk/c/blip/driver
> >> ./ip-driver -c ../serial_tun.conf /dev/ttyUSB0 telosb
> >>
> >> Regards.
> >>
> >> --
> >> Giuseppe Cardone
> >>
> >>
> >>
> >> On Fri, Jan 15, 2010 at 1:30 AM, Aldo Javier <[email protected]>
> >> wrote:
> >> > Hi all,
> >> >
> >> > Me again, now I facing a problem with the ip-driver who works with the
> >> > BLIP implementation, this is it:
> >> >
> >> > r...@aldo-laptop:/opt/tinyos-2.x/support/sdk/c/blip/driver# ./ip-driver
> >> > /dev/ttyUSB0 telosb
> >> > 2010-01-14T21:19:23.329PYT: FATAL: config parse of serial_tun.conf
> >> > failed!
> >> >
> >> > Anyone know what can be the problem???
> >> >
> >> > make telosb blip, works perfectly for both IPBaseStation and UDPEcho
> >> >
> >> > Thanks in advance...
> >> >
> >> > Aldo Insfran...
> >> >
> >> > _______________________________________________
> >> > 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
