BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

[Alexander Motin]

Lev Serebryakov wrote:
>   BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of
> errors on every start and doesn't answer on requests for 30-60 seconds
> after that. Errors are like this:
> 
> Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: unexpected error:
> Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device not configured
> Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:111: unexpected error:
> Jan 24 12:18:12 gateway named[1455]: unable to convert errno to isc_result: 6: Device not configured
> Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1567: unexpected error:
> Jan 24 12:18:12 gateway named[1455]: internal_send: 193.0.14.129#53: Device not configured
> 
>  Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect to two
> providers.

ENXIO reported by many netgraph nodes if they receiving data while not 
configured. I have found small time window in mpd5 operation when 
interface is UP and configured, but IP flow is not enabled yet. I have 
made small change in mpd5 CVS which should close that window. I hope it 
will help you.

-- 
Alexander Motin