<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1">So as described in one of the first posts, the idea
is to have an information where the DHCP_DISCOVER comes from. So
the option 82 give the informations I need to have a unique
identifier with combination of client-id/circuit-id to assing the
ip address. I know that this usage of the relay client is non
standard. So therefore I don't know if it is possible to use it
like that. It seems not to be ...<br>
<br>
<br>
<br>
</font>Am 13.12.2010 09:55, schrieb Alex Bligh:
<blockquote cite="mid:E32188BE3783A4EC652BDD00@nimrod.local"
type="cite">
<br>
<br>
--On 13 December 2010 08:09:05 +0100 Rico Zoss
<a class="moz-txt-link-rfc2396E" href="mailto:rico.zoss@annax.ch"><rico.zoss@annax.ch></a> wrote:
<br>
<br>
<blockquote type="cite">As I understand your last sentence, your
relay agents are running on a
<br>
router. So therefor the dhcp-server is not in the same subnet.
Or do your
<br>
relay agents on the APs block the broadcast in any case?
<br>
</blockquote>
<br>
Why do you need a relay agent at all if the DHCP server is on the
same
<br>
broadcast domain as the client?
<br>
<br>
It sounds to me that the dhcp relay agent in your switch is there
for
<br>
when it is operating in L3 mode.
<br>
<br>
</blockquote>
</body>
</html>