Enable Network for IPV6

[tp1de]

Since I watch WiFi stability I recognized that IPV6 is not enabled (like on my km200 too).

Most of my WLAN/LAN Devices support IPV6 and I recommend to enable on EMS-ESP as well.

[proddy]

I'm not sure it will help with WiFi stability, since EMS-ESP is only a WiFi client. I could make the Web Server and Telnet Server respond to IPV6 but this is just peer-to-peer. Can you give some examples of your other devices that support IPv6 so I can take a look?

[MichaelDvP]

I've tested to enable IPv6 for dynamic IP, adding to WebStatusService.cpp line 39:

    case SYSTEM_EVENT_STA_CONNECTED:
        WiFi.enableIpV6();
        break;
    case SYSTEM_EVENT_ETH_CONNECTED:
        ETH.enableIpV6();
        break;
    case SYSTEM_EVENT_GOT_IP6:
#ifndef EMSESP_STANDALONE
        EMSESP::logger().info(F("WiFi Connected with IP=%s, hostname=%s"), WiFi.localIPv6().toString().c_str(), WiFi.getHostname());
#endif
        break;

Using the above addition i got the ipv6, can ping it, but can not connect to Webpage and telnet via IPv6.
AsyncTCP does not handle it for now. There is a PR, but not merged.

[proddy]

We use local copies of the libraries so I updated AsyncTCP with https://github.com/husarnet/AsyncTCP/tree/master/src and added your changes. Seems to work with WiFi. The Eth causes a crash which needs looking into

[proddy]

found the reason for the crash and made a small change

[tp1de]

Seems to work. Good job !

[tp1de]

@proddy @MichaelDvP

I tested a bit more:

1. DHCP for IPV6 is working
2. Web-ui is available with IPV6 address
3. API V3 is working with IPV6
4. my ioBroker Adaper works with IPV6 address for EMS-ESP
5. Not working: Enter IPV6 addresses for Syslog-Server or MQTT-Broker (not a valid ip address)

I think 5 is a check you implemented and can be easily adjusted. The rest is working.

[proddy]

Not working: Enter IPV6 addresses for Syslog-Server or MQTT-Broker (not a valid ip address)

The fix here is to add an additional Javascript RegExp form field validator like interface/src/validators/isIP.ts to allow 8 groups of hextets (e.g. 2001:0db8:85a3:0000:0000:8a2e:0370:7334) or a range.

[MichaelDvP]

The regexp is one fix (it should allow also shorteners like FE00::1), but mqtt and syslog does not handle ipv6 for now.
Mqtt uses AsyncTCP, it's only a small addition, i'm currently testing a modification.
Syslog seems to have some defines (ARP_CHECK, NDP_CHECK, LWIP_xx) to handle ipv6, but i do not understand for now. Also destination(host, port) uses only IPv4.

BTW: @proddy What do you think about adding the WiFi-tweaks (IPv6, Bandwidth, Tx-power) to Network settings? Maybe some other people want to use it without recompiling.

[proddy]

BTW: @proddy What do you think about adding the WiFi-tweaks (IPv6, Bandwidth, Tx-power) to Network settings? Maybe some other people want to use it without recompiling.

@MichaelDvP good idea. I would call it "WiFi low power mode"

[tp1de]

Excellent idea to have selectable parameters since I was not able yet to compile for use with 20Mhz bandwidth.
Maybe you should name it "WiFi-Bandwidth".

[proddy]

it does more than just the HT20, it lowers the tx transmit power, disables sleep mode and turns off Bluetooth. basically, it lowers the power consumption of the whole gateway board (BBQKees and I have been doing some benchmarking)

[tp1de]

That's good to hear. The 40MHz bandwidth ( max 150 Mbit/s) is not needed at all. So why not making it standard?