public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "chenjian" <ustcchenjian@163.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] l2ping issues
Date: Fri, 16 Jun 2006 21:29:52 +0800 (CST)	[thread overview]
Message-ID: <4492B250.000111.26041@bj163app70.163.com> (raw)
In-Reply-To: <mailman.0.1150463548.25144.bluez-users@lists.sourceforge.net>


[-- Attachment #1.1: Type: text/plain, Size: 1563 bytes --]

hi guys, I have 2 issues with l2ping. bluz version is as the following:
rpm info:

linux-l20w:~ # rpm -qa|grep bluez

bluez-utils-2.24-17

bluez-libs-2.24-10

1. l2ping failed to ping itself
linux-l20w:~ # hciconfig
hci0:   Type: USB
        BD Address: 00:0E:9B:DD:E4:D1 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN
        RX bytes:5545 acl:3 sco:0 events:193 errors:0
        TX bytes:4482 acl:3 sco:0 commands:168 errors:0

linux-l20w:~ # lsmod|grep -E "l2cap|rfcomm|bcm203x"
rfcomm                 32408  5
l2cap                  20740  14 hidp,bnep,rfcomm
bluetooth              41188  10 hidp,bnep,rfcomm,l2cap,hci_vhci,hci_usb
linux-l20w:~ # l2ping 00:0E:9B:DD:E4:D1
Can't connect: No route to host

Is this normal or correct?

2. I can run hciemu to emulate a faked bluetooth device, but the l2ping still failed. Is that normal or correct?
linux-l20w:~ # modprobe hci_vhci
linux-l20w:~ # ls /dev/vhci -l
crw-rw---- 1 root root 10, 62 Jun 15 07:51 /dev/vhci
linux-l20w:~ # hciemu 00:0E:9B:DD:E4:D2
linux-l20w:~ # hciconfig
hci0:   Type: USB
        BD Address: 00:0E:9B:DD:E4:D1 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN
        RX bytes:203 acl:0 sco:0 events:28 errors:0
        TX bytes:876 acl:0 sco:0 commands:28 errors:0

hci1:   Type: VHCI
        BD Address: 00:0E:9B:DD:E4:D2 ACL MTU: 192:8 SCO MTU: 64:0
        UP RUNNING PSCAN ISCAN
        RX bytes:0 acl:0 sco:0 events:15 errors:0
        TX bytes:569 acl:0 sco:0 commands:15 errors:0

linux-l20w:~ # l2ping  00:0E:9B:DD:E4:D2
Can't connect: Host is down


[-- Attachment #1.2: Type: text/html, Size: 2811 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

       reply	other threads:[~2006-06-16 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1150463548.25144.bluez-users@lists.sourceforge.net>
2006-06-16 13:29 ` chenjian [this message]
2006-06-17 10:16   ` [Bluez-users] l2ping issues 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=4492B250.000111.26041@bj163app70.163.com \
    --to=ustcchenjian@163.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