Hi, These comments on Chapter 5 are mostly good ones. Here is my review on them.
** As for URL for IPROUTE2, I can think of : http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 http://en.wikipedia.org/wiki/Iproute2 I think I used non-wikipedia page since I could not foind it back then. Let's use wikipedia site. ** As for your concern on: - IP address "`224.0.0.251`" for IPv4 and "`ff02::fb`" for IPv6 are used. http://tools.ietf.org/html/rfc6762 Any DNS query for a name ending with ".local." MUST be sent to the mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 equivalent FF02::FB). The design rationale for using a fixed multicast address instead of selecting from a range of multicast addresses using a hash function is discussed in Appendix B. Implementers MAY choose to look up such names concurrently via other mechanisms (e.g., Unicast DNS) and coalesce the results in some fashion. Implementers choosing to do this should be aware of the potential for user confusion when a given name can produce different results depending on external network conditions (such as, but not limited to, which name lookup mechanism responds faster). So let's change this to: - The mDNS IPv4 link-local multicast address "`224.0.0.251`" or its IPv6 equivalent "`FF02::FB`" are used to make DNS query for a name ending with "`.local.`" ** As for "NM or Wicd", you have a good point. Question is what about KDE/LXDE/.... OK, I see network-manager-kde. I take your text. ** As for `iptables`(8), nftables(8) may needs to be mentioned. | WIKIPEDIA: | The currently used iptables(8), ip6tables(8), arptables(8), and | ebtables(8) (IPv4, IPv6, ARP, and Ethernet bridging) are intended to be | replaced with nftables(8) as a single unified implementation, providing | firewall configuration on top of the in-kernel virtual machine. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
