[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: minimal name resolution configuration?
From:       Kramcsák_Attila <kramcsak.attila () gmail ! com>
Date:       2019-03-02 9:46:28
Message-ID: CAJZR744orEstx=nNB-DpLrgV5ZMzX5z13pg39d4GBaV9AMNezA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi,

This has nothing to do with busybox nor the kernel, but the glibc version
the kernel is built against. According to the manual below the order
keyword in your /etc/host.conf file may be deprecated. Try strace ping
node01 to see which system call drops an error.

http://man7.org/linux/man-pages/man5/host.conf.5.html

Cheers,
Attila


David Mathog <mathog@caltech.edu> ezt írta (időpont: 2019. márc. 2., Szo,
1:41):

> The name resolution configuration which worked under 2.6.* kernels and a
> busybox from 10 years ago no longer functions.  What is the minimum
> needed to get name resolution with a 3.14.* kernel and current busybox?
>
> This is what I have, which doesn't work (3.14.78 kernel, perhaps it
> needs
> some module loaded or built in???)
>
> echo "filling /etc/host.conf"
> cat >>/etc/host.conf <<EOFHOSTCONF
> order hosts,bind
> multi on
> EOFHOSTCONF
> #
> echo "filling /etc/hosts"
> cat >>/etc/hosts <<EOFHOSTS
> 192.168.1.1     node01.cluster  node01
> 192.168.1.2     node02.cluster  node02
> #etc.
> EOFHOSTS
>
> cat >>/etc/nsswitch.conf <<EOFSWITCH
> passwd:     files nis sss
> shadow:     files nis sss
> group:      files nis sss
> hosts:      files dns
> bootparams: nisplus [NOTFOUND=return] files
> ethers:     files
> netmasks:   files
> networks:   files
> protocols:  files
> rpc:        files
> services:   files sss
> netgroup:   files nis sss
> publickey:  nisplus
> automount:  files nis
> aliases:    files nisplus
> EOFSWITCH
>
> which used to be enough for
>
>    ping node01
>
> or
>
>    ping node01.cluster
>
> to work.  But it doesn't anymore.  Instead ping complains that it cannot
> resolve the name.  ping by IP number works.  ping is just a symbolic
> link to busybox.
>
> Thanks,
>
> David Mathog
> mathog@caltech.edu
> Manager, Sequence Analysis Facility, Biology Division, Caltech
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div \
dir="ltr"><div>Hi,</div><div><br></div><div>This has nothing to do with busybox nor \
the kernel, but the glibc version the kernel is built against. According to the \
manual below the order keyword in your /etc/host.conf file may be deprecated. Try \
strace ping node01 to see which system call drops an \
error.<br></div><div><br></div><div><a \
href="http://man7.org/linux/man-pages/man5/host.conf.5.html">http://man7.org/linux/man \
-pages/man5/host.conf.5.html</a></div><div><br></div><div>Cheers,</div><div>Attila<br></div><div><br></div></div></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">David Mathog &lt;<a \
href="mailto:mathog@caltech.edu">mathog@caltech.edu</a>&gt; ezt írta (időpont: \
2019. márc. 2., Szo, 1:41):<br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">The name resolution configuration which worked \
under 2.6.* kernels and a <br> busybox from 10 years ago no longer functions.   What \
is the minimum <br> needed to get name resolution with a 3.14.* kernel and current \
busybox?<br> <br>
This is what I have, which doesn&#39;t work (3.14.78 kernel, perhaps it <br>
needs<br>
some module loaded or built in???)<br>
<br>
echo &quot;filling /etc/host.conf&quot;<br>
cat &gt;&gt;/etc/host.conf &lt;&lt;EOFHOSTCONF<br>
order hosts,bind<br>
multi on<br>
EOFHOSTCONF<br>
#<br>
echo &quot;filling /etc/hosts&quot;<br>
cat &gt;&gt;/etc/hosts &lt;&lt;EOFHOSTS<br>
192.168.1.1        node01.cluster   node01<br>
192.168.1.2        node02.cluster   node02<br>
#etc.<br>
EOFHOSTS<br>
<br>
cat &gt;&gt;/etc/nsswitch.conf &lt;&lt;EOFSWITCH<br>
passwd:        files nis sss<br>
shadow:        files nis sss<br>
group:         files nis sss<br>
hosts:         files dns<br>
bootparams: nisplus [NOTFOUND=return] files<br>
ethers:        files<br>
netmasks:     files<br>
networks:     files<br>
protocols:   files<br>
rpc:            files<br>
services:     files sss<br>
netgroup:     files nis sss<br>
publickey:   nisplus<br>
automount:   files nis<br>
aliases:      files nisplus<br>
EOFSWITCH<br>
<br>
which used to be enough for<br>
<br>
     ping node01<br>
<br>
or<br>
<br>
     ping node01.cluster<br>
<br>
to work.   But it doesn&#39;t anymore.   Instead ping complains that it cannot <br>
resolve the name.   ping by IP number works.   ping is just a symbolic <br>
link to busybox.<br>
<br>
Thanks,<br>
<br>
David Mathog<br>
<a href="mailto:mathog@caltech.edu" target="_blank">mathog@caltech.edu</a><br>
Manager, Sequence Analysis Facility, Biology Division, Caltech<br>
_______________________________________________<br>
busybox mailing list<br>
<a href="mailto:busybox@busybox.net" target="_blank">busybox@busybox.net</a><br>
<a href="http://lists.busybox.net/mailman/listinfo/busybox" rel="noreferrer" \
target="_blank">http://lists.busybox.net/mailman/listinfo/busybox</a><br> \
</blockquote></div>



_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic