diff --git a/configs/dk-tm4c129x/README.txt b/configs/dk-tm4c129x/README.txt index 291323da4a..9e5aa4ebd0 100644 --- a/configs/dk-tm4c129x/README.txt +++ b/configs/dk-tm4c129x/README.txt @@ -757,7 +757,8 @@ Where is one of the following: configuration other than using IPv6. So all of the notes above regarding the nsh configuration apply. - Telnet does not work with IPv6. + Telnet does work with IPv6 but is not enabled in this + configuration (but could be). 2. This configuration can be modified to that both IPv4 and IPv6 are support. Here is a summary of the additional configuration @@ -788,9 +789,14 @@ Where is one of the following: ping6 fc00::2 (Linux) ping -6 fc00::2 (Windows cmd) - and Telnet again works from the host: + and Telnet is now enabled and works from the host... but only using + IPv6 addressing: - telnet 10.0.0.2 + telnet fc00::2 + + That is because the Telnet daemon will default to IPv6 and there is + no Telnet option to let you select which if both IPv4 and IPv6 are + enabled. 3. You can enable IPv6 autonomous address configuration with the following changes to the configuration: diff --git a/configs/sama5d4-ek/README.txt b/configs/sama5d4-ek/README.txt index 4ea1109f88..c8bb1c0192 100644 --- a/configs/sama5d4-ek/README.txt +++ b/configs/sama5d4-ek/README.txt @@ -3948,7 +3948,8 @@ Configurations configuration other than using IPv6. So all of the notes below regarding the nsh configuration apply. - Telnet does not work with IPv6. + Telnet does work with IPv6 but is not enabled in this + configuration (but could be). 2. This configuration can be modified to that both IPv4 and IPv6 are support. Here is a summary of the additional configuration @@ -3979,9 +3980,14 @@ Configurations ping6 fc00::2 (Linux) ping -6 fc00::2 (Windows cmd) - and Telnet again works from the host: + and Telnet is now enabled and works from the host... but only using + IPv6 addressing: - telent 10.0.0.2 + telnet fc00::2 + + That is because the Telnet daemon will default to IPv6 and there is + no Telnet option to let you select which if both IPv4 and IPv6 are + enabled. 3. You can enable IPv6 autonomous address configuration with the following changes to the configuration: diff --git a/configs/stm32f4discovery/README.txt b/configs/stm32f4discovery/README.txt index b748027d83..6cc16183ee 100644 --- a/configs/stm32f4discovery/README.txt +++ b/configs/stm32f4discovery/README.txt @@ -1349,7 +1349,8 @@ Where is one of the following: configuration other than using IPv6. So all of the notes above regarding the netnsh configuration apply. - a. Telnet does not work with IPv6. + a. Telnet does work with IPv6 but is not enabled in this + configuration (but could be). b. The network initialization thread was enabed in the netnsh configuration on 2015-09-28, but not in the ipv6 configuration. @@ -1382,9 +1383,14 @@ Where is one of the following: ping6 fc00::2 (Linux) ping -6 fc00::2 (Windows cmd) - and Telnet again works from the host: + and Telnet is now enabled and works from the host... but only using + IPv6 addressing: - telent 10.0.0.2 + telnet fc00::2 + + That is because the Telnet daemon will default to IPv6 and there is + no Telnet option to let you select which if both IPv4 and IPv6 are + enabled. 3. I have used this configuration to serve up IP address prefixes in a local network with these modifications to the configuration: diff --git a/configs/tm4c1294-launchpad/README.txt b/configs/tm4c1294-launchpad/README.txt index 1ed896c3e9..b45511d2cf 100644 --- a/configs/tm4c1294-launchpad/README.txt +++ b/configs/tm4c1294-launchpad/README.txt @@ -112,7 +112,8 @@ Where is one of the following: configuration other than using IPv6. So all of the notes above regarding the nsh configuration apply. - Telnet does not work with IPv6. + Telnet does work with IPv6 but is not enabled in this + configuration (but could be). 2. This configuration can be modified to that both IPv4 and IPv6 are support. Here is a summary of the additional configuration @@ -143,9 +144,14 @@ Where is one of the following: ping6 fc00::2 (Linux) ping -6 fc00::2 (Windows cmd) - and Telnet again works from the host: + and Telnet is now enabled and works from the host... but only using + IPv6 addressing: - telnet 10.0.0.2 + telnet fc00::2 + + That is because the Telnet daemon will default to IPv6 and there is + no Telnet option to let you select which if both IPv4 and IPv6 are + enabled. 3. You can enable IPv6 autonomous address configuration with the following changes to the configuration: