Re: [riot-devel] Border-router and multicast

2016-05-17 Thread Martine Lenders
Hi, Sorry forgot to answer this. > I did try but ping6 does not receive anything > Did you do any more set up? As I said: I wasn't able to reach the multicast address either (at least after the first reply + the reply didn't seem to be forwarded by the BR [something I seem to have forgotton to

Re: [riot-devel] Border-router and multicast

2016-05-17 Thread Baptiste Clenet
Martine? 2016-05-13 20:45 GMT+02:00 Baptiste Clenet : > 2016-05-12 21:03 GMT+02:00 Baptiste Clenet : >> Thanks Martine, I will try tomorrow >> >> 2016-05-12 14:10 GMT+02:00 Martine Lenders : >>> Hi, >>> >>> Ah the problem seems to

Re: [riot-devel] Border-router and multicast

2016-05-13 Thread Baptiste Clenet
2016-05-12 21:03 GMT+02:00 Baptiste Clenet : > Thanks Martine, I will try tomorrow > > 2016-05-12 14:10 GMT+02:00 Martine Lenders : >> Hi, >> >> Ah the problem seems to be that for some reason Linux elects a link-local >> address for the ping, which is

Re: [riot-devel] Border-router and multicast

2016-05-12 Thread Baptiste Clenet
Thanks Martine, I will try tomorrow 2016-05-12 14:10 GMT+02:00 Martine Lenders : > Hi, > > Ah the problem seems to be that for some reason Linux elects a link-local > address for the ping, which is of course due to the fact, that there is no > global address assigned to

Re: [riot-devel] Border-router and multicast

2016-05-12 Thread Martine Lenders
Hi, Ah the problem seems to be that for some reason Linux elects a link-local address for the ping, which is of course due to the fact, that there is no global address assigned to the interface and that the hop limit seems to be set to short (it is 1). So I did the following sudo ip route add

Re: [riot-devel] Border-router and multicast

2016-05-12 Thread Martine Lenders
Hi Baptiste, yeah in that case multicast seems like the best thing to go. But how about using an actual global address then: (ff:1e::1 e.g.; 10 flag = non-permanent, e scope = global). With the hint by Kaspar I was able to get the pings through the interface, but apparently the border router does

Re: [riot-devel] Border-router and multicast

2016-05-11 Thread Martine Lenders
Hi again, 2016-05-11 21:42 GMT+02:00 Martine Lenders : > Hi Baptist, > > First of all, sorry for the late reply. > > 2016-05-11 10:05 GMT+02:00 Baptiste Clenet : > >> Ok Martine, >> >> In the start_network.sh, create_tap(), you route >> ip route add

Re: [riot-devel] Border-router and multicast

2016-05-10 Thread Martine Lenders
Sorry, was (and still am) otherwise occupied. Will look into it tonight, tomorrow at the latest though. Regards, Martine 2016-05-10 18:05 GMT+02:00 Baptiste Clenet : > Ok Martine, Have you found any solution yet? > > 2016-05-10 9:48 GMT+02:00 Martine Lenders

Re: [riot-devel] Border-router and multicast

2016-05-10 Thread Martine Lenders
Hi Baptiste, since IEEE 802.15.4 itself is not a multicast medium (it only supports broadcast), and we don't have MLD implemented at this point (which configures routers for multicast), multicast is indeed tricky at the moment. Let me try something out and I come back to you. Cheers, Martine

Re: [riot-devel] Border-router and multicast

2016-05-10 Thread Baptiste Clenet
Thanks Alex for your answer. 2016-05-09 19:07 GMT+02:00 Alexander Aring : > Hi, > > On Mon, May 09, 2016 at 06:20:48PM +0200, Baptiste Clenet wrote: >> 2016-05-09 16:44 GMT+02:00 Alexander Aring : >> > On Mon, May 09, 2016 at 04:24:34PM +0200, Baptiste

Re: [riot-devel] Border-router and multicast

2016-05-09 Thread Alexander Aring
Hi, On Mon, May 09, 2016 at 06:20:48PM +0200, Baptiste Clenet wrote: > 2016-05-09 16:44 GMT+02:00 Alexander Aring : > > On Mon, May 09, 2016 at 04:24:34PM +0200, Baptiste Clenet wrote: > >> Hi Martine, > >> Thank you for the answer. > >> Ok ff04::1 is also a multicast

Re: [riot-devel] Border-router and multicast

2016-05-09 Thread Alexander Aring
On Mon, May 09, 2016 at 06:20:48PM +0200, Baptiste Clenet wrote: > 2016-05-09 16:44 GMT+02:00 Alexander Aring : > > On Mon, May 09, 2016 at 04:24:34PM +0200, Baptiste Clenet wrote: > >> Hi Martine, > >> Thank you for the answer. > >> Ok ff04::1 is also a multicast address so

Re: [riot-devel] Border-router and multicast

2016-05-09 Thread Baptiste Clenet
Martine, I added ifconfig 7 add ff04::1 to board B and I couldn't ping f04::1 from Linux. Any other solution? 2016-05-09 18:20 GMT+02:00 Baptiste Clenet : > 2016-05-09 16:44 GMT+02:00 Alexander Aring : >> On Mon, May 09, 2016 at 04:24:34PM +0200,

Re: [riot-devel] Border-router and multicast

2016-05-09 Thread Alexander Aring
On Mon, May 09, 2016 at 04:24:34PM +0200, Baptiste Clenet wrote: > Hi Martine, > Thank you for the answer. > Ok ff04::1 is also a multicast address so I add it to every board with > gnrc_networking and I should be able to ping them with this multicast > address. > Shouldn't I use: > ifconfig 7 add

Re: [riot-devel] Border-router and multicast

2016-05-09 Thread Baptiste Clenet
Hi Martine, Thank you for the answer. Ok ff04::1 is also a multicast address so I add it to every board with gnrc_networking and I should be able to ping them with this multicast address. Shouldn't I use: ifconfig 7 add multicast ff04::1 ? I'm missing something here, could give me an explanation

[riot-devel] Border-router and multicast

2016-05-09 Thread Baptiste Clenet
Hi, My set up: Linux -> board A (border router) board B (gnrc_networking) I've set up the border router, I can ping board B by changing fe80 by 2001:db8:: inside Linux, but I used the multicast address ff02::1 to send frames to all my nodes and this does not work. How can I do that with