[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] Problems with Sockets




The IP assign server is AXIS internal stuff, it checks for the server and if it fails it uses options for btd or /etc/ppp/options for remote IP and gets the local from the ethernet interface.

The unknown command messages is simply due to that the HCI emulator does not support the commands (it doesn't matter for testing the stack). The failed BD address is the same.
The HCI emulation could easily be expanded to handle these cases also, however I think this it is of rather low priority. Feel free to do it yourself :)

The command "con" is temporarily removed but will be added again once we fix the SDP client issues.
Until then you can always use the rf_conn command which is availabel in the usermode stack.

brgds
Mattias Ågren, 
AXIS Communications AB


-----Original Message-----
From: Juan Ignacio Perez Diez [mailto:juan@xxxxxxx.com]
Sent: den 22 november 2000 14:36
To: Blue tooth list
Subject: [bluetooth-dev] Problems with Sockets


Iam trying to test the application (version  bluetooth_20001031.tgz) through
two networked computers.

Command line:  btd --cmdmode --tcpsock :10000 --hwinit none

And I get this log file:
Nov 22 14:35:18 bertha btd: Initiating signal handler
Nov 22 14:35:18 bertha btd: Opening socket /tmp/ipa_server
Nov 22 14:35:18 bertha btd: open_socket /tmp/ipa_server failed
Nov 22 14:35:18 bertha btd: Could not find IP Assign server
Nov 22 14:35:18 bertha kernel: BT SYS: Setting BT driver to use serial tty
Nov 22 14:35:18 bertha kernel: BT SYS: Registering tty on line 7
Nov 22 14:35:18 bertha btd: Current HW set to HW no init
Nov 22 14:35:18 bertha kernel: BT SYS: Setting HW
Nov 22 14:35:18 bertha kernel: BT SYS: Current HW set to HW no init
Nov 22 14:35:18 bertha kernel: BT SYS: Initialising Bluetooth Stack
Nov 22 14:35:18 bertha kernel: BT SYS: Initialising HCI
Nov 22 14:35:18 bertha kernel: BT SYS: *** HCI emulator on ***
Nov 22 14:35:18 bertha kernel: BT SYS: Initialising HCI inbuffers [17000]
Nov 22 14:35:18 bertha kernel: command_handler: Unknown command ogf:0x3,ocf:0x3
Nov 22 14:35:18 bertha kernel: BT SYS: Reading buffer sizes in the module...
Nov 22 14:35:18 bertha kernel: command_handler: Unknown command ogf:0x3,ocf:0x24
Nov 22 14:35:18 bertha kernel: BT SYS: Initialising L2CAP
Nov 22 14:35:18 bertha kernel: command_handler: Unknown command ogf:0x4,ocf:0x9
Nov 22 14:35:28 bertha kernel: Timeout when waiting for command response
Nov 22 14:35:28 bertha kernel: BT SYS:  ERROR :Failed to get local BD addr
Nov 22 14:35:28 bertha kernel: BT SYS: Initialising RFCOMM
Nov 22 14:35:28 bertha kernel: BT SYS: Initialising SDP
Nov 22 14:35:28 bertha kernel: BT SYS: Initialising TCS
Nov 22 14:35:28 bertha kernel: BT SYS: Initialising BTMEM [2500 bytes]
Nov 22 14:35:28 bertha kernel: hci_change_local_name to bertha
Nov 22 14:35:28 bertha kernel: command_handler: Unknown command ogf:0x3,ocf:0x13
Nov 22 14:35:38 bertha kernel: Timeout when waiting for command response
Nov 22 14:35:38 bertha btd: Starting SDP server
Nov 22 14:35:38 bertha kernel: BT SYS: Registering tty on line 0  


The problem is that I get several errors (as you can see in the log file:
btd: Could not find IP Assign server
kernel: command_handler: Unknown command ogf:0x3,ocf:0x3
......

I supposse that something is wrong. What can be happening???
Because if i try to get the readbd I get 00:00:00:00:00:00

In the other side i type con 00:00:00:00:00:00 0 and I get error: command not recognized or wrong syntax

Can you help me??
-- 
Juan Ignacio Perez Diez
Software Engineer
juan@xxxxxxx.com
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com