Failed to send 300 byte long packet over fallback interface.

[kevinmsmith22]

Listers,
    I recently started getting this error in my log. It doesnt seem to be
be causing and major malfunctions yet, but I dont like random errors.
This only seems to pop up with after a static address is assigned, not
sure if thats related.

FYI I have googled the heck out of this, with only issues found no 
solutions, that Russian site looked promising, but I dont understand 
cyrillic.
---
Heres an exerpt of the /var/log/dhcpd.log:
Jul  4 15:50:26 server dhcpd: DHCPINFORM from 10.0.0.8 via eth1
Jul  4 15:50:26 server dhcpd: DHCPINFORM from 10.0.0.8 via eth1
Jul  4 15:50:26 server dhcpd: DHCPACK to 10.0.0.8 (deleted) via eth1
Jul  4 15:50:26 server dhcpd: DHCPACK to 10.0.0.8 (deleted) via eth1
Jul  4 15:50:26 server dhcpd: send_packet: Operation not permitted
Jul  4 15:50:26 server dhcpd: dhcp.c:1324: Failed to send 300 byte long
packet over fallback interface.Jul  4 16:18:54 server dhcpd: DHCPREQUEST
for 10.0.0.21 from e4:25:e7:08:2a:2a via eth1
Jul  4 16:18:54 server dhcpd: DHCPACK on 10.0.0.21 to  via eth1
Jul  4 16:18:54 server dhcpd: DHCPACK on 10.0.0.21 to  via eth1
Jul  4 16:18:54 server dhcpd: Added new forward map from
client1.local.lan to 10.0.0.21
Jul  4 16:18:54 server dhcpd: Added new forward map from
client1.local.lan to 10.0.0.21
Jul  4 16:18:54 server dhcpd: Added reverse map from
21.0.0.10.in-addr.arpa. to client1.local.lan
Jul  4 16:18:54 server dhcpd: Added reverse map from
21.0.0.10.in-addr.arpa. to client1.local.lan
--

--
Also note its seems to be giving out 2 IP'S to the same client...Can I
assume the error is caused by one of the packets being rejected?
and the DNS does double the mappings too. (but, I think if the first 
issue is corrected, this one with as well)
--

DHCPD.CONF

one-lease-per-client true;
ignore bootp;
allow booting;
option ip-forwarding true;
option mask-supplier true;

ddns-updates on;
ddns-update-style interim;
ignore client-updates;
ddns-domainname "local.lan";
ddns-rev-domainname "in-addr.arpa.";
option domain-name "local.lan";
option domain-name-servers 10.0.0.1;
option ntp-servers 10.0.0.1;
update-static-leases on;
use-host-decl-names on;

# This is the key so that DHCP can authenticate it's self to BIND9
include "/etc/bind/rndc-key";

# This is the communication zone
zone local.lan {
     primary 10.0.0.1;
     key "rndc-key";
}

zone 0.0.10.in-addr.arpa. {
primary 10.0.0.1;
key "rndc-key";
}


log-facility local7;
interfaces="eth1";
option netbios-name-servers 10.0.0.1;
option host-name "server";
option subnet-mask 255.255.255.192;
option broadcast-address 10.0.0.63;
option routers 10.0.0.1;


authoritative;
default-lease-time 604800;

subnet 10.0.0.0 netmask 255.255.255.192 {
allow-known-clients;
option routers 10.0.0.1;

class "DirectTV" {
match hardware;
}
subclass "DirectTV" 1:60:02:b4:cd:b7:49;#LR
subclass "DirectTV" 1:70:85:c6:ea:7c:1c;#MBR
subclass "DirectTV" 1:70:85:c6:ea:7c:51;#BR
subclass "DirectTV" 1:70:85:c6:ea:7c:b9;#JR


		pool{
		allow members of "DirectTV";
		range 10.0.0.33 10.0.0.37;	
		allow known-clients;	
		default-lease-time 604800; #one_week
}
		pool{
		range 10.0.0.46 10.0.0.50;
		default-lease-time 600; #10_minutes
		max-lease-time 1200;
		deny known clients;
}
Assigned Addresses follow.
----

Let me know if there any other logs are needed..

TIA

Kev

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus