IPv6 addresses cannot connect

[Steve-Mcl]

Current Behavior

If user has specified !Pv6 address, WS (via MQTT.js) throws an error

Full details in MQTT.JS issue raised here: https://github.com/mqttjs/MQTT.js/issues/1569

Expected Behavior

IPv6 addresses should connect

Steps To Reproduce

• Set broker config in flowforge.yml to use ::1 (or any other IPv6 address)
• Start FlowForge
• regenerate a device credentials, copy to device & run the agent

example yml section for project nodes MQTT Broker Configuration:

#################################################
# MQTT Broker Configuration                     #
#################################################

broker:
  ## Internal url used by the platform to connect to the broker
  url: mqtt://[::1]:9883
  ## External url used by devices to connect to the broker, if different
  public_url: ws://[::1]:9884

Environment

• FlowForge version: 1.x-git
• Node.js version: 16
• npm version: 8
• Platform/OS: Windows/Linux
• Browser:

[Steve-Mcl]

Tested localfs, windows and linux - OK.

@hardillb is it possible to adjust an IPv4 to IPv6 on staging (or your own k8s) to test this pls?

[hardillb]

Enabling IPv6 on AWS would not be useful in this case, because access is always going to be via a Hostname not a bare IP address. It has to be because the hostname needs to match the TLS certificate.

[Steve-Mcl]

ok, so local test only is all we can achieve at this point.

[hardillb]

And localfs is the only place bare IP addresses should ever be used