-
Notifications
You must be signed in to change notification settings - Fork 2k
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
nrf52: Not able to add global or ULA address to interface #13280
Comments
I guess @haukepetersen could be familiar with this. Haven't tried it with other radios yet. |
@haukepetersen @miri64 The goal of it is basically to use BLE instead of slip or something else. I am not sure, if this is even possible. I guess the header compression in linux is still missing and therefore it is not able to understand the header. But I am not that familiar with the status of it. |
Have you the 6LoWPAN module loaded? Header compression should be possible with that. Most of what can be found in the |
Yes.
In openwrt it was a bit different, as a I remember. Yes, but the connection changed. It's not 1 anymore. The last time I checked you needed to connect it with 2. But I don't have an idea what the difference is. |
Which one is the router? For Linux as the router you need to install and run radvd to advertise the global prefix. See https://github.com/RIOT-Makers/wpan-raspbian/wiki/Setup-native-6LoWPAN-router-using-Raspbian-and-RADVD. |
The Acher C7 (OpenWRT) is the router. It's already in OpenWRT. I don't think they use radvd for router advertisements. |
OpenWRT uses the |
@Citrullin I am not 100% but I have an assumption where this might be coming from: in the default configuration, one can only set I think 1 additional address per interface. So when you add the first ULA, that memory spot is taken and the netif will not accept any additional addresses. But whats strange is, that @miri64 could you quickly remind us what the config value is to increase the number of addresses per interface? Thx Aside from that I don't have much experience connecting RIOT BLE nodes to Linux, thats something somewhere on my TODO list to explore this a little further... |
https://doc.riot-os.org/group__net__gnrc__netif__conf.html#ga366596e311b4a450887a1a180ae66fb3 |
Description
Not sure, if this is a bug or if I just configured it not correct. I already wrote an email, but I guess this setup is a bit too complicated for an email.
Fritzbox cable acts as a Modem (bridge mode) and is connected to an Archer C7 v2. The Archer acts as the main router to the internet. The router gets an /56 range via prefix delegation.
I compiled a fresh OpenWRT (v19.07.1) with all necessary 6lowpan_bluetooth modules.
The Archer C7 uses a BLE USB Stick. After connecting the nrf52832 device to the router, I tried to add a global and ULA address to the interface.
The issue also happens when Bluetooth is not connected.
and
Both don't work and the shell is not responding. Instead I can just execute the next command. After checking the interface with ifconfig again, the interface still has only the link local address.
The configured interface in OpenWRT looks like this and this.
Steps to reproduce the issue
ble info
on the RIOT shell.MAC_ADDR for example CC:C5:51:01:8E:8C
Replace fe80::ccc6:52ff:fe01:8e8c with the address of your nrf52 device
You should be able to reach the device. If not, something went already wrong.
9. Try to add your global and ULA address to your nrf52. If your bt0 interface has the prefix:
2aaa:8aaa:baaa:b700::1/60
or2aaa:8aaa:baaa:b700::1/64
Give the nrf52 the suffix ::2. In this case:
The same doesn't work the configured ULA:
You need to get the ID of your interface first with
ifconfig
. In this case 9.Expected results
A configured network interface with the ULA and global address.
or
Error message
Actual results
No response from the shell
Versions
OpenWRT 19.07.1
Compiles and flashed RIOT on commit c310bfb
The text was updated successfully, but these errors were encountered: