Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BLE IPSP sample doesn't work on raspberry pi 4 with nrf52840_mdk board #29683

Closed
hguomin8 opened this issue Nov 1, 2020 · 3 comments
Closed
Assignees
Labels
area: Bluetooth area: Networking bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: low Low impact/importance bug

Comments

@hguomin8
Copy link

hguomin8 commented Nov 1, 2020

Describe the bug
Follow the steps in the IPSP sample document to test BLE IPSP connection between RPI4 and nrf52840_mdk board, while I can ping nrf52840_mdk successfully with scoped IPv6 address, but can't ping with static ipv6 address, also can't connect to the board using telnet, please check the screen shot below.

To Reproduce
Steps to reproduce the behavior:

  1. cd zephyr\samples\bluetooth\ipsp
  2. west build -b nrf52840_mdk . -DCONF_FILE="prj_dbg.conf"
  3. west flash
  4. See error in below screen shot

Expected behavior
Can ping and telnet via static ipv6 address

Impact
Can not make any progress without this ipsp feature...

Logs and console output

  1. Steps and ouputs on RPI 4
    image

  2. net shell logs on nrf52840_board
    image

Environment (please complete the following information):

  • OS: (Raspberry pi OS(buster, kernel 5.4.51-v7l+))
  • Zephyr branch: master

Additional context

  1. In below environment, it works
  • OS: Raspberry pi OS(buster, kernel 4.19.97-v7+)
  • Zephry branch: v2.3.0
  1. In below environment, can ping with static ipv6 address, but can not connect via telnet
  • OS: Raspberry pi OS(buster, kernel 5.4.51-v7l+)
  • Zephyr branch: v2.3.0
@hguomin8 hguomin8 added the bug The issue is a bug, or the PR is fixing a bug label Nov 1, 2020
@MaureenHelm MaureenHelm added the priority: low Low impact/importance bug label Nov 3, 2020
@Vudentz
Copy link
Contributor

Vudentz commented Nov 5, 2020

We will probably need some HCI logs, but it does looks like this is a Linux problem rather than Zephyr.

@hguomin8
Copy link
Author

hguomin8 commented Nov 6, 2020

Hmm...this issue can be reproduced easily, look forward you guys can help to fix it, I am not specialize in kernel development

@carlescufi
Copy link
Member

@hguomin8 could you please report this to the Linux BlueZ mailing list, since this looks like a BlueZ issue? I will close this issue but feel free to reopen it if you find out this to be a Zephyr issue instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth area: Networking bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants