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

Setting the port to ::1:2000 causes error #66

Open
tonnenpinguin opened this issue Jan 16, 2018 · 12 comments
Open

Setting the port to ::1:2000 causes error #66

tonnenpinguin opened this issue Jan 16, 2018 · 12 comments
Assignees
Labels
Milestone

Comments

@tonnenpinguin
Copy link

When setting the port to ::1:2000 (as mentioned in the comment) emqttd exits with the following error message.

15:13:40.661 [error] Error generating configuration in phase transform_datatypes
15:13:40.661 [error] Error transforming datatype for: mqtt.sn.port
15:13:40.661 [error] "::1:20000" cannot be converted to a(n) integer

Is setting the port to ::1:xxxx even required when trying to get IPv6 only clients to connect with the MQTT-SN bridge?
Thanks in advance!

@grutabow
Copy link
Contributor

emq-sn will allow binding itself on an ipv6 address in next official release.

@emqplus emqplus added the bug label Jan 17, 2018
@emqplus emqplus added this to the 2.3.4 milestone Jan 17, 2018
@tonnenpinguin
Copy link
Author

Thanks for the quick reply!
Alright, I'll resume testing in a week then :)

@manchoz
Copy link

manchoz commented Jan 30, 2018

Still unable to get IPv6 working after upgrading to v2.3.4. With mqtt.sn.port = ::1:1884 emq_sn exits with:

[error] Supervisor emq_sn_sup had child emq_sn_udp_server started with esockd_udp:server(mqtt_sn, {"::1",1884}, [], {emq_sn_gateway_sup,start_gateway,[1,false]}) at undefined exit with reason {'EXIT',{function_clause,[{esockd_udp,server,[mqtt_sn,{"::1",1884},[],{emq_sn_gateway_sup,start_gateway,[1,false]}],[{file,"src/esockd_udp.erl"},{line,48}]},{supervisor,do_start_child,2,[{file,"supervisor.erl"},{line,365}]},{supervisor,start_children,3,[{file,"supervisor.erl"},{line,348}]},{supervisor,init_children,2,[{file,"supervisor.erl"},{line,314}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,365}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,333}]},{proc_lib,init_p_do_apply,...}]}} in context start_error

@tonnenpinguin
Copy link
Author

tonnenpinguin commented Jan 30, 2018

I'm seeing the same issue as @manchoz.
This is on a clean install on a raspberry pi 3 running the latest raspbian.

@emqplus
Copy link
Contributor

emqplus commented Feb 1, 2018

@manchoz @tonnenpinguin This issue has been fixed in esockd library. But both the emq-sn and emqttd projects still depends on the v5.2 of esockd.

I tagged esockd v5.2.1 and fixed the dependencies in the Makefile. Please clean and build the EMQ broker from latest master branch.

@emqplus emqplus modified the milestones: 2.3.4, 2.3.5 Feb 1, 2018
@tonnenpinguin
Copy link
Author

tonnenpinguin commented Feb 3, 2018

Now it works :)
Thanks @emqplus!

@manchoz
Copy link

manchoz commented Feb 5, 2018

Confirmed working for me too. Thanks @emqplus!

@tonnenpinguin
Copy link
Author

Now I'm running into the same issue again after upgrading to 3.0 :(

Any ideas @emqplus?

@gilbertwong96
Copy link
Contributor

gilbertwong96 commented Oct 9, 2018 via email

@tonnenpinguin
Copy link
Author

Thanks for the quick reply!
Is there an ETA available already?

@gilbertwong96
Copy link
Contributor

gilbertwong96 commented Oct 9, 2018 via email

@HJianBo HJianBo modified the milestones: 2.3.5, 4.0-rc.5 Jan 3, 2020
@HJianBo
Copy link
Member

HJianBo commented Jan 3, 2020

Hi, guys. Sorry so delay replying here

We will ensure it before v4.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants