Skip to main content

IT Network

Network configuration checklist (quick summary)​

  • Assign static IPs to Modbus assets and to web assets accessible via the "Console".
  • Check that local ports are open/accessible: 502 (Modbus TCP), 8080 (OCPP WebSocket), 80/443 (web Console).
  • Assign a static IP to the Fuzz Local Controller
  • Allow outbound traffic to 63.179.40.7:22 (console.fuzz.energy:22)
  • Allow outbound traffic to AWS services
  • Allow NTP time synchronization (UDP port 123 to *.pool.ntp.org)

Client network configuration​

To enable communication between the Fuzz Energy Local Controller, the local assets, and the Fuzz Energy Console platform, certain network settings must be configured on the client's network.

Ports to open​

The network must allow outbound Internet connections on port 22 (SSH) to the Fuzz Energy server.

Return traffic handling (stateful firewall)​

The firewall must allow return traffic associated with outbound connections initiated by the Local Controller.

In most cases, this behavior is handled automatically by stateful firewalls. Specific configuration may be required on equipment operating in stateless mode.

Destination server address​

The Local Controller must be able to reach the following server:

console.fuzz.energy whose fixed IP is 63.179.40.7

The client firewall must therefore allow outbound connections to this domain.

DNS resolution​

The Local Controller must have functional access to a DNS server in order to resolve the domain names of external services (AWS, console.fuzz.energy, etc.).

By default, public DNS servers are used (1.1.1.1 and 8.8.8.8), unless a network policy requires the use of internal DNS servers.

The firewall must allow outgoing DNS queries: UDP 53 (and possibly TCP 53)

Time synchronization (NTP)​

The Local Controller must maintain an accurate clock to ensure reliable communications.

  • Protocol: NTP
  • Port: UDP 123
  • Default servers used:
    • 0.debian.pool.ntp.org
    • 1.debian.pool.ntp.org
    • 2.debian.pool.ntp.org
    • 3.debian.pool.ntp.org

Allow outbound UDP 123 to *.pool.ntp.org

Access to AWS services​

Normal operation​

The Local Controller must be able to reach the following endpoints:

  • ab1833q6mlyrv-ats.iot.eu-central-1.amazonaws.com:8883
  • c9nsxgthwgeph.credentials.iot.eu-central-1.amazonaws.com:443
  • greengrass-ats.iot.eu-central-1.amazonaws.com:8443
  • *.s3.amazonaws.com:443
  • *.s3.eu-central-1.amazonaws.com:443

Installation only​

The following endpoints are only needed during installation or provisioning:

  • iot.eu-central-1.amazonaws.com:443
  • iam.amazonaws.com:443
  • sts.eu-central-1.amazonaws.com:443
  • greengrass.eu-central-1.amazonaws.com:443

Communication on the local network​

In addition to exchanges between the Local Controller and console.fuzz.energy (EV Proxy), the Local Controller must also communicate with assets via Modbus TCP and/or OCPP 1.6J (WebSocket) protocols. Many assets also expose a web console (HTTP/HTTPS) for configuration and diagnostics.

Modbus TCP​

  • Default port: 502 (TCP).
  • Role: the Local Controller acts as the Modbus client, while assets (meters, inverters, batteries, some charge point models) act as Modbus servers.
  • IP address: assets using Modbus TCP must have a fixed IP on the local network.

OCPP 1.6J (WebSocket)​

  • Default port used on the Local Controller side: 8080 (WebSocket).
  • Role: for OCPP, the Local Controller behaves as the server (local endpoint) and charge points are clients that open a WebSocket connection to the Local Controller.
  • Charge point IPs: OCPP charge points do not need a fixed IP to operate, because it is the charge point that initiates the outbound connection.

Asset web consoles (HTTP / HTTPS)​

  • Description: many assets expose a local web interface for configuration and diagnostics. console.fuzz.energy provides a Console link to open this page from the platform.
  • Protocols/ports: HTTP (80) or HTTPS (443) by default; some assets may use a custom port (e.g. 8081, 8443).
  • Address: assign a static IP to the asset so that the "Console" feature works reliably.

Optional services and third-party integrations​

The Local Controller / EV Proxy can send data to and/or exchange commands with third-party platforms. Each integration must be configured and validated.

  • Sending to CPO (Charge Point Operator) The CPO is an optional service enabling billing of charging sessions on charge points. The Local Controller can communicate with a CPO via OCPP 1.6 (WebSocket). The Local Controller is the client and the CPO is the server. The server URL and port depend on the CPO used.

  • Sending to Neofleet Neofleet allows fleet tracking and charge point access management. The destination data server has a fixed IP. Contact us for more information at: support@fuzz.energy.

  • Sending to Izix (or other platforms) Contact us for more information at: support@fuzz.energy.

Client network and Fuzz Energy Local Controller IP​

The Local Controller must have a fixed IP address on the client's local network as soon as the OCPP protocol is used. If OCPP is not used on the site (no charge points), there is no need to set a static IP and the controller keeps its dynamic IP configuration.

Two methods are available to set the IP:

IP via DHCP with reservation​

The controller receives an IP address automatically via DHCP, with a reservation based on the MAC address to guarantee a fixed IP. The MAC address is available on the controller box as well as on its label (left side of the controller). The MAC address of the top port — which should be preferred as it is faster — corresponds to "MAC0". The MAC address must be provided to the client's IT administrator.

IP configured directly on the controller​

A static IP address can also be configured directly on the Local Controller by the Fuzz Energy team.

In this case, the following information must be provided to support@fuzz.energy:

  • IP address
  • Subnet mask
  • Default gateway
  • DNS1 and DNS2 servers

These settings must be provided by the client's network administrator.