host declaration: Either hardware or dhcp-client-identifier will always match, but never both?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

host declaration: Either hardware or dhcp-client-identifier will always match, but never both?

Harald A. Irmer
Hi,

I'd like to have a host declaration thus:

host nb2-smith {
hardware 00:11:22:33:44:55;
option hostname "nb2-smith";
option dhcp-client-identifier "smith\nb2@vlan111";
...
}

Why this?:

Two concurrent independent uses:

1. User Smith connects with his notebook and gets the static lease
dependent on its hardware address, "00:11:22:33:44:55"; the notebook
will NOT send the client identifier "smith2\nb2@vlan111"; we will assume
that the notebook sends a client identifier which is DIFFERENT TO
"smith2\nb2@vlan111".

2. User Smith's notebook is not connected to its vlan but is going to
set up a vpn connection from outside; the multiple VLAN vpn server with
delegated address management (yes there's one!) then send's a
DHCP-Request with the client identifier "smith2\nb2@vlan111"; for sure
the vpn server's hardware address is DIFFERENT TO 00:11:22:33:44:55.


Will this work, that either hardware or dhcp-client-identifier will
always match, but never both the same time?


Yours,

Harald

--

Karlsruher Institut für Technologie (KIT)
Fakultät für Informatik
ATIS – Abteilung Technische Infrastruktur

Harald A. Irmer
Mitarbeiter Datennetz

Am Fasanengarten 5
Gebäude 50.34, Raum 008
76131 Karlsruhe

Telefon: +49 721 608 – 46963
Fax: +49 721 608 – 46699
E-Mail: [hidden email]
Web: www.atis.informatik.kit.edu/413_420.php
       www.kit.edu

KIT – Universität des Landes Baden-Württemberg und nationales
Forschungszentrum in der Helmholtz-Gemeinschaft

 
Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users
Reply | Threaded
Open this post in threaded view
|

Re: host declaration: Either hardware or dhcp-client-identifier will always match, but never both?

Harald A. Irmer
Forgot to add: for ip economy we'd like to use the same ip - one host
declaration - for both usages, i.e. the line "fixed-address
[hidden email]" should be added.

Am 09.12.2015 um 20:15 schrieb Harald A. Irmer:

> Hi,
>
> I'd like to have a host declaration thus:
>
> host nb2-smith {
> hardware 00:11:22:33:44:55;
> option hostname "nb2-smith";
> option dhcp-client-identifier "smith\nb2@vlan111";
> ...
> }
>
> Why this?:
>
> Two concurrent independent uses:
>
> 1. User Smith connects with his notebook and gets the static lease
> dependent on its hardware address, "00:11:22:33:44:55"; the notebook
> will NOT send the client identifier "smith2\nb2@vlan111"; we will
> assume that the notebook sends a client identifier which is DIFFERENT
> TO "smith2\nb2@vlan111".
>
> 2. User Smith's notebook is not connected to its vlan but is going to
> set up a vpn connection from outside; the multiple VLAN vpn server
> with delegated address management (yes there's one!) then send's a
> DHCP-Request with the client identifier "smith2\nb2@vlan111"; for sure
> the vpn server's hardware address is DIFFERENT TO 00:11:22:33:44:55.
>
>
> Will this work, that either hardware or dhcp-client-identifier will
> always match, but never both the same time?
>
>
> Yours,
>
> Harald
>

--

Karlsruher Institut für Technologie (KIT)
Fakultät für Informatik
ATIS – Abteilung Technische Infrastruktur

Harald A. Irmer
Mitarbeiter Datennetz

Am Fasanengarten 5
Gebäude 50.34, Raum 008
76131 Karlsruhe

Telefon: +49 721 608 – 46963
Fax: +49 721 608 – 46699
E-Mail: [hidden email]
Web: www.atis.informatik.kit.edu/413_420.php
       www.kit.edu

KIT – Universität des Landes Baden-Württemberg und nationales
Forschungszentrum in der Helmholtz-Gemeinschaft

 
Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users