Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-05 15:58:59 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update TODO list

Browse Source
This commit is contained in:
Gregory Nutt
2016-01-13 11:08:05 -06:00
parent 8ee75a96fe
commit 47c8eaab58
1 changed files with 26 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODO
+26 -12
View File
@@ -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 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. someone will encounter this in the future.
Title: GLOBAL DNS ADDRESS Title: GLOBAL DNS ADDRESS
Description: Currently there is a single, global DNS server address. I am Description: Currently there is a single, global DNS server address. This
thinking that there should be one DNS server address per address resides in user space (owned by libc/netdb) but is
network device. This would mean: accessed by network code in kernel space (net/procfs). This
- Moving the global DNS server address into the network work in a FLAT build, not not in other build modules.
device structure
- Add netwok IOCTLs to set and get the DNS address Things would be really weird in the kernel build: There
- Use these address in libc/netdb and apps/netutils/netlib. would be a separate name server address and a separate netdb
- The netdb/netlib interface would need to have the device DNS client in each process. That can't be right.
name as a parameter and would need to call the IOCTL to
get/set the DNS server address associated with the device. The Linux kernel has no knowledge at all about DNS addresses.
Needs a more investigation. DNS addresses are retained in /etc/resolv.conf in records
ike:
nameserver <name> <server IP addresses>
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 Status: Open
Priority: Low. I doubt that there are any multiple NIC, multiple DNS Priority: Low. I doubt that there are any multiple NIC, multiple DNS
server configurations server configurations