Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ServerURI with IPv6 not supported for Windows #7

Closed
jpwsutton opened this issue Feb 4, 2016 · 2 comments
Closed

ServerURI with IPv6 not supported for Windows #7

jpwsutton opened this issue Feb 4, 2016 · 2 comments
Assignees
Milestone

Comments

@jpwsutton
Copy link
Member

migrated from Bugzilla #484496
status UNCONFIRMED severity normal in component MQTT-C for 1.2
Reported in version 1.2 on platform PC
Assigned to: Ian Craggs

Original attachment names and IDs:

On 2015-12-16 10:32:52 -0500, Juergen Kosel wrote:

If the server URI contains an IPv6 address, e.g.
"tcp://[2002:3e92:dead:beef:250:56ff:fe28:1234]:1883" (invalidated address in example)
then MQTTAsync_create fails with return value -2 on Windows machines.

If you use the same valid serverURI on a Linux machine, for example within test/test4.c, then the test passes.

On 2015-12-16 11:06:39 -0500, Juergen Kosel wrote:

Created attachment 258731
Partial fix for bug 484496

With this fix MQTTAsync_Create does not fail with -2 any more.
But there are other issues, which prevent MQTT and IPv6 from working on Windows.

On 2015-12-17 05:51:58 -0500, Juergen Kosel wrote:

Created attachment 258751
Patch to remove the leading '[' from IPv6 addresses

With this 2nd patch the socket could be created.
But connecting to a broker with IPv6 address still fails.

This was referenced Feb 16, 2016
@JuergenKosel JuergenKosel mentioned this issue Apr 7, 2016
@icraggs icraggs self-assigned this May 26, 2016
icraggs pushed a commit that referenced this issue May 26, 2016
@icraggs
Copy link
Contributor

icraggs commented May 26, 2016

I've added a fix to the fixes branch. As well as the persistence directory name, the socket initialization for IPv6 was not correct.

@icraggs icraggs added this to the 1.1 milestone May 31, 2016
@icraggs
Copy link
Contributor

icraggs commented May 31, 2016

Merged to develop.

@icraggs icraggs closed this as completed May 31, 2016
@frett27 frett27 mentioned this issue Jun 29, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants