Tomek, this is just part of log....in the same log, Kea tries to find the same
MAC on correct subnet id....but I guess I found the 'problem'.
Actually, I need some explanations from experts....
DHCP works on Layer 2? And VLAN's, works on layer 2 too?
This is what I have:
One VM with only one interface.....this interface has VLAN 227 as untagged and
a lot of other VLAN"s tagged, including VLAN 209
On OS of this VM (CentOS 7), I have two interfaces:
eth0 => 'normal interface', configured with static IP and nothing related to
VLAN. Untagged VLAN = 227, but receives a lot of other tagged VLAN's.
network-id = 1025 for this IP range/VLAN
eth0.209 => interface configured with VLAN ID 209. Network-id = 1024 for this
range/VLAN.
In Kea configuration, I had:
"interfaces-config": {
"interfaces": [ "eth0", "eth0.209" ]
},
and nothing more.
The 'problem' is that Kea is seeing more traffic on eth0....I mean, Kea is
receiving DHCP requests from ALL other VLAN's that is tagged, even if my linux
is not configured for these VLAN's. So I'm guessing that Kea is intercepting
DHCP packages before my linux could 'ignore' these tagged packets on eth0 (I
could see this on log with debug). Since my VLAN 209 came untagged to interface
eth0.209 and tagged to interface eth0, I think Kea is guetting crazy with same
packet on both network cards and subnets.
I have added 'interface' to specific subnetworks and It's working for now.
"subnet4": [
{
"subnet": "143.107.205.0/24",
"id": 1024,
"option-data": [ {
"name": "routers",
"code": 3,
"space": "dhcp4",
"csv-format": true,
"data": "143.107.205.1"
}
],
"interface": "eth0.209"
},
{
"subnet": "143.107.158.0/24",
"id": 1025,
"option-data": [ {
"name": "routers",
"code": 3,
"space": "dhcp4",
"csv-format": true,
"data": "143.107.158.1"
}
],
"interface": "eth0"
},
Jonis Maurin Ceará
Analista de Sistemas
FEA-RP
Help Desk +55 (16) 3315-3898
Audiovisual +55 (16) 3315-3927
Desenv. Sistemas +55 (16) 3315-4485
Infraestrutura +55 (16) 3315-8539 / 0672
Atendimento Web: http://suporte.fearp.usp.br
----- Mensagem original -----
> De: "Tomek Mrugalski" <[email protected]>
> Para: [email protected]
> Enviadas: Quinta-feira, 19 de Maio de 2016 14:11:53
> Assunto: Re: [Kea-users] Can't get KEA to work here
> I think I found the issue.
> On 16.05.2016 15:15, Jonis Maurin Ceara wrote:
> > Another example of log and a registry on database:
> >
> > 2016-05-16 10:02:01.754 DEBUG [kea-dhcp4.packets/30560]
> > DHCP4_SUBNET_SELECTED [hwtype=1 6c:62:6d:bd:1a:18],
> > cid=[01:6c:62:6d:bd:1a:18], tid=0x1fcfffa7: the subnet with ID 1025
> > was selected for client assignments
> > 2016-05-16 10:02:01.754 DEBUG [kea-dhcp4.packets/30560]
> > DHCP4_SUBNET_DATA [hwtype=1 6c:62:6d:bd:1a:18],
> > cid=[01:6c:62:6d:bd:1a:18], tid=0x1fcfffa7: the selected subnet
> > details: 143.107.158.0/24
> > 2016-05-16 10:02:01.754 DEBUG [kea-dhcp4.hosts/30560]
> > HOSTS_CFG_GET_ONE_SUBNET_ID_HWADDR_DUID get one host with IPv4
> > reservation for subnet id 1025, HWADDR hwtype=1 6c:62:6d:bd:1a:18,
> > DUID 01:6c:62:6d:bd:1a:18
> This query is for subnet-id 1025.
> > Registry:
> >
> >
> This image above shows entry for with subnet-id 1024.
> I don't know your deployment scenario, so can't make any specific
> recommendations. Just make sure that your host reservation data
> matches
> the subnet id in your config file.
> Let me know if that was it.
> Tomek
> _______________________________________________
> Kea-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-users
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
