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

2 HA-Bridge instances: UpnpListener encountered an error sending upnp notify packet. IP: 239.255.255.250 with message: Operation not permitted #737

Closed
heikoh81 opened this issue Sep 5, 2017 · 5 comments
Assignees
Milestone

Comments

@heikoh81
Copy link

heikoh81 commented Sep 5, 2017

Hi,

as stated in issue #736, I need to run 2 HA-Bridge instances on the same Raspi2.
However, upon doing so, I now get my log flooded with this message that I didn't have before:

UpnpListener encountered an error sending upnp notify packet. IP: 239.255.255.250 with message: Operation not permitted

I use 2 different home-dirs, thus running 2 different config files, 1 for each instance.
My further settings are:

  • Raspi2, Raspian Jessie, HA-Bridge 4.5.6
  • Use UPNP Address Interface Only = FALSE
  • UPNP Strict Handling = FALSE
  • Port for Webinterface, instance 1: 81
  • UPNP-Port, instance 1: 50001
  • Port for Webinterface, instance 2: 82
  • UPNP-Port, instance 2: 50002
  • local IP adress of my Raspi: 192.168.178.220

Thanks for your help.
Heiko

@bwssytems
Copy link
Owner

Will take a look as that should not happen.

@bwssytems bwssytems self-assigned this Sep 6, 2017
@heikoh81
Copy link
Author

heikoh81 commented Sep 6, 2017

Thanks! I really hope you can fix this!

I tried some other things today - not successful though.

  • I bound a 2nd IP-Address to my Raspi, assigning the new IP to the 2nd instance (in the HA-Bride Webinterface config). Error still occurs.
  • I added 2 iptables rules. Error still occurs
    iptables -I INPUT -p ALL -s 239.255.255.250/24 -j ACCEPT iptables -I OUTPUT -p ALL -d 239.255.255.250/24 -j ACCEPT

As soon as I stop one of the two instances, the error message stops!

@bwssytems
Copy link
Owner

I think I may need to have a bind on the upnp interface if it is specified.

@heikoh81
Copy link
Author

Despite the error messages in the log, I now have 3 instances running (24/32/31 devices).
If I put all of these devides into 1 habridge, Alexa completely messes up recognizing any voice commands.
Just right now I tried adding a 4th instance, however, now Alexa also messes completely up.
A random small number of devices of any of the 4 virtual bridges is now not found by device discovery.
Any idea why that is happening?

@bwssytems
Copy link
Owner

I have updated the upnp socket implementation to be on only one socket for the multicast responses.

@bwssytems bwssytems added this to the V5.0.0 milestone Oct 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants