Multiple problems in DHCP client
Sebastien Bourdeauducq
sebastien at milkymist.org
Fri May 6 22:22:53 UTC 2011
On Sat, 2011-05-07 at 07:42 +1000, Chris Johns wrote:
> > 3) The variable rtems_bsdnet_nameserver_count is not set to 0 at the
> > beginning of the DHCP request, which means that when DHCP is restarted,
> > the DNS entries keep piling up until the table is full (3 entries), at
> > which point the new DNS will not be taken into account at all.
>
> Another bug. The difficultly is a user who mixes the DHCP supplied
> entries and initialised entries in the rtems_bsdnet_nameserver table. If
> just the file was created would this solve the issue ?
No, since as far as I can tell, the DHCP client simply adds to that file
(with rtems_rootfs_file_append) and does not truncate it. However, it
should make spotting that bug (and potential similar ones) easier - as
the problem could be exposed simply by displaying the contents
of /etc/resolv.conf.
I also think it should be better to remove the table and use
resolv.conf ...
> I thought the stack would keep an eye on resolv.conf. I know on a
> FreeBSD system I can just edit any time and the change take effect.
Hmm, that's something I'd test.
S.
More information about the users
mailing list