From: wim delvaux <wim.delvaux@adaptiveplanet.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] L2Ping / Rfcomm connect : Function not implemented
Date: Mon, 13 Dec 2004 11:47:13 +0100 [thread overview]
Message-ID: <200412131147.13321.wim.delvaux@adaptiveplanet.com> (raw)
In-Reply-To: <1102924939.8750.84.camel@pegasus>
On Monday 13 December 2004 09:02, Marcel Holtmann wrote:
> Hi Wim,
>
> > If I execute on my 3870 Ipaq
> >
> > l2ping 00:60:57:35:81:B6
> >
> > Where the BDAddr is of a Nokial 6310 telephone
> >
> > I get the above error.
> >
> > Hcidump -x shows
> >
> >
> > < HCI Command: Create Connection(0x01|0x0005) plen 13
> > B6 81 35 57 60 00 18 CC 02 00 00 00 01
> >
> > > HCI Event: Command Status(0x0f) plen 4
> >
> > 00 01 05 04
> >
> > > HCI Event: Connect Complete(0x03) plen 11
> >
> > 1F 00 00 B6 81 35 57 60 00 01 00
> >
> > If I read the specs properly 0x1f is a 'unspecified error' ;-(
> >
> > What could be wrong ?
>
> show us "hciconfig -a" from the iPAQ.
hci0: Type: UART
BD Address: 00:02:C7:0D:85:96 ACL MTU: 128:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN AUTH
RX bytes:1181186 acl:3150 sco:0 events:1857 errors:0
TX bytes:220702 acl:2025 sco:0 commands:49 errors:0
Features: 0xff 0xff 0x05 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'familiar'
Class: 0x120112
Service Classes: Networking, Object Transfer
Device Class: Computer, Handheld
HCI Ver: 1.1 (0x1) HCI Rev: 0x72 LMP Ver: 1.1 (0x1) LMP Subver: 0x72
Manufacturer: Cambridge Silicon Radio (10)
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-12-13 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 22:56 [Bluez-users] L2Ping / Rfcomm connect : Function not implemented wim delvaux
2004-12-13 8:02 ` Marcel Holtmann
2004-12-13 10:47 ` wim delvaux [this message]
2004-12-13 11:01 ` Marcel Holtmann
2004-12-13 11:43 ` wim delvaux
2004-12-13 11:47 ` Marcel Holtmann
2004-12-13 11:59 ` wim delvaux
2004-12-13 12:04 ` Marcel Holtmann
2004-12-13 12:09 ` wim delvaux
2004-12-13 12:12 ` wim delvaux
2004-12-13 12:15 ` Marcel Holtmann
2004-12-13 12:18 ` wim delvaux
2004-12-13 12:31 ` Marcel Holtmann
2004-12-13 12:14 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412131147.13321.wim.delvaux@adaptiveplanet.com \
--to=wim.delvaux@adaptiveplanet.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox