[pupnp-tracker] [ pupnp-Feature Requests-3508818 ] Allow multiple interfaces/ip addresses with UpnpInit

[Tracker i. u. n. <pup...@li...>]

Feature Requests item #3508818, was opened at 2012-03-19 09:34
Message generated for change (Tracker Item Submitted) made by mcnetic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=841029&aid=3508818&group_id=166957

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: upnp
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nicolai Ehemann (mcnetic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Allow multiple interfaces/ip addresses with UpnpInit

Initial Comment:
Currently, UpnpInit only allows for one IP address to be used when initializing. As the documentation already mentions, this is problematic in multi-homed scenarios. Here, one can specify the IP address.
But common multi-homes scenarios are mobile devices connected to the second network (for example a corporate network) via vpn. Specifying the ip in this scenario is not only uncomfortable, for end users, it may well be impossible, as the ip addresses constantly change when moving the portable device to other locations (lans/wlans).
Therefore, I suggest changing UpnpInit to allow for connecting to multiple (and consequently all) available interfaces. Applications could then choose to only connect to interfaces of special types (which should probably not be the scope of libupnp).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=841029&aid=3508818&group_id=166957