Mosquitto - EMQX bridge connection name
1) How to determine the Mosquitto bridge connection name.
The snippet written below is from the EMQx documentation (http://emqtt.io/docs/v2/bridge.html#mosquitto-conf)
connection emqttd
address 127.0.0.1:2883
topic sensor/# out 2
the connection name - emqttd is written on what basis?
2) I have a tcp connection open from EMQX on the host 172.22.25.53 and port 2883.
When i try connecting from the same system. It works absolutely fine. But from a different system, I get this error
C:Program Filesmosquitto>mosquitto.exe -c mosquitto.conf -v
1542182003: mosquitto version 1.5.3 starting
1542182003: Config loaded from mosquitto.conf.
1542182003: Opening ipv6 listen socket on port 1883.
1542182003: Opening ipv4 listen socket on port 1883.
1542182003: Bridge local.AOI146.emq@172.22.25.53 doing local SUBSCRIBE on topic BA/#
1542182003: Connecting bridge emq@172.22.25.53 (172.22.25.53:2883)
1542182003: Bridge AOI146.emq@172.22.25.53 sending CONNECT
1542182003: Error creating bridge: Unknown error.
1542182003: Warning: Unable to connect to bridge emq@172.22.25.53.
My mosquitto.conf file is:
connection emqx
address 172.22.25.53:2883
cleansession false
topic AB/# both 2
mqtt mosquitto emq
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
add a comment |
1) How to determine the Mosquitto bridge connection name.
The snippet written below is from the EMQx documentation (http://emqtt.io/docs/v2/bridge.html#mosquitto-conf)
connection emqttd
address 127.0.0.1:2883
topic sensor/# out 2
the connection name - emqttd is written on what basis?
2) I have a tcp connection open from EMQX on the host 172.22.25.53 and port 2883.
When i try connecting from the same system. It works absolutely fine. But from a different system, I get this error
C:Program Filesmosquitto>mosquitto.exe -c mosquitto.conf -v
1542182003: mosquitto version 1.5.3 starting
1542182003: Config loaded from mosquitto.conf.
1542182003: Opening ipv6 listen socket on port 1883.
1542182003: Opening ipv4 listen socket on port 1883.
1542182003: Bridge local.AOI146.emq@172.22.25.53 doing local SUBSCRIBE on topic BA/#
1542182003: Connecting bridge emq@172.22.25.53 (172.22.25.53:2883)
1542182003: Bridge AOI146.emq@172.22.25.53 sending CONNECT
1542182003: Error creating bridge: Unknown error.
1542182003: Warning: Unable to connect to bridge emq@172.22.25.53.
My mosquitto.conf file is:
connection emqx
address 172.22.25.53:2883
cleansession false
topic AB/# both 2
mqtt mosquitto emq
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
add a comment |
1) How to determine the Mosquitto bridge connection name.
The snippet written below is from the EMQx documentation (http://emqtt.io/docs/v2/bridge.html#mosquitto-conf)
connection emqttd
address 127.0.0.1:2883
topic sensor/# out 2
the connection name - emqttd is written on what basis?
2) I have a tcp connection open from EMQX on the host 172.22.25.53 and port 2883.
When i try connecting from the same system. It works absolutely fine. But from a different system, I get this error
C:Program Filesmosquitto>mosquitto.exe -c mosquitto.conf -v
1542182003: mosquitto version 1.5.3 starting
1542182003: Config loaded from mosquitto.conf.
1542182003: Opening ipv6 listen socket on port 1883.
1542182003: Opening ipv4 listen socket on port 1883.
1542182003: Bridge local.AOI146.emq@172.22.25.53 doing local SUBSCRIBE on topic BA/#
1542182003: Connecting bridge emq@172.22.25.53 (172.22.25.53:2883)
1542182003: Bridge AOI146.emq@172.22.25.53 sending CONNECT
1542182003: Error creating bridge: Unknown error.
1542182003: Warning: Unable to connect to bridge emq@172.22.25.53.
My mosquitto.conf file is:
connection emqx
address 172.22.25.53:2883
cleansession false
topic AB/# both 2
mqtt mosquitto emq
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
1) How to determine the Mosquitto bridge connection name.
The snippet written below is from the EMQx documentation (http://emqtt.io/docs/v2/bridge.html#mosquitto-conf)
connection emqttd
address 127.0.0.1:2883
topic sensor/# out 2
the connection name - emqttd is written on what basis?
2) I have a tcp connection open from EMQX on the host 172.22.25.53 and port 2883.
When i try connecting from the same system. It works absolutely fine. But from a different system, I get this error
C:Program Filesmosquitto>mosquitto.exe -c mosquitto.conf -v
1542182003: mosquitto version 1.5.3 starting
1542182003: Config loaded from mosquitto.conf.
1542182003: Opening ipv6 listen socket on port 1883.
1542182003: Opening ipv4 listen socket on port 1883.
1542182003: Bridge local.AOI146.emq@172.22.25.53 doing local SUBSCRIBE on topic BA/#
1542182003: Connecting bridge emq@172.22.25.53 (172.22.25.53:2883)
1542182003: Bridge AOI146.emq@172.22.25.53 sending CONNECT
1542182003: Error creating bridge: Unknown error.
1542182003: Warning: Unable to connect to bridge emq@172.22.25.53.
My mosquitto.conf file is:
connection emqx
address 172.22.25.53:2883
cleansession false
topic AB/# both 2
mqtt mosquitto emq
mqtt mosquitto emq
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
asked Nov 14 '18 at 8:01
Abishek RankaAbishek Ranka
14
14
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The connection name is the value after connection in the configuration file. As described in the bridge section of the mosquitto.conf man page
e.g.
connection foo
Will result in a connection name of foo.
172.22.25.53 is in the reserved range 172.16.0.0 – 172.31.255.255, I'm going to guess you are running emq in a docker container and you are trying to access the container using it's Docker internal IP address. You will need to expose the port on your host machine to be able to access it from a remote machine.
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295459%2fmosquitto-emqx-bridge-connection-name%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The connection name is the value after connection in the configuration file. As described in the bridge section of the mosquitto.conf man page
e.g.
connection foo
Will result in a connection name of foo.
172.22.25.53 is in the reserved range 172.16.0.0 – 172.31.255.255, I'm going to guess you are running emq in a docker container and you are trying to access the container using it's Docker internal IP address. You will need to expose the port on your host machine to be able to access it from a remote machine.
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
add a comment |
The connection name is the value after connection in the configuration file. As described in the bridge section of the mosquitto.conf man page
e.g.
connection foo
Will result in a connection name of foo.
172.22.25.53 is in the reserved range 172.16.0.0 – 172.31.255.255, I'm going to guess you are running emq in a docker container and you are trying to access the container using it's Docker internal IP address. You will need to expose the port on your host machine to be able to access it from a remote machine.
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
add a comment |
The connection name is the value after connection in the configuration file. As described in the bridge section of the mosquitto.conf man page
e.g.
connection foo
Will result in a connection name of foo.
172.22.25.53 is in the reserved range 172.16.0.0 – 172.31.255.255, I'm going to guess you are running emq in a docker container and you are trying to access the container using it's Docker internal IP address. You will need to expose the port on your host machine to be able to access it from a remote machine.
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
The connection name is the value after connection in the configuration file. As described in the bridge section of the mosquitto.conf man page
e.g.
connection foo
Will result in a connection name of foo.
172.22.25.53 is in the reserved range 172.16.0.0 – 172.31.255.255, I'm going to guess you are running emq in a docker container and you are trying to access the container using it's Docker internal IP address. You will need to expose the port on your host machine to be able to access it from a remote machine.
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
answered Nov 14 '18 at 11:41
hardillbhardillb
24.4k73160
24.4k73160
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
add a comment |
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
Nope. I haven't used docker. 172 is an internal set of IP Address. These systems are corporate connection. So these ports are already exposed via LAN. Not sure how else to expose the ports. My bridge connection gets connected very rarely. Its not stable.
– Abishek Ranka
Nov 14 '18 at 12:51
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
And also, So since the connection name is foo, i dont need to mention it anywhere else on my broker on the other end right?
– Abishek Ranka
Nov 15 '18 at 4:35
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295459%2fmosquitto-emqx-bridge-connection-name%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
