QUOTE(speculatrix @ Sep 27 2005, 06:07 AM)
what does "ifconfig -a" and "netstat -r" say?
could it be simply the default route is not being set?
Thanks for the suggestion. I've tried a few things, but haven't made any progress.
When the USB is connected ifconfig -a lists two interfaces: lo
inet addr: 127.0.0.1 ... usbd0
inet addr: 192.168.129.201 ...
And netstat -r lists 192.168.129.0 as the default gateway.
I don't fully understand how the IP routes are used by l2ping which takes as input a bluetooth MAC address. My end application is to associate a TTY using rfcomm and then interface to the Bluetooth device as I would any serial device.
So I tried the following just to verify that the default routes are not being used by l2ping.
1. Connected the USB cable.
2. Checked the routing table. 192.168.129.0 was there.
3. Verified the l2ping to the Bluetooth device works without problem.
4. Removed the default route using: route delete -net 192.168.129.0/24 usdb0
5. Verified the routing table was empty.
6. Repeated the l2ping. Which works flawlessly. l2ping didn't care that there was no default route.
I then tried the following:
1. With the USB cable still connected, started the l2ping to the Bluetooth device. Works flawlessly with response times around 40 ms.
2. While the l2ping was in progress, disconnected the USB cable. The l2ping starts reporting response times around 2-3 seconds.
3. After 3 or 4 slow responses, I reconnect the USB cable. The l2ping returns to normal with response times around 40 ms.
Any further suggestions would be appreciated.