Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream

sdetweil

@rkorell not double dash

just trying to figure out what the problem is
maybe curl version

rkorell

@sdetweil OK
this is curl --version :-) (just successfully trial&errored)

curl --version
curl 7.88.1 (aarch64-unknown-linux-gnu) libcurl/7.88.1 OpenSSL/3.0.15 zlib/1.2.13 brotli/1.0.9 zstd/1.5.4 libidn2/2.3.3 libpsl/0.21.2 (+libidn2/2.3.3) libssh2/1.10.0 nghttp2/1.52.0 librtmp/2.3 OpenLDAP/2.5.13
Release-Date: 2023-02-20, security patched: 7.88.1-10+deb12u12
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd

rkorell

@sdetweil because it doesn’t work on windows either this is most likely not a version but a command or URL thing …

rkorell

@sdetweil said in Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream:

just trying to figure out what the problem

Dear Sam,
I caught it …
The Windows command is not working for other reasons - doesn’t matter…
The curl on MY Pi doesn’t work because - for some strange reason the resolving of “localhost” doesn’t work ???

Figured this out by using another linux client (Macbook) and therefor using IP address of pi remotely - which worked instantly.

And trying this locally on Pi with IP adreees does the job as well.

Thanks again for your help!
Regards,
Ralf

sdetweil

@rkorell weird, it works on windows for me

i just copy/pasted from the repo and
changed the address and port at the end

i can do it on the same machine or across the network to other machines

sdetweil

@rkorell localhost is(always) mapped to 127.0.0.1 on the same system

which is called the loopback adapter, cause the packets never leave the system

ping localhost

should work

rkorell

@sdetweil said in Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream:

@rkorell localhost is(always) mapped to 127.0.0.1 on the same system
which is called the loopback adapter, cause the packets never leave the system

Yes. I’m aware of this, thanks.

ping localhost
should work

Yes, do work:

pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-CurlToNotification $ ping localhost
PING localhost(localhost (::1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.035 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.035 ms
64 bytes from localhost (::1): icmp_seq=4 ttl=64 time=0.036 ms
64 bytes from localhost (::1): icmp_seq=5 ttl=64 time=0.031 ms
64 bytes from localhost (::1): icmp_seq=6 ttl=64 time=0.039 ms
^Z
[1]+  Stopped                 ping localhost

thanks anyway,
Regards,
Ralf

sdetweil

@rkorell so, its a curl problem… weird…
but its using ipv6 (::1 is the ipv6 version of 127.0.0.1)

rkorell

@sdetweil said in Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream:

but its using ipv6 (::1 is the ipv6 version of 127.0.0.1)

good catch!
THis may is the reason, because - as far as I. know - ipV6 isn’t implemented (properly?) in my network (at least I do not have anything configured. My AVM (Fritzbox) router is ipV6 aware but I do not “use” it esplicitely …

Strange!

Ralf

sdetweil

@rkorell can you edit your /etc/hosts
to see how localhost is defined

on my amd host it is

127.0.0.1       localhost

on my pi it is

127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback