[Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Florian]

hi,

im using an elmeg D@VOS-44.dsl AP has anyone figured out how to pair and 
connect the device
or is it impossible too do that using bluez(at the moment)?


using
gentoo linux 2.6.3
USB BT-Device (BT3030 Tecom)

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> im using an elmeg D@VOS-44.dsl AP has anyone figured out how to pair and 
> connect the device
> or is it impossible too do that using bluez(at the moment)?

it looks like the AP is using LAN access using PPP and DUN. So it should
be easy to connect to the AP using

	dund --connect <bdaddr-ap>

Please also run "hcitool info <bdaddr-ap>" (as root) and show us the
output.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Florian]

On Wed, 25 Feb 2004 17:18:55 +0100, Marcel Holtmann <marcel@holtmann.org> 
wrote:

> Hi Florian,
>
>> im using an elmeg D@VOS-44.dsl AP has anyone figured out how to pair and
>> connect the device
>> or is it impossible too do that using bluez(at the moment)?
>
> it looks like the AP is using LAN access using PPP and DUN. So it should
> be easy to connect to the AP using
>
> 	dund --connect <bdaddr-ap>
>
> Please also run "hcitool info <bdaddr-ap>" (as root) and show us the
> output.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

hi again,

thx for the high speed reply,

i have run both
bash-2.05b# dund --connect 00:0B:CE:00:01:8E

bash-2.05b# hcitool info 00:0B:CE:00:01:8E
Requesting information ...
          BD Address:  00:0B:CE:00:01:8E
          Device Name: elmeg D@VOS-44.dsl
          LMP Version: 1.1 (0x1) LMP Subversion: 0x175
          Manufacturer: Cambridge Silicon Radio (10)
          Features: 0xff 0xff 0x0f 0x00
                  <3-slot packets> <5-slot packets> <encryption> <slot 
offset>
                  <timing accuracy> <role switch> <hold mode> <sniff mode>
                  <park mode> <RSSI> <channel quality> <SCO link>
                  <HV2 packets> <HV3 packets> <u-law log> <A-law log>
                  <CVSD> <paging scheme> <power control> <transparent SCO>

mhh this is what i get. But still no clue how to get things working.
In my eyes pairing comes next then establishing a connetion and then tell 
the AP
username and passwd.
Found an option in dund using MSDUN but did not get it the way i want.

suggestions?

Regards

Florian

P.S.: tried using  mailing list archives 
(http://sourceforge.net/mailarchive/forum.php?forum_id=672)
but get
ERROR
Forum not found

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> i have run both
> bash-2.05b# dund --connect 00:0B:CE:00:01:8E
> 
> bash-2.05b# hcitool info 00:0B:CE:00:01:8E
> Requesting information ...
>          BD Address:  00:0B:CE:00:01:8E
>          Device Name: elmeg D@VOS-44.dsl
>          LMP Version: 1.1 (0x1) LMP Subversion: 0x175
>          Manufacturer: Cambridge Silicon Radio (10)
>          Features: 0xff 0xff 0x0f 0x00
>                  <3-slot packets> <5-slot packets> <encryption> <slot 
> offset>
>                  <timing accuracy> <role switch> <hold mode> <sniff mode>
>                  <park mode> <RSSI> <channel quality> <SCO link>
>                  <HV2 packets> <HV3 packets> <u-law log> <A-law log>
>                  <CVSD> <paging scheme> <power control> <transparent SCO>
> 
> mhh this is what i get. But still no clue how to get things working.
> In my eyes pairing comes next then establishing a connetion and then tell 
> the AP
> username and passwd.
> Found an option in dund using MSDUN but did not get it the way i want.

try it with

	dund --nodetach --connect <bdaddr> --msdun

What version of dund are you using? Do you see any errors in your
logfiles? What kernel are you using?

If you still have problems, please start "hcidump -w <file>" (as root)
before executing dund and send us the dump file.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> bash-2.05b# dund --nodetach --connect 00:0B:CE:00:01:8E  --msdun
> dund[3470]: DUN daemon ver 1.1
> dund[3470]: Searching for LAP on 00:0B:CE:00:01:8E
> dund[3470]: Failed to connect to the SDP server. Connection timed out(110)
> 
> bash-2.05b# hcidump
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection(0x01|0x0005) plen 13
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connect Complete(0x03) plen 11
> 
> how do i start/configure the sdp server?

this is the SDP server on the AP, you don't have to start one. Run
hcidump with the -x option, so I can see the status codes.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> bash-2.05b# dund --connect 00:0B:CE:00:01:8E
> 
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection(0x01|0x0005) plen 13
>    8E 01 00 CE 0B 00 18 CC 02 00 00 00 00
> > HCI Event: Command Status(0x0f) plen 4
>    00 01 05 04
> > HCI Event: Connect Complete(0x03) plen 11
>    21 06 00 8E 01 00 CE 0B 00 01 00

you have to enable role switch on your local device. Use hciconfig or
set it in hcid.conf.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> I have changed hcid.conf & restarted hcid - nothing happend, but I have 
> run
> 
> sdptool browse
> Inquiring ...
> Failed to connect to SDP server on 00:0B:CE:00:01:8E: Function not 
> implemented
> 
> for some reason service is not discoverd.

run "hcidump -x" again and show us the output of "hciconfig -a".

> found patch-2.6.3-mh.gz does it make anything easier?

No. It only contains small changes which are not related.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> Hope this help figure out the problem.
> 
> bash-2.05b# hciconfig -a
> hci0:   Type: USB
>          BD Address: 00:03:C9:23:3D:51 ACL MTU: 377:10  SCO MTU: 16:0
>          UP RUNNING PSCAN ISCAN AUTH ENCRYPT
>          RX bytes:6807 acl:0 sco:0 events:488 errors:0
>          TX bytes:5371 acl:0 sco:0 commands:268 errors:0
>          Features: 0xff 0xfd 0x05 0x00
>          Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>          Link policy: RSWITCH HOLD SNIFF PARK
>          Link mode: ACCEPT MASTER
>          Name: 'BT3030 (0)'
>          Class: 0x000100
>          Service Classes: Unspecified
>          Device Class: Computer, Uncategorized
>          HCI Ver: 1.1 (0x1) HCI Rev: 0x2 LMP Ver: 1.1 (0x1) LMP Subver: 
> 0xf07
>          Manufacturer: Broadcom Corporation (15)
> 
> bash-2.05b# hcidump -x
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Read Local Name(0x03|0x0014) plen 0
> > HCI Event: Command Complete(0x0e) plen 252
>    01 14 0C 00 42 54 33 30 33 30 20 28 30 29 00 40 38 14 03 40
>    00 54 01 40 04 00 00 00 9C 56 01 40 20 48 01 40 0C 4C 01 40
>    C9 89 04 08 A4 F7 FF BF 6A 83 00 40 C9 89 04 08 AC 5A 70 00
>    F0 87 04 08 60 F7 FF BF C0 4B 01 40 02 00 00 00 D0 56 01 40
>    00 00 00 00 01 00 00 00 00 00 00 00 60 F7 FF BF 00 00 00 00
>    17 9C 09 40 48 00 00 00 00 00 00 00 AC 5A 70 00 E0 F7 FF BF
>    70 4A 01 40 E0 63 15 40 60 59 15 40 F8 1B 03 40 00 54 01 40
>    84 F7 FF BF 62 ED 09 40 E0 63 15 40 B0 07 05 08 60 59 15 40
>    00 00 00 00 B0 07 05 08 B8 F7 FF BF AE E4 08 40 B0 07 05 08
>    00 00 00 00 DC 82 00 40 20 48 01 40 44 00 00 00 70 4A 01 40
>    F0 F7 FF BF AE B2 00 40 0C 4C 01 40 D0 56 01 40 01 00 00 00
>    66 46 0D 40 E0 63 15 40 2C 2A 05 08 00 00 00 00 08 F8 FF BF
>    27 97 04 08 00 00 00 00 EC FC 04 08
> < HCI Command: Read Class of Device(0x03|0x0023) plen 0
> > HCI Event: Command Complete(0x0e) plen 7
>    01 23 0C 00 00 01 00
> < HCI Command: Read Local Version Information(0x04|0x0001) plen 0
> > HCI Event: Command Complete(0x0e) plen 12
>    01 01 10 00 01 02 00 01 0F 00 07 0F

I meant from the connection process.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> I tried the command You gave me some mails ago
> 
> bash-2.05b# dund --nodetach --connect 00:0B:CE:00:01:8E --msdun
> dund[8116]: DUN daemon ver 1.1
> dund[8116]: Searching for LAP on 00:0B:CE:00:01:8E
> dund[8116]: Failed to connect to the SDP server. Function not 
> implemented(38)
> 
> This is all I get :(
> 
> 
> bash-2.05b# hcidump -x
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Create Connection(0x01|0x0005) plen 13
>    8E 01 00 CE 0B 00 18 CC 02 00 00 00 00
> > HCI Event: Command Status(0x0f) plen 4
>    00 01 05 04
> > HCI Event: Connect Complete(0x03) plen 11
>    21 06 00 8E 01 00 CE 0B 00 01 00

it's again the role switch problem, but what I overlooked is that you
set your link mode to accept and master. Don't do this. Change it back
to accept and slave

        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> sorry my fault Link mode was master. Now I get
> 
> 
> bash-2.05b# dund --nodetach --connect 00:0B:CE:00:01:8E --msdun
> dund[6848]: DUN daemon ver 1.1
> dund[6848]: Searching for LAP on 00:0B:CE:00:01:8E
> dund[6848]: Connecting to 00:0B:CE:00:01:8E channel 1
> dund[6848]: Connection established
> 
> bash-2.05b# hcid -n
> hcid[6838]: HCI daemon ver 2.3 started
> hcid[6838]: HCI dev 0 up
> hcid[6838]: Starting security manager 0
> hcid[6838]: link_key_request (sba=51:3D:23:C9:03:00, dba=8E:01:00:CE:0B:00)
> hcid[6838]: link_key_request (sba=51:3D:23:C9:03:00, dba=8E:01:00:CE:0B:00)
> 
> bash-2.05b# hcidump
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Read Local Supported Features(0x04|0x0003) plen 0
> > HCI Event: Command Complete(0x0e) plen 12
> < HCI Command: Read Buffer Size(0x04|0x0005) plen 0
> > HCI Event: Command Complete(0x0e) plen 11
> < HCI Command: Read BD ADDR(0x04|0x0009) plen 0
> > HCI Event: Command Complete(0x0e) plen 10
> < HCI Command: Read Voice Setting(0x03|0x0025) plen 0
> > HCI Event: Command Complete(0x0e) plen 6
> < HCI Command: Set Event Filter(0x03|0x0005) plen 2
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Page Timeout(0x03|0x0018) plen 2
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Connection Accept Timeout(0x03|0x0016) plen 2
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Scan Enable(0x03|0x001a) plen 1
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Authentication Enable(0x03|0x0020) plen 1
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Encryption Mode(0x03|0x0022) plen 1
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Write Class of Device(0x03|0x0024) plen 3
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Change Local Name(0x03|0x0013) plen 248
> > HCI Event: Command Complete(0x0e) plen 4
> < HCI Command: Create Connection(0x01|0x0005) plen 13
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Role Change(0x12) plen 8
> > HCI Event: Link Key Request(0x17) plen 6
> < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
> > HCI Event: Command Complete(0x0e) plen 10
> > HCI Event: Connect Complete(0x03) plen 11
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(s): Connect req: psm 1 scid 0x0040
> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
> > HCI Event: Command Complete(0x0e) plen 6
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Max Slots Change(0x1b) plen 3
> > HCI Event: Link Key Request(0x17) plen 6
> < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22
> > HCI Event: Command Complete(0x0e) plen 10
> > ACL data: handle 0x0006 flags 0x02 dlen 16
>      L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> > ACL data: handle 0x0006 flags 0x02 dlen 16
>      L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
>      MTU 2016
> < ACL data: handle 0x0006 flags 0x02 dlen 14
>      L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 14
>      L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> < ACL data: handle 0x0006 flags 0x02 dlen 22
>      L2CAP(d): cid 0x40 len 18 [psm 1]
>          SDP SSA Req: tid 0x0 len 0xd
>            pat uuid-16 0x1102 (LAN)
>            max 0xffff
>            aid(s) 0x0004 (ProtocolDescList)
>            cont 00
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 1
>      L2CAP(d): cid 0x40 len 31 [psm 1]
>          SDP SSA Rsp: tid 0x0 len 0x1a
>            cnt 0x17
>   len 0x17 frm->len 0x15 n 0x14
>            srv rec #0
>              aid 0x0004 (ProtocolDescList)
>                 uuid-16 0x0100 (L2CAP)
>                 uuid-16 0x0003 (RFCOMM) uint 0x1
>              cont 00
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(s): Connect req: psm 3 scid 0x0041
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> > ACL data: handle 0x0006 flags 0x02 dlen 16
>      L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
> < ACL data: handle 0x0006 flags 0x02 dlen 16
>      L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
>      MTU 1024
> > ACL data: handle 0x0006 flags 0x02 dlen 16
>      L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4
>      MTU 2016
> < ACL data: handle 0x0006 flags 0x02 dlen 14
>      L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 14
>      L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0
> < ACL data: handle 0x0006 flags 0x02 dlen 8
>      L2CAP(d): cid 0x40 len 4 [psm 3]
>        RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 8
>      L2CAP(d): cid 0x41 len 4 [psm 3]
>        RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> < ACL data: handle 0x0006 flags 0x02 dlen 18
>      L2CAP(d): cid 0x40 len 14 [psm 3]
>        RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
>        dlci 2 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 1019 
> max_r
> etrans 0 credits 7
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 18
>      L2CAP(d): cid 0x41 len 14 [psm 3]
>        RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8
>        dlci 2 frame_type 0 credit_flow 14 pri 7 ack_timer 0 frame_size 1019 
> max_r
> etrans 0 credits 0
> < ACL data: handle 0x0006 flags 0x02 dlen 8
>      L2CAP(d): cid 0x40 len 4 [psm 3]
>        RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59
> > ACL data: handle 0x0006 flags 0x02 dlen 8
>      L2CAP(d): cid 0x41 len 4 [psm 3]
>        RFCOMM(s): UA: cr 1 dlci 2 pf 1 ilen 0 fcs 0x92
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(d): cid 0x40 len 8 [psm 3]
>        RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>        dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> > ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(d): cid 0x41 len 8 [psm 3]
>        RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>        dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> < ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(d): cid 0x40 len 8 [psm 3]
>        RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
>        dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> > ACL data: handle 0x0006 flags 0x02 dlen 9
>      L2CAP(d): cid 0x41 len 5 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c
> > ACL data: handle 0x0006 flags 0x02 dlen 12
>      L2CAP(d): cid 0x41 len 8 [psm 3]
>        RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
>        dlci 2 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 0 b2 0 b3 0 len 0
> < ACL data: handle 0x0006 flags 0x02 dlen 9
>      L2CAP(d): cid 0x40 len 5 [psm 3]
>        RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86
> < ACL data: handle 0x0006 flags 0x02 dlen 14
>      L2CAP(d): cid 0x40 len 10 [psm 3]
>        RFCOMM(d): UIH: cr 1 dlci 2 pf 0 ilen 6 fcs 0x9a
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0006 flags 0x02 dlen 48
>      L2CAP(d): cid 0x41 len 44 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 39 fcs 0x5c
> > ACL data: handle 0x0006 flags 0x02 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 13
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 13
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 17
> > ACL data: handle 0x0006 flags 0x01 dlen 13
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> > ACL data: handle 0x0006 flags 0x02 dlen 47
>      L2CAP(d): cid 0x41 len 43 [psm 3]
>        RFCOMM(d): UIH: cr 0 dlci 2 pf 0 ilen 39 fcs 0x40
> 
> 
> 
> 
> looks like we are on stepp away from getting this working.
> So could you tell me what comes next or is there a nice howto
> for the next step(s)(I am getting a bad conscience writing so
> many begging mails and keep you off your work) If no howto exist
> I promise to write one if I get it running. 

you should have a working PPP over RFCOMM connection. There are many
howto's at http://www.holtmann.org/linux/bluetooth/ and now it is only a
problem of using the right PPP settings.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> This is how far I get at the moment but I do not know how to
> configure the ppp connection to authenticate my system.
> 
> bash-2.05b# dund --nodetach --connect 00:0B:CE:00:01:8E --msdun
> dund[4386]: DUN daemon ver 1.1
> dund[4386]: Searching for LAP on 00:0B:CE:00:01:8E
> dund[4386]: Connecting to 00:0B:CE:00:01:8E channel 1
> dund[4386]: Connection established
> bash-2.05b# Using interface ppp0
> Connect: ppp0 <--> /dev/rfcomm0
> LCP terminated by peer (peer refused to authenticate)
> Connection terminated.

you can use

	dund --nodetach --connect 00:0B:CE:00:01:8E --msdun call lap

and create a /etc/ppp/peers/lap file with your PPP settings. But that is
now up to you, because I don't know what your AP is expecting.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluetooth Access Point elmeg D@VOS-44.dsl

[Marcel Holtmann]

Hi Florian,

> > you can use
> >
> > 	dund --nodetach --connect 00:0B:CE:00:01:8E --msdun call lap
> >
> > and create a /etc/ppp/peers/lap file with your PPP settings. But that is
> > now up to you, because I don't know what your AP is expecting.
> 
> at first thanks for your fast help!!!! In the end it works I can connect 
> to the AP
> using PAP and ppp.(little trick - after conection is established I have to 
> use route
> to set a gateway "route add default gw 192.168.1.110" ip the AP gave my 
> dongel)

you can also do this with pppd. Look for "defaultroute".

> I did not belive that I get it working so quick despite the fact that I 
> use Linux
> for about 3 weeks now.
> But I have still some questions.
> 
> When plugging in the dongel  I have to use bluefw 00X/00Y for the firmware 
> to be loaded
> into the dongel. Is it possible to automate this?

Yes. You can use Linux Hotplug for this. Look at the mailing list
archive for more details about it. With 2.6 you can try the bcm203x
kernel driver for the firmware loading.

> Why is the 2nd light on the dongel off when it is connected?

This is dongle specific, so I can't tell you.

> P.S.: As promised I ll write a howto for this AP but I need some more 
> testing time. ;) 

Go ahead and do it.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users