SV: Option-82 in DHCPACK-packets

[Dahl, Alfred Henning]

On Wed, Apr 18, 2007 at 09:31:58AM +0200, Dahl, Alfred Henning wrote:
>> However, when the client after leasetime/2 tries to renew its lease,
even when option-82-information is included in the request, it is _not_
>inkluded in the reply from the DHCP-server.

>As far as I am aware, this is only if giaddr is not set.

>> Would you seay this is a bug that should be fixed, or is this pattern
a correct behaviour?

>This specific behaviour is not a bug.  RFC3046 defines it as behaviour
you should expect.

>But, the code paths that elect not to include option 82 when giaddr is
not set also will fail to interoperate per RFC3046 when the relay agent
>is a "l2" relay agent...one that never sets giaddr, not even when the
client is broadcasting their packets.

>So that is a bug that is scheduled for our next maintenance release,
and it has the effect that your other behaviour will change.



Thank you, David - this does make sense.

I have walked through the 3.1.0b2-version's RELNOTES, and a lot of
issues related to L2 relay agents and reflection of options are
mentioned. We have upgraded the system to 3.1.0b2, but we still do not
get option-82 (agent.circuit-id) back from server.