> In order to try and keep the email lists a bit more focused and to make
> it easier to understand which code base somebody is using when they say
> something like “the server does <something>” we have separate mailing
> lists for Kea and ISC DHCP.
>
> Messages about Kea should be sent to either
>
[hidden email]
> or
>
[hidden email]
>
> regards,
> Shawn
>
> On Sep 14, 2015, at 7:27 AM, Raj raj <
[hidden email]> wrote:
>
> Dear List,
>
> I am testing kea (0.9.2) in my environment as my DHCP server. One
> peculiarity is that all clients are in a VLAN and DHCP server must
> listen on a vlan interface for DHCP packets. I have configured the kea
> config file accordingly and the server is receiving DHCPDISCOVER
> packet. But it is not responding to DHCPDISCOVER and bails out with
> the following error message.
>
> 2015-09-14 19:34:25.852 ERROR [kea-dhcp4.bad-packets/29128]
> DHCP4_PACKET_NAK_0001 [hwtype=1 a0:36:9f:41:b6:3a], cid=[no info],
> tid=0xc28b7213: failed to select a subnet for incoming packet, src
> 192.168.200.79, type DHCPDISCOVER
>
> The dhcp4 section of the config file is as follows:
>
> "Dhcp4":
> {
> # Add names of interfaces to listen on.
> "interfaces-config": {
> "interfaces": ["vlan0/192.168.200.1","eth0"]
> },
>
> # Use Memfile lease database backend to store leases in a CSV file.
> "lease-database": {
> "type": "memfile"
> },
>
> # Global (inherited by all subnets) lease lifetime is mandatory parameter.
> "valid-lifetime": 4000,
>
> # Below an example of the simple subnet declaration. Uncomment to
> # enable it. This is a list, denoted with [ ], of structure, denoted
> # with { }. Each structure describes a single subnet and may have
> # several parameters. One of those parameters is "pools" that is
> # also a list of structures.
> "subnet4": [
> { "subnet": "192.0.2.0/24",
> "pools": [ { "pool": "192.0.2.1 - 192.0.2.200" } ] }
> ]
> }
>
> my interface list is as follows:
>
> eth0 Link encap:Ethernet HWaddr f8:a9:63:0c:3c:cb
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:653 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4085 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:187646 (187.6 KB) TX bytes:813585 (813.5 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:3621 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3621 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:310760 (310.7 KB) TX bytes:310760 (310.7 KB)
>
> vlan0 Link encap:Ethernet HWaddr f8:a9:63:0c:3c:cb
> inet addr:192.168.200.1 Bcast:192.168.200.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:653 errors:0 dropped:0 overruns:0 frame:0
> TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:175892 (175.8 KB) TX bytes:54628 (54.6 KB)
>
> wlan0 Link encap:Ethernet HWaddr b8:ee:65:23:4f:4b
> inet addr:192.168.13.157 Bcast:192.168.13.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:30638 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15842 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:23644283 (23.6 MB) TX bytes:1962670 (1.9 MB)
>
> As you can see the vlan0 is configured with 192.168.200.1/24. The dhcp
> requests are being relayed by 192.168.200.79. I am not able to figure
> out what am I doing wrong here.
>
> Help to resolve this will be much appreciated.
>
> Thanks and Regards,
>
> Raj
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users>
>
>
> _______________________________________________
> dhcp-users mailing list
>
[hidden email]
>
https://lists.isc.org/mailman/listinfo/dhcp-users
Locked
