Kacheong Poon writes:
> James Carlson wrote:
> 
> > If Firefox (et al) want to retrieve the DHCP options on Solaris,
> > shouldn't they be using dhcpinfo?  If they're really sending
> > DHCPINFORM, then the whole thing sounds extremely kludgy to me.
> 
> 
> I just did an experiment using firefox's auto-detect method in
> Solaris.  It seems that it does not contact dhcpagent, nor send
> out any DHCP message.

Good to hear, actually.  ;-}

>  It just uses the DNS method for WPAD.
> If people know more about this, please comment.

That's much simpler.  I still maintain that we ought not be involved
here, except (if we so choose) to make deployment of WPAD itself
simpler.

In other words, provide tools that help the administrator to set up
the Apache or <insert-what-they-call-it-today> web server to provide
the necessary PAC file, and to configure named properly.  Trying to do
an end-run around the WPAD design (regardless of what one might think
of the 'design') seems like a long-term mistake to me.

I think you're trying to work around a missing bit of infrastructure.
Though it might help some folks in the short term, I don't see why
that's really the right strategy in the long term, and it seems to me
that it has some unfortunate failure modes.  (Such as potentially
_breaking_ WPAD operation if NWAM's mediation mechanism gets it
wrong.)

> > I still think that if we're to support WPAD at all, we should just
> > make it easy to use.  Faking it up to interpose on Firefox's behavior
> > seems very likely to end in tears.
> 
> 
> If people have a suggestion on how to make WPAD work with NWAM,
> please point it out.  It helps us a lot.  I think it is important
> for us to make this work.

My proposal: configure named, configure Apache, go have coffee.  ;-}

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to