Darren Reed wrote:
Has the NWAM team looked at UPnP?
http://www.upnp.org/
And specific to this would be CR#6224486
Or to have a better idea of what the "competition" does,
plug in a Windows XP box to a LAN, snoop the traffic and
toggle the "automatic discovery" for the proxy setting.
You should see it broadcast looking for an http proxy.
Finding the data isn't necessarily the problem for Solaris it is getting
the applications to use it once the NWAM daemon has discovered it.
Though as you point out maybe it isn't just NWAM that should be
attempting to discover this but the applications should be.
So how does this relate to what we should do with Solaris?
*IF* you wanted to steer away from making something
Solaris specific, I'd argue that one approach would be
to adapt programs such as web browsers to send out a
request for the http proxy on the loopback interface and
for Solaris to provide a daemon that listens for and answers
those queries with information provided to it via some
"other means".
Or have a proxy proxy running on a local port ;-)
In addition, we could think about adding vendor specific
type codes to DHCP for proxies (I'm surprised that there
is nothing in DHCP for this - that I can find- yet) that
are retrieved at bootup and fed into the GNOME thing or
your login shell as $http_proxy, etc.
From /etc/dhcp/inittab
SHTTPproxy VENDOR, 17, ASCII, 1, 0, smi
Already there ;-)
--
Darren J Moffat
_______________________________________________
networking-discuss mailing list
[email protected]
