Tag: Networking, Networking / Home

Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
Home » Networking

  • Relay agent + option 82

    6 answers - 1217 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    From dhcp-server -- To unsubscribe, see the end of this message.
    Hello,
    I have a problem setting up ISC dhcpd in conjuction with dhcp relay
    agent. The main problem is that the relay inserts option 82 only in
    broadcast packets, so any packets destined directly to DHCP server's
    IP-address have N option 82 information. Yes, everything is fine with
    dynamic leases, because server adds circuit-id and remote-id to
    dhcpd.leases file and use this data when there is no such options in
    packet. But I'd like to implement this scheme with static host
    declarations. That's a problem. dhcpd doesn't save option 82
    information in dhcpd.leases for static leases and I have no correct
    way to classify users to the specific class when they communicating
    directly with DHCP server. :(
    Any thoughts?
    P.S.: Ah, source IP address of relayed packets is constant (IP address
    of relay agent) so I have no ability to classify users behind this
    switch just using subnet { } decl.
    Thanks,
    List Archives : http://www.isc.org/ops/lists/
    Unsubscribe :
    -or- : mailto:dhcp-server-request (AT) isc (DOT) org?Subject=unsubscribe

  • No.1 | | 2439 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    A. Arkhangelsky schrieb:

    From dhcp-server -- To unsubscribe, see the end of this message.
    >
    >Hello,
    >
    >I have a problem setting up ISC dhcpd in conjuction with dhcp relay
    >agent. The main problem is that the relay inserts option 82 only in
    >broadcast packets, so any packets destined directly to DHCP server's
    >IP-address have N option 82 information. Yes, everything is fine with
    >dynamic leases, because server adds circuit-id and remote-id to
    >dhcpd.leases file and use this data when there is no such options in
    >packet. But I'd like to implement this scheme with static host
    >declarations. That's a problem. dhcpd doesn't save option 82
    >information in dhcpd.leases for static leases and I have no correct
    >way to classify users to the specific class when they communicating
    >directly with DHCP server. :(
    >
    >Any thoughts?
    >
    >P.S.: Ah, source IP address of relayed packets is constant (IP address
    >of relay agent) so I have no ability to classify users behind this
    >switch just using subnet { } decl.
    >
    >Thanks,
    >
    >
    >
    >
    >List Archives : http://www.isc.org/ops/lists/
    >Unsubscribe :
    >-or- : mailto:dhcp-server-request (AT) isc (DOT) org?Subject=unsubscribe
    >
    >
    >

    I think your are looking for this one here:

    The stash-agent-options statement

    stash-agent-options flag;

    If the stash-agent-options parameter is true for a given client, the
    server will record the relay agent information options sentduring
    the client'sinitial DHCPREQUEST message when the client was in the
    SELECTING state and behave as if those options are included in all
    subsequent DHCPREQUEST messages sent in the RENEWING state. This
    works around a problem with relay agent information options, which is
    that they usually not appear in DHCPREQUEST messages sent by the
    client in the RENEWING state, because suchmessages are unicast
    directly to the server and not sent through a relay agent.

    Regards,

    Andre

    List Archives : http://www.isc.org/ops/lists/
    Unsubscribe :
    -or- : mailto:dhcp-server-request (AT) isc (DOT) org?Subject=unsubscribe

  • No.2 | | 352 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    Hello Andre,

    Monday, August 15, 2005, 3:47:53 PM, you wrote:

    AMI think your are looking for this one here:
    AMThe stash-agent-options statement

    Unfortunately, no. As I understand, this statement is true by default
    and applicable only for dynamic leases.

  • No.3 | | 664 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    Mon, Aug 15, 2005 at 01:19:46PM +0400, A. Arkhangelsky wrote:
    declarations. That's a problem. dhcpd doesn't save option 82
    information in dhcpd.leases for static leases and I have no correct
    way to classify users to the specific class when they communicating
    directly with DHCP server. :(

    The problem you're describing is that fixed-address host statements are
    not treated like leases. There's no place for ISC DHCP to store a
    binding state, or stash client-supplied options.

    There's naught to be done until a future feature release.

  • No.4 | | 785 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    Hello David,

    Monday, August 15, 2005, 8:34:31 PM, you wrote:

    DWHThe problem you're describing is that fixed-address host statements are
    DWHnot treated like leases. There's no place for ISC DHCP to store a
    DWHbinding state, or stash client-supplied options.

    DWHThere's naught to be done until a future feature release.

    K, but for now I end up with the following:

    option dhcp-server-identifier 10.100.111.83;

    where 10.100.111.83 is IP-address of relay agent. So I forced
    clients ALWAYS use this address for DHCP requests. That's work,
    but I don't know how much this is correct. Are there any possible
    problems with such setup?

  • No.5 | | 1195 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    Even though this doesn't apply to his fixed addresses issues

    I think "stash-agent-options" is enabled by default?
    It sure does appear that way with v3.0.3 David?

    Duane Cox

    Message
    From: "David W. Hankins" <David_Hankins (AT) isc (DOT) org>
    To: <dhcp-server (AT) isc (DOT) org>
    Sent: Monday, August 15, 2005 11:34 AM
    Subject: Re: Relay agent + option 82

    From dhcp-server -- To unsubscribe, see the end of this message.

    Mon, Aug 15, 2005 at 01:19:46PM +0400, A. Arkhangelsky wrote:
    >declarations. That's a problem. dhcpd doesn't save option 82
    >information in dhcpd.leases for static leases and I have no correct
    >way to classify users to the specific class when they communicating
    >directly with DHCP server. :(
    >
    The problem you're describing is that fixed-address host statements are
    not treated like leases. There's no place for ISC DHCP to store a
    binding state, or stash client-supplied options.

    There's naught to be done until a future feature release.

  • No.6 | | 941 bytes | |

    From dhcp-server -- To unsubscribe, see the end of this message.

    Wed, Sep 07, 2005 at 11:06:31PM -0500, Duane Cox wrote:
    Even though this doesn't apply to his fixed addresses issues

    I think "stash-agent-options" is enabled by default?
    It sure does appear that way with v3.0.3 David?

    That's correct, it is enabled by default.

    You realize this doesn't help the fixed-address case

    Common configuration practice as viewed by snippets I see fly across
    this list seems to duplicate the stash-agent-options feature in binding
    scopes. I'm not sure if this is a passive bug report - that there is some
    problem here not reported that people are working around on their ownor
    if these configs merely predate the feature.

    I've said this a few times now, so if someone did actually ahve a problem
    with stash-agent-options, I hope they would have been vocal by now.

Re: Relay agent + option 82


max 4000 letters.
Your nickname that display:
In order to stop the spam: 6 + 5 =
QUESTION ON "Networking"

EMSDN.COM