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.

Sign up for GitHub

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

Jump to bottom

After updating to 1.x only listening on IPv6 interface #51

Closed
Tranquility76 opened this issue Sep 6, 2019 · 9 comments
Closed

After updating to 1.x only listening on IPv6 interface #51

Tranquility76 opened this issue Sep 6, 2019 · 9 comments
Assignees
@mabunixda
Labels
bug Something isn't working

Comments

@Tranquility76
Copy link

Helllo,

while having the same issues as described in #16 I did some research and figured out, that node-red is only listening on TCP 60000 on the IPv6 interface.

With this "iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 60000" cannot work a it is an IPv4 rule.

On the other side it is listening on UDP 60000 at the IPv4 interface.

I was not able to figure out why the controller node only listens on IPv6 interfaces for TCP 60000.
@Tranquility76 Tranquility76 added the bug Something isn't working label Sep 6, 2019
@mabunixda
Copy link
Owner

@Tranquility76 but node-red is listening on all ipv4 only?
Normally the output is just for ipv6 listed even when ipv4 is also listening.

Did you try a curl http://127.0.0.1:6000/ ?

@Tranquility76
Copy link
Author

Tranquility76 commented Sep 6, 2019 via email

@mabunixda
Copy link
Owner

On the latest version of the node you can also change the port of the hub to 80 and remove the iptables statement - so you could remove 1 component of complexity ...

Can you post the http requests to the alexa-controller of the logfile of node-red?
Or you can change the logging details to debug to get more information.

At the moment i get no problems on my setup with gen2 and gen3 devices

@Tranquility76
Copy link
Author

Tranquility76 commented Sep 6, 2019 via email

@mabunixda
Copy link
Owner

Can you post the output of "/api/c6260f982b43a226b5542b967f612ce/lights" ?

@Tranquility76
Copy link
Author

Tranquility76 commented Sep 6, 2019 via email

@mabunixda
Copy link
Owner

interessting - i expected more umlaute ;-) So the node "Gästebad" is detected correct?
When i review the 2 log outputs both types you are using are detected within those 3 items?
Or did i miss something and just 1 type of items is available in alexa?

Which node/node-red/alexa version/generation are you using?

@Tranquility76
Copy link
Author

Tranquility76 commented Sep 6, 2019 via email •
edited
Loading

mabunixda added a commit that referenced this issue Oct 1, 2019
@mabunixda
fixing #51 + #57 bind to ip, #53 to discover all nodes
5aaa8aa 
Signed-off-by: Martin Buchleitner <[email protected]>
@mabunixda mabunixda mentioned this issue Oct 1, 2019
Merged
mabunixda added a commit that referenced this issue Oct 1, 2019
@mabunixda
Bugs/detection (#61)
709a6c0 
* fixing #51 + #57 bind to ip, #53 to discover all nodes
* Fix npm-check errors
* remove node 6/7 from support
* pump version to 1.2.0
@mabunixda
Copy link
Owner

You might try to bind the hub to a dedicated IP with an env variable ALEXA_IP ... otherwise i think this i more a detection/communication problem as in #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mabunixda mabunixda

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mabunixda @Tranquility76