From 47c8eaab588bc356cdf60f3fa02dbe0ee73653c7 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Wed, 13 Jan 2016 11:08:05 -0600 Subject: [PATCH] Update TODO list --- TODO | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/TODO b/TODO index c011a56051..773a90684e 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -NuttX TODO List (Last updated January 11, 2016) +NuttX TODO List (Last updated January 13, 2016) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This file summarizes known NuttX bugs, limitations, inconsistencies with @@ -1009,17 +1009,31 @@ o Network (net/, drivers/net) someone will encounter this in the future. Title: GLOBAL DNS ADDRESS - Description: Currently there is a single, global DNS server address. I am - thinking that there should be one DNS server address per - network device. This would mean: - - Moving the global DNS server address into the network - device structure - - Add netwok IOCTLs to set and get the DNS address - - Use these address in libc/netdb and apps/netutils/netlib. - - The netdb/netlib interface would need to have the device - name as a parameter and would need to call the IOCTL to - get/set the DNS server address associated with the device. - Needs a more investigation. + Description: Currently there is a single, global DNS server address. This + address resides in user space (owned by libc/netdb) but is + accessed by network code in kernel space (net/procfs). This + work in a FLAT build, not not in other build modules. + + Things would be really weird in the kernel build: There + would be a separate name server address and a separate netdb + DNS client in each process. That can't be right. + + The Linux kernel has no knowledge at all about DNS addresses. + DNS addresses are retained in /etc/resolv.conf in records + ike: + + nameserver + + The nameserver is associated with the device only through + the routing of the IP address. And this is how there can + be multiple, global DNS addresses. + + Conclusion: The logic in net/procfs needs to be re-designed + so that it does not use the DNS address. The DNS address(es) + should to applied to the device status by logic in the + implementation of the NSH ifconfig command. This would be, + unfortunately, a significant re-design since the formatting + is currently performed in net/procfs. Status: Open Priority: Low. I doubt that there are any multiple NIC, multiple DNS server configurations