*** From dhcp-server -- To unsubscribe, see the end of this message. ***
from the quill of "Ted Lemon" <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
>
> You aren't talking about the relay agent information option, are you?
Tag 82? Nope. Want to use that one soon enough though. ~evil grin~
> The protocol doesn't say one way or the other.
OK, good. I didn't miss something.
> I interpreted it as
> limiting what would be sent, because a number of popular clients fail
> if you send them options they didn't ask for.
Can you tell me which ones? I suspect I am about to get into a pissing
contest with a relay agent vendor about who is doing what wrong or right,
and some ammo on my side would help. Because of this issue with "some
popular clients", if the relay agent wants to see an option it will need to
prune the response out of the ACK then, or we risk blowing up some clients,
right?
> In the next snapshot, it will be possible to specify a parameter
> request list, but this will override what the client sent rather than
> being appended to it.
Not really optimal either.
> The right thing to do would be something like
> this:
>
> option dhcp-parameter-request-list =
> concat (option dhcp-parameter-request-list, c9:ca:cb);
Yeah, that looks pretty good. But is not what you are talking about for
the next snapshot, right?
b.
--
Brian J. Murrell [EMAIL PROTECTED]
BCTel Advanced Communications 604 454 5279
Vancouver, B.C.
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
