Hi Bob,
thanks yes that makes sense.
That means my 50+ networks are NOT shared networks because thy are all
in a different Vlan behind a relay host?
So i could live with simply subnet4 definitions without shared networks?
What worked until now in my test environment is one shared network with
all my 50 reservation subnet in it and one dyn pool.
That one Shared network has the relay option set so that everything need
to come from that relay host.
Similar to that example from Satish without the relay host. @Satish
Thanks for you response
###
...
"shared-networks": [
{
"name": "device-mgmt",
"relay": {
"ip-addresses": [ "10.3.1.3" ]
},
"subnet4": [
{
"id": 2,
...
###
I now understand it that way that this configuration is wrong because
these networks are on separate VLAN and have nothing todo with each other.
There is no network expand an existing one.
Where is my misunderstanding?
---
Giso
Am 10.03.20 um 22:00 schrieb Bob Harold:
On Tue, Mar 10, 2020 at 9:15 AM Giso Kegel <[email protected]
<mailto:[email protected]>> wrote:
Hi Folks,
I work with kea 1.6.1
I really do not understand the concept or at leased the documentation
regarding shared-networks.
Do i need shared-networks or not?
I do not have the problem that I have networks that grew out of there
original definition.
https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html
lets say i have 50+ subnet4 that will ask the kea dhcp server over
dhcp
relayhosts (a swtich).
All these subnet4 will hold only server that have a IP-reservation.
Do i need multi shard networks?
Can or do i have to put these 50+ networks in multi shared networks?
Do i have to use different interfaces for each shared network?
I would be very thankful for some enlightenment.
Best
Giso
"Shared networks" are layer 3 subnets in the same layer 2 broadcast
domain (physical wire or VLAN). If the same router port has multiple
subnets on it, and they are not 'tagged' differently, then they are
"shared networks". Otherwise, they are not shared.
Does that help?
--
Bob Harold
--
Giso Kegel
Systems Engineer
Internal Support & Services (IONOS Cloud)
1&1 IONOS SE | Greifswalder Str. 207 | 10405 Berlin | Germany
Phone:
E-Mail: [email protected] | Web: www.ionos.de
Hauptsitz Montabaur, Amtsgericht Montabaur, HRB 24498
Vorstand: Dr. Christian Böing, Hüseyin Dogan, Dr. Martin Endreß, Hans-Henning
Kettler, Matthias Steinberg, Achim Weiß
Aufsichtsratsvorsitzender: Markus Kadelke
Member of United Internet
Diese E-Mail kann vertrauliche und/oder gesetzlich geschützte Informationen
enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind oder diese E-Mail
irrtümlich erhalten haben, unterrichten Sie bitte den Absender und vernichten
Sie diese E-Mail. Anderen als dem bestimmungsgemäßen Adressaten ist untersagt,
diese E-Mail zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise
auch immer zu verwenden.
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient of this e-mail, you are hereby notified that saving,
distribution or use of the content of this e-mail in any way is prohibited. If
you have received this e-mail in error, please notify the sender and delete the
e-mail.
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
