Multicast ipv6 addressing ff02::1%<interface>

[dcomins]

Hi,
I have some nodes which work on ipv6 connected to my Pi, i have a python program running with Coapthon and i am able to communicating with them using their unicast ip. Therefore when i want to use multicast coap (with the addres ff02::1%fslthr0, where fslthr0 is my TUN interface) it doesnt work. Any solution? This library allows the use of an ipv6 multicast address with interface (%fslthr0)?

Note: I can ping the nodes using the all addres ff02::1%fslthr0. But if I only ping ff02::1 it doesn work, so i need to put ff02::1%fslthr0 address in coapthon.
Best
Diego C.

[Tanganelli]

Can you ping without specifying the interface with unicast addresses? Il giorno gio 7 giu 2018 alle ore 10:30 dcomins <[email protected]> ha scritto:

…

Hi, I have some nodes which work on ipv6 connected to my Pi, i have a python program running with Coapthon and i am able to communicating with them using their unicast ip. Therefore when i want to use multicast coap (with the addres ff02::1%fslthr0, where fslthr0 is my TUN interface) it doesnt work. Any solution? This library allows the use of an ipv6 multicast address with interface (%fslthr0)? *Note:* I can ping the nodes using the all addres ff02::1%fslthr0. But if I only ping ff02::1 it doesn work, so i need to put ff02::1%fslthr0 address in coapthon. Best Diego C. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#114>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGb2-mLhJwFEtyg1owflYnIXwXmooHEeks5t6OSagaJpZM4Ud9hq> .

[dcomins]

Yes, I ping with no problems without specifying the interface with unicast addresses. But for pinging a multicast address in ipv6 it is mandatory to specify the interface, see: https://superuser.com/questions/840767/ipv6-multicast-address-for-all-nodes-on-network

Txthings library also had problems with this multicast issue, see the second comment from "sjlongland": mwasilak/txThings#16

[dcomins]

Tanganelli can you fix this issue? I think there are many people interested on it.

[Tanganelli]

Yes, I will try to fix it in the next weeks. Sorry but I am really busy at the moment. Il giorno lun 11 giu 2018 alle ore 13:41 dcomins <[email protected]> ha scritto:

…

Tanganelli can you fix this issue? I think there are many people interested on it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#114 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGb2-gdC9DK0be-B9PzQWA978ynbHB5eks5t7kltgaJpZM4Ud9hq> .

[dcomins]

Ok, I really appreciate it. Thanks in advance.
Diego C.

[dcomins]

Have you made some advances Tanganelli?

[Tanganelli]

No sorry, I am more than busy right now. Il giorno lun 2 lug 2018 alle ore 13:24 dcomins <[email protected]> ha scritto:

…

Have you made some advances Tanganelli? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#114 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGb2-oknscypmDCcIDAsNZvfYfdXHma7ks5uCgLlgaJpZM4Ud9hq> .

[pchwalek]

I struggled with this issue and found the solution to be binding the socket to my interface. After doing so, multicast sending worked!! =)

(python3) in client\coap.py, for binding to the wpan0 interface, I added:
self._socket.setsockopt(socket.SOL_SOCKET, 25, str("wpan0" + '\0').encode('utf-8'))

[aslehv]

Is this solved? I am trying to multicast aswell to ff03::1 or ff02::1 :) I could not get, @pchwalek solution to work.