Am 23.01.23 um 09:43 schrieb Stefan G. Weichinger:
I currently wait for the admin there to call me back, then we will try
to test drive the relay setup. Currently ~85 leases in 4 subnets active,
we'll see.
Unsure how the active leases will be handled, looking forward to see the
behavior. Eit
Am 23.01.23 um 07:52 schrieb Klaus Steden:
This is what we added to our Kea configs to deal with the encapsulated
requests:
...
"option-def": [
{
"name": "link",
"code": 150,
"space": "relay-cisco",
"type": "ipv4-address",
"record-
This is what we added to our Kea configs to deal with the encapsulated
requests:
...
"option-def": [
{
"name": "link",
"code": 150,
"space": "relay-cisco",
"type": "ipv4-address",
"record-types": "",
"array": false,
"encapsulat
Stefan G. Weichinger wrote:
>> I will start by stopping one of my 2 kea-nodes, and then remove the VLAN
>> interfaces on the remaining one. Plus enable the DHCP-relay, plus adding
>> that fw-rule.
>> In kea I have to remove the various vlan-interfaces and edit the subnets to
>> all listen on t
Hi,
I'm just using dnsmasq to create a dhcp relay on my router, and my machine
running Kea just have one interface but many IP ranges to cover all subnets in
Kea.
dnsmasq is easy to configure, this is a complete setup:
dhcp-relay=gateway_ip,dhcp_server_ip
# Disable the DNS server in dnsmasq
port
Am 21.01.23 um 08:03 schrieb Stefan G. Weichinger:
I will start by stopping one of my 2 kea-nodes, and then remove the VLAN
interfaces on the remaining one. Plus enable the DHCP-relay, plus adding
that fw-rule.
In kea I have to remove the various vlan-interfaces and edit the subnets
to all l
Am 20.01.23 um 15:44 schrieb Simon:
Stefan G. Weichinger wrote:
It seems I have to rebuild my DHCP setup.
I suggest “rebuild” is a strong word - modify would be more appropriate.
You are right, yes ;-)
Ignore circuit-id and agent-id, they are a fairly advanced configuration
relating to
Stefan G. Weichinger wrote:
> It seems I have to rebuild my DHCP setup.
I suggest “rebuild” is a strong word - modify would be more appropriate.
> So it seems I have to remove the VLAN interfaces and somehow use a DHCP relay
> (on the existing pfsense) for each of the VLANs.
>
> What I don't
On Fri, Jan 20, 2023, at 03:17, Stefan G. Weichinger wrote:
> What I don't yet understand: how to assign requests coming from VLAN X
> to the matching subnet X on Kea?
>
> I read something around "circuit ID" and "agent ID" here:
>
> https://docs.netgate.com/pfsense/en/latest/services/dhcp/relay.h
It seems I have to rebuild my DHCP setup.
Currently I have vlan interfaces on the kea-servers to provide DHCP to
each defined VLAN.
This leads to problems: the VLAN interfaces also set routes to the
various VLANs, this breaks routing for the Samba DCs also running on the
same hardware.
(
10 matches
Mail list logo
