Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
IPv6 addresses do not work for bridging. #886
Using IPv6 addresses for bridging brokers currently does not work with Mosquitto. This doesn't appear in the documentation anywhere either.
In the meantime, if this requires a lot of code changes a documentation update to specify that only IPv4 sockets are supported for bridges at this time should be made.
A couple things will need changed to make IPv6 addresses work:
changed the title from
IPv6 bridging not supported
IPv6 addresses do not work for bridging.
Jul 19, 2018
@toast-uz Please look at the bridge section of the mosquitto.conf documentation, you'll see that it does not specify that the address has to be IPv4, it simply says address and port. This means one of two things, this is a bug and it was intended to be supported with both IPv6 and IPv4 addresses, or this is intentional behavior as IPv4 addresses were the only ones intended to be supported for bridges. I'm not sure what you mean mean by changing the subject to clarify this is a bug, as there is not official guide line or structure for issue reporting. The nature of this ticket is ambiguous as the documentation is ambiguous. I changed the title to hopefully be a little clearer as to what I am reporting in this issue.
Essentially, the issue list is for the users search known bugs. But I guess mosquitto's community is too flexible to realize the original purpose. There are over 200 issues! Therefore, I am asking the not a bug reporters to close the issue and post at mosquitto-dev ML.
If your real insist is reporting a critical bug on the document, keep your issue. If not, your real insist is a new request for supporting IPv6 bridge, I am asking to close this issue and post at mosquitto-dev ML.
Sorry for your inconvenience.
seriously? let me reword the original (valid) bug report
First, let's set up a v6 only broker, happily listening via a v6 address in the bind_address or listener directives....
Now, let's make a bridge connection to that via the ipv6 name "localhost6"
See how it accepts v6 addresses and v6 resolutions of names everywhere except the "address" directive to a bridge? That's what this bug is for. I don't believe that could be considered anything other than a bug.