Bug #2277
closed
miniupnp will does not listen on vip's
0%
Description
Currently miniupnp does not listen on vip's just the of the interface. Unfortunately that means if the default GW is on a vip many clients won't be able to use UPNP. I have tested this with my PS3 and XBox, unless I manually add the ip to the config file it doesn't work.
Updated by Chris Buechler over 12 years ago
- Category set to UPnP/NAT-PMP
- Priority changed from Normal to Low
- Affected Version set to All
Updated by Dave Sanderson over 12 years ago
After some more research I'm not sure this can solved as it doesn't appear that CARP interfaces are multicast capable
miniupnpd30572: setsockopt(udp, IP_ADD_MEMBERSHIP): Can't assign requested address
miniupnpd30572: Failed to add multicast membership for address 192.168.1.254
miniupnpd30572: setsockopt(udp_notify, IP_MULTICAST_IF): Operation not supported
miniupnpd30572: Failed to open sockets for sending SSDP notify messages. EXITING
Updated by Chris Buechler over 12 years ago
- Status changed from New to Feedback
looks like that's changed more recently in CARP in OpenBSD judging by the ifconfig output shown here.
http://www.openbsd.org/faq/pf/carp.html
which means it should work when we have a FreeBSD 9.x based release (2.2).
is this actually an issue, or is it just that CARP can't do multicast?
Updated by Dave Sanderson over 12 years ago
At the end of the day the issue is with CARP not doing multicast, since even if there was an option to allow binding miniupnp to vips it wouldn't work. Guess for now the PS3 and XBox don't get the benefit of firewall failover, at least till release 2.2 hopefully. Thanks for looking into it. Cheers.
Updated by Jim Pingle over 12 years ago
- Status changed from Feedback to Resolved