OTBR: Can ping IPv4 (via NAT64) but not plain IPv6 #12302
Unanswered
schildbach
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm running OTBR in Docker on a Debian host with a ZBT-1 connected. It is fully IPv4+IPv6 (dualstack) enabled. From the host:
Now, when trying this within
ot-ctl(in the container), I get this:IPv4 + NAT64 appears to work as expected:
I can also ping the synthesized IPv6:
But pinging a plain IPv6 doesn't work:
Is this expected?
I have more or less followed the official instructions:
https://openthread.io/guides/border-router/build-docker and
https://openthread.io/guides/border-router/form-network
I did not yet bring up a second Thread node, as I don't have any. In future, I want to try add one of each Ikea Bilresa, Myggbett and Myggspray devices as well as a Tado "Smart Radiator Thermostat X".
My home router is an AVM FritzBox 7590. It obtains a /56 prefix from my Internet provider, and splits it into two /64 subnets (main and guests). I followed these instructions to operate a router behind the FritzBox, because I assume that's what OTBR is/needs. In a nutshell:
Within seconds after I changed these settings, my FritzBox allocated two /62 prefixes (labelled as "Delegated"). Sadly I cannot see where they are delegated to. These prefixes appear in none of my server's "ip a" command outputs and there is no mention in my router logs either.
Back on my host, both IPv4 and IPv6 forwarding is enabled by Docker already – I did not change this:
I manually enabled IPv6 router advertisements for my host network (yes, it's wireless not wired):
Two OTBR states that might be of interest:
Here is my Docker Compose. I even enabled IPv6 on the bridge network, although I guess that is useless for now as I need to use
network_mode: hostanyway.(Side question: many examples add the baud rate and flow control params to the OT_RCP_DEVICE url. Is this recommended? In my case it seems to be auto-detected just fine.)
And here is my log file:
Beta Was this translation helpful? Give feedback.
All reactions