Kacheong Poon writes:
> Kacheong Poon wrote:
>
> > For 4, NWAM can probably do the following. NWAM can perform
> > WPAD and check if there is proxy info available from any
> > server (we need to figure out what to do if there are multiple
> > servers providing different info). If the info is available,
> > then NWAM may do nothing. A WPAD aware app will find the
> > proper info from the server(s). But if there is no proxy
> > info available from the server(s) and there is a NWAM proxy
> > setting associated with the current network environment, NWAM
> > may "fake" a DHCP server (*) reply using that info to any query
> ^^^^^^^^^^^^^^^^^^^^
>
> I think I've used the wrong words here. The proposal is
> not trying to impersonate a DHCP server. It is really
> "acting" on a request. For WPAD, the above proposes to reply
> to the DHCPINFORM request on option 252 based on the
> NWAM network proxy info. So the proposal is about
I'm still confused about how what you're proposing will work.
For WPAD to work, you need to have at least one of two things:
- a host named "wpad.foo.com" (where "foo.com" is replaced by
something that is in the configured DNS search path) that has a
web server running and has a document named "/wpad.dat" with the
PAC info.
- a DHCP server offering up site-local option 252, with the contents
of the string set to a URL that gives you the PAC information.
I don't see where any special DHCP action on NWAM's part helps here.
In both cases, these are bits of infrastructure that the network must
be configured to have.
If I understand what you're proposing (and I'm not at all sure that I
do), it might be possible to hack dhcpinfo(1) so that it lies to the
user and says that site-local option 252 was received, and that it has
a string provided by NWAM itself. But where is the web server
required for that? Does NWAM fake up a web server in order to hand
off the PAC file? How does NWAM even figure out what to put into the
PAC file?
All of this sounds like a problem that's best solved by vendors of web
proxies, not NWAM.
--
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]
