Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: Option 82 problem (Simon Hobson)
2. Re: Option 82 problem (????????? ?????????)
----------------------------------------------------------------------
Message: 1
Date: Fri, 17 Apr 2020 21:08:34 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Option 82 problem
Message-ID: <f3c23202-9714-4a2a-af09-6961f1063...@thehobsons.co.uk>
Content-Type: text/plain; charset=utf-8
????????? ????????? <alexander.sandet...@gmail.com> wrote:
> Actually I do not fully understand how it works. My hardware vendor say me
> that Option 82 MUST be configured on the edge (client access ) switches but
> you says (as I can understand) that it must be configured somewhere on the
> "main" (core) ROUTER, not every switch. Your concept more prefferable for me.
I suspect something has been lost in translation because you DO NOT NEED
OPTION82 AT ALL for DHCP to work. You do not need it on edge switches, you do
not need it on a core switch.
To clarify a bit ...
treat each VLAN as if it was a separate LAN - conceptually think of a VLAN
enabled switch as a stack of "simple" switches. At some point, you need a
router to link those networks together - but instead of needing a router with
lots of ports (one per network), when using VLANs you can combine all the VLANs
down one cable with the ports on each end in trunk mode.
Once you have the basics working (any device can reach any other device,
firewall/access rules permitting, then you can consider DHCP. The only
requirement there is that the DHCP server has a connection to at least one
network (it can directly connect to more than one), and any network not
directly connected to the DHCP server needs a Relay Agent to pick-up broadcasts
from the clients and forward them to the server (and relay replies back again).
Simon
------------------------------
Message: 2
Date: Sat, 18 Apr 2020 09:33:30 +0400
From: ????????? ????????? <alexander.sandet...@gmail.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Option 82 problem
Message-ID:
<CAKzvn5OckZbKGYinvDtxDctoDsRvfyctfHkiOCQZ=xqpcp6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Basic network services topology assumes that DHCP server exist in every
network segment. In every VLAN in my case. It can be separate servers in
network segments or single server with network interfaces gor every
network. Or every VLAN configured on the server. This is a simple and clear
idea. But in some cases it's not good (need to configure lot of vlans for
ex.). But DHCP service offers the relaying technology. With combination of
Option 82 it's common practice to setup single server with single network
interface for DHCP. Option 82 can be used to classify clients by the switch
(agent IP or MAC), by the switch port, by the vlan, etc.
Relaying assumes the dhcp query comes not from original device and original
network segment but from some managed switch where client connected. With
some additional information for identifying client and swithc.
My idea is to not to configure every vlan on the server.
??, 18 ???. 2020 ?., 00:08 Simon Hobson <dh...@thehobsons.co.uk>:
> ????????? ????????? <alexander.sandet...@gmail.com> wrote:
>
> > Actually I do not fully understand how it works. My hardware vendor say
> me that Option 82 MUST be configured on the edge (client access ) switches
> but you says (as I can understand) that it must be configured somewhere on
> the "main" (core) ROUTER, not every switch. Your concept more prefferable
> for me.
>
> I suspect something has been lost in translation because you DO NOT NEED
> OPTION82 AT ALL for DHCP to work. You do not need it on edge switches, you
> do not need it on a core switch.
>
> To clarify a bit ...
> treat each VLAN as if it was a separate LAN - conceptually think of a VLAN
> enabled switch as a stack of "simple" switches. At some point, you need a
> router to link those networks together - but instead of needing a router
> with lots of ports (one per network), when using VLANs you can combine all
> the VLANs down one cable with the ports on each end in trunk mode.
> Once you have the basics working (any device can reach any other device,
> firewall/access rules permitting, then you can consider DHCP. The only
> requirement there is that the DHCP server has a connection to at least one
> network (it can directly connect to more than one), and any network not
> directly connected to the DHCP server needs a Relay Agent to pick-up
> broadcasts from the clients and forward them to the server (and relay
> replies back again).
>
> Simon
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20200418/ca27776b/attachment-0001.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 138, Issue 9
******************************************
