Tuesday, November 17, 2020

Re: Wrong net in vlan

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEl5evOTfnjZdhkBzKaPxTRM3nQSAFAl+0JDQACgkQaPxTRM3n
QSBwbg//XbEKSiEb9Ftc75/1WGa0yzjmZ3KImL+yfjkcT+0v8EmuVvMR7ke/rLED
xbXcWmSwB4+A9RYWC2WbGOxkNqB3DKhOthLqzC6Qid3PJ/Ik28vj1WkrQbIPwC80
4lxlSKM9NPz+V9NeNZh/YD7xlgM+m1CjUpsKQYPRttZLyqXJCRjX8e7PIL9+JoDa
jKmNJZXEXFeQpLHGhrMqCWwBjZpG0J/x2+jOE4GaDnjzG7q4GkgMjRQ4SIqo0Bb2
3QRWPsqcD3aZAqt6fhkkYZDOFLEDewtMNI6Zi0PS1SVW72IeWG2hBY9QVbPJlY+L
oTRjLtnIDIjpbq5ccrt4Sh5IAgljnAZFuaIk69m0pD5WSW1oZEmwt+EdrTRnq1LS
KClNmgBfrYLgvtz+ef4Nc6HMuQxCkC0+cqEBBWFv+tBWsRivzxxQxSk0/qMEzBxJ
ovKsMWww26ss+DYGQLhaob0C4urbw6uYBQJm/IxWP/t+cJ76ebDRhIP9wFeq33hw
g0REKK+eY/GuKzoTvsDygmVl7chLAeAdgGVWL1nMHZdPz3UVWAVClUR+0+1ILuTN
+MyoiOm7EFlrz+4rCFcdZCwJiB2V9OxMNuQiOX5eXKlliFtGBJg7avDE/DYcmGxX
10pfWOhORTQcHkYUpXGWU/Xu0TZa/SbCT1oujdzxql97Abe4xn0=
=oVBJ
-----END PGP SIGNATURE-----
Hi all.

> Am 16.11.2020 um 11:09 schrieb Axel Rau <Axel.Rau@chaos1.de>:
>
> - - -
> From /etc/rc.conf.local:
> - - -
> dhcpd_flags="em0 em3 vlan11 vlan12 vlan13 vlan14 vlan15 vlan16"
> - - -

I have still no resolution. dhcpd preovides always an address from the subnet 172.16.11/24 regardless from which vlan comes the request.
172.16.11/24 is the subnet associated with the 1st vlan on em3 (vlan11)
- - -
gw1# ifconfig vlan11
vlan11: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:60:e0:5a:75:43
index 13 priority 0 llprio 3
encap: vnetid 11 parent em3 txprio packet rxprio outer
groups: vlan
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 172.16.11.1 netmask 0xffffff00 broadcast 172.16.11.255
inet6 fe80::260:e0ff:fe5a:7543%vlan11 prefixlen 64 scopeid 0xd
inet6 2a05:bec0:26:16:11::a prefixlen 80
gw1# ifconfig vlan13
vlan13: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:60:e0:5a:75:43
index 15 priority 0 llprio 3
encap: vnetid 13 parent em3 txprio packet rxprio outer
groups: vlan
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 172.16.13.1 netmask 0xffffff00 broadcast 172.16.13.255
inet6 fe80::260:e0ff:fe5a:7543%vlan13 prefixlen 64 scopeid 0xf
inet6 2a05:bec0:26:16:13::a prefixlen 80
- - -
- - -
DHCPREQUEST for 172.16.11.106 from d6:b5:e4:2a:3a:1c via vlan13
Nov 17 19:00:47 gw1 dhcpd[12274]: DHCPACK on 172.16.11.106 to d6:b5:e4:2a:3a:1c via vlan13
- - -
The client receives a IPv6 address from the correct subnet via rad.

In DHCPD.CONF(5), I read:
- - -
hardware-type must be the name of a hardware interface type. Currently, the ethernet, token-ring and fddi physical interface types are recognized, although support for DHCP-over-IPsec virtual interface type ipsec-tunnel is provided. The hardware-address should be a set of colon-separated hexadecimal octets (0-ff) or a hostname that can be looked up in ethers(5) <https://man.openbsd.org/ethers.5> when the configuration is read.
- - -

Are vlans aresupported by dhcpd at all?

Axel
---
PGP-Key: CDE74120 ☀ computing @ chaos claudius

No comments:

Post a Comment