From: Steve Brown <sbrown@cortland.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: meshctl: Can't connect via Node Identity advertisement
Date: Sun, 03 Dec 2017 16:39:34 -0700 [thread overview]
Message-ID: <1512344374.16639.18.camel@ewol.com> (raw)
Connect via Net ID works without a problem.
I'm using meshctl with zephyr's mesh_shell (upstream version)
I provision the shell and turn on it's gatt-proxy. Then I exit meshctl,
run it again and issue a "connect 0". It reconnects to the mesh without
a problem.
If I turn off the shell's gatt-proxy, start meshctl, issue a
"connect 0" and then issue a shell "ident". I get no connection. The
ident command only transmits advertisements for a short period of time.
The CONN_TYPE_IDENTITY path in parse_mesh_service_data() seems broken.
The comparison of data[0] and connection.type fails. The value of
data[0] is 1 (CONN_TYPE_IDENTITY) and the value of connection.type is
0.
Below is sniffer output of the two advertisements.
Steve
Net ID Advertisement
systime=1512335672 freq=2402 addr=8e89bed6 delta_t=1000.969 ms rssi=-20
40 1a d0 59 81 b8 f1 cf 02 01 06 03 03 28 18 0c 16 28 18 00 d4 76 79 43 3f db 10 4a bf 47 10
Advertising / AA 8e89bed6 (valid)/ 26 bytes
Channel Index: 37
Type: ADV_IND
AdvA: cf:f1:b8:81:59:d0 (random)
AdvData: 02 01 06 03 03 28 18 0c 16 28 18 00 d4 76 79 43 3f db 10 4a
Type 01 (Flags)
00000110
LE General Discoverable Mode
BR/EDR Not Supported
Type 03 (16-bit Service UUIDs)
1828
Type 16 (Service Data)
UUID: 1828, Additional: 00 d4 76 79 43 3f db 10 4a
Data: d0 59 81 b8 f1 cf 02 01 06 03 03 28 18 0c 16 28 18 00 d4 76 79 43 3f db 10 4a
CRC: bf 47 10
Node Identity Advertisement
systime=1512335702 freq=2402 addr=8e89bed6 delta_t=30492.935 ms rssi=-19
40 22 d0 59 81 b8 f1 cf 02 01 06 03 03 28 18 14 16 28 18 01 cb 3b d5 82 b5 1f 32 00 c6 36 a1 be 9b 88 c5 b6 fd e1 b3
Advertising / AA 8e89bed6 (valid)/ 34 bytes
Channel Index: 37
Type: ADV_IND
AdvA: cf:f1:b8:81:59:d0 (random)
AdvData: 02 01 06 03 03 28 18 14 16 28 18 01 cb 3b d5 82 b5 1f 32 00 c6 36 a1 be 9b 88 c5 b6
Type 01 (Flags)
00000110
LE General Discoverable Mode
BR/EDR Not Supported
Type 03 (16-bit Service UUIDs)
1828
Type 16 (Service Data)
UUID: 1828, Additional: 01 cb 3b d5 82 b5 1f 32 00 c6 36 a1 be 9b 88 c5 b6
Data: d0 59 81 b8 f1 cf 02 01 06 03 03 28 18 14 16 28 18 01 cb 3b d5 82 b5 1f 32 00 c6 36 a1 be 9b 88 c5 b6
CRC: fd e1 b3
next reply other threads:[~2017-12-03 23:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 23:39 Steve Brown [this message]
2017-12-04 12:36 ` meshctl: Can't connect via Node Identity advertisement Johan Hedberg
2017-12-04 13:06 ` Steve Brown
2017-12-04 13:59 ` Steve Brown
2017-12-04 15:05 ` Johan Hedberg
2017-12-04 15:21 ` Steve Brown
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=1512344374.16639.18.camel@ewol.com \
--to=sbrown@cortland.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.