Good call Gregg, an Apache v1.1 library for Upnp already exists, this
will be a good start: http://www.sbbi.net/site/upnp/index.html
How's this for a Preferred order for publicly visible services:
1. Public Address
2. Upnp NAT - All the home routers
3. STUN TCP - The majority of Enterprise NAT / Firewalls
4. TURN TCP - Whatever is left over.
Where / how should this integrate with secure JERI and the utility
services (DnsSdRegistrar, JeriUpnp, JeriRendezvous, JeriRelay),
Abstracted from any Service utilising it?
Should it be an SPI?
Cheers,
Peter.
Peter Firmstone wrote:
It's a good idea to support UPNP IGD Standardized Device Control
Protocol V, since it would allow the service to be supported directly,
it would be the preferred option when it existed, but we still need
some fall back for enterprise environments where its usually disabled.
I'll look into it further.
Peter.
Maybe we need an endpoint implementation which knows how to use uPnP
for port forwarding configuration on consumer routers? More and more
software is using uPnP for port forwarding.
Microsofts Home Server knows how to do this, and there are others
that I've seen doing this to provide appropriate port forwarding
changes.
Gregg Wonderly
