Hi @t1nux
Disabling IPv6 on the main router will not affect the Thread subnet.
Can you capture the IPv6 address allocation process on your PC with Wireshark when IPv6 is enabled on your main router?
Hi @lancer
I totally agree that the main router's IPv6 settings do not influence the thread network, but routing to the thread network is obviously influenced by certain IPv6 settings on the main router, as access to the thread network only works for the weird conditions I described above.
I do not know where the issue lies, but it must be either the main router or the S200. I hope we can find a working and reliable solution soon, as I now have added a number of additional matter/thread devices, and I would like to further extend my smart home based on matter/thread.
I will see how to obtain the wireshark log for IPv6 address allocation in the next days.
Sorry, I did not manage to get the wireshark logs. However, I am pretty sure the issue is with the S200 and not the main router, my PC or the home assistant server, see below for details.
During the following tests I was continuously pinging a thread device in the thread network provided by wpan0 on the S200. Pinging was initiated from my PC on the main network. The main router (not the S200) is set to native IPv6 and was rebooted quite some time before starting the tests. The S200 it also connected to that same main network on the WAN port.
When I start the test, I reboot the S200. Until the boot process is done, I obviously do not get pings through, but right after rebooting the S200 is done, I am getting a couple of successful pings. This is not successful for more than maybe 20 sec. After that, I cannot get any more successful pings.
If I now go to the luci interface in the S200, to Network > Interfaces, and I restart WAN6, I can again get a few successful pings from the thread device.
As I did not change anything on the main router or my PC and just made a changes on the S200, the issues must lie there.
I do not know how to troubleshoot this, but I am kindly asking for help on how to do this, as it is quite clearly an issue on the S200. I can provide outputs from the luci interface, or from commands executed via SSH.
Thanks in advance, t1nux
Hi @t1nux
Before commissioning, you need to make sure your phone can receive the mDNS service information sent by S200, and the OMR address of S200 can be pinged from your phone. I also tested a Raspberry Pi TBR and an Apple Homepod mini connected directly to the main router, and they also failed to commission the Matter device. Is the IPv6 address assigned by your main router a global ipv6 address?
Hi @lancer
I should probably rename the topic of this whole conversation. I initially thought it was about commissioning, but now I know it is about reaching (eg. pinging) the thread devices when certain IPv6 setting are in place. I will try to rename it later.
So, I can get everything working (see my post from August 4), but the conditions are unstable, temporary, and not persistent between reboots of the S200 or the main router. All info is given in that post. In this unstable but working state, everything works, i.e. commissioning (via mobile phone), pinging (from PC or phone), and general operation of thread devices from home-assistant.
As I wrote in my post form August 21, it seems clear that the issue is related to the S200. Please have a look at that post for all the info.
And for you question from your last post, in normal IPv6 operation (i.e. when things are not working), the S200 does seem to get a global IPv6 address. However, I think this is also the case in the "working" case, see the data in the post from August 04 (ip addr output from the S200).
Hi @t1nux
The new firmware version is coming soon. Could you help try it out before the official release?
Hi @lancer
Yes, I can try the new firmware. Currently, I have the most recent version installed (4.1.5), and there is no beta version that is more recent on the FW download page. If you could upload a beta version, I'd be happy to give it a try.
Hi @t1nux
I have uploaded the S200 4.7.0-0500 beta firmware, you can download from GL.iNet download center .
This is still not working using 4.7.0-0500 beta. The issues actually got worse, because the work-around trick I mentioned of switching the main router to stateful does not work anymore.
When trying to continuously ping a thread device with the not-working (but default) settings on the main router, restarting the WAN6 device still gets a few pings through.
The issues with the S200 remains.
PS: I'm using eth0 as backbone router interface. I mentioned this in one of the posts, I just wanted to mention it again.
Hi @t1nux
Could you please check this issue? Why can ot-ctl ping work, but sys ping fails? · Issue #10677 · openthread/openthread · GitHub
Hi @lancer
I had a look at the issue. It seems the route that was missing for you is there in my case. I do not know what else to try, but if you want me to run any commands on the S200 via SSH I can do that and post the output here.
PS: I went back to firmware 4.1.5 as the trick described in my post from Aug 4 did not work anymore on 4.7.0.
Hi @t1nux
Can you give me the results of using ping and ot-ctl ping commands to verify on the S200?