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

Hello, Freebsd-stable.

  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
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
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
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: 192.112.36.4#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: 192.112.36.4#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
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

  IP addresses are RANDOM and DIFFERENT on every restart. These IP
addresses are not mentioned in ANY config file on my computer, and
addresses on my network interfaces IS NOT from these networks.

  Main problem is, that mount_nfs failed on startup on this router
because bind is not ready due to these errors and all system goes to
single-user mode :(

  Computer is Soekris net5501, with 6 network interfaces (vr0-vr3 on
board, em0 and ath0 attached). Only vr0 and vr1 are used, but adding
fake addresses to vr2 and vr3 doesn't help at all.

 Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect to two
providers.

 But previous installation (on faster hardware) doesn't show these
errors at all!

-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

Hello, Lev.
You wrote 24 ?????? 2009 ?., 13:37:33:
>   IP addresses are RANDOM and DIFFERENT on every restart. These IP
> addresses are not mentioned in ANY config file on my computer, and
> addresses on my network interfaces IS NOT from these networks.
  Ok, I'm stupid, it is root servers. Ok. But this knowledge doesn't
help to fix problem :(
>   Main problem is, that mount_nfs failed on startup on this router
> because bind is not ready due to these errors and all system goes to
> single-user mode :(

-- 
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

On Saturday 24 January 2009 21:07:33 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:11
>1: 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
...
>
>  Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect
> to two providers.
>
>  But previous installation (on faster hardware) doesn't show these
> errors at all!
I think this is an mpd problem - I had the same issue and I couldn't find a 
solution. In the end I switched to userland PPP (which has an issue with PF 
but you can work around that).

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090124/2888b106/attachment.pgp

Lev Serebryakov wrote:
> Hello, Freebsd-stable.
> 
>   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:
It's not necessary or desirable to paste in so many examples of the
same message. It's also not good to cross post the same message to
multiple lists.
> 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
That message is fairly clear, the system has told named that it can
talk to the outside world, but there isn't anything there for named to
talk to. As you already pointed out in another message, the IP
addresses are for the root name servers. The first thing named does
when it starts up is to verify the information in the hints file.
>   Main problem is, that mount_nfs failed on startup on this router
> because bind is not ready due to these errors and all system goes to
> single-user mode :(
Any time you are using NFS you should maintain the addresses of the
critical hosts in /etc/hosts. Yes, I realize that's anachronistic
(especially for a DNS guy) but it works. Obviously you should make
sure to update them as needed.
>   Computer is Soekris net5501, with 6 network interfaces (vr0-vr3 on
> board, em0 and ath0 attached). Only vr0 and vr1 are used, but adding
> fake addresses to vr2 and vr3 doesn't help at all.
> 
>  Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect
to two
> providers.
> 
>  But previous installation (on faster hardware) doesn't show these
> errors at all!
I've never used mpd myself, but you might want to try adding the
following line to /usr/local/etc/rc.d/mpd and see if it helps:

# BEFORE: named


Doug

-- 

    This .signature sanitized for your protection

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