Particle Argon allowing access to network for in field site

This should be a simple one but wanter to make sure I get it right! We are putting a project in field
I’m just coordinating with the network person for the site to make sure our devices can get access to their network. They’ve asked the following

“Allowing access to​ https://console.particle.io (https://console.particle.io/) – I can see this resolves to cloudfront IP 13.32.73.91 currently. Does this change or is it a fixed address for the site?”

I assume it’s a fixed address?

That’s the IP address of the console, but not what the Argon connects to. The Argon itself sends UDP packets to port 5684 address <device_id>. udp-mesh.particle.io. It also will receive packets from the IP address it sends to, which should be automatically handled by the router and does not require dedicated port forwarding in most cases. It also requires working DNS (UDP 53) and uses 8.8.8.8 as the DNS server.

The IP addresses of the cloud are subject to change. These are the current IP addresses for the Argon, Boron, Electron, and E Series, but could change in the future:

54.226.52.22
34.194.48.89
54.86.198.203
3.227.163.177
3.210.194.186
3.225.113.205
3.222.253.60
3.228.117.244
54.82.141.176
3.85.71.8

3.224.151.208
52.22.68.60
52.70.88.102
3.229.224.193
100.25.253.74
34.233.0.183
3.221.51.74
52.70.247.238
3.223.76.106
54.89.110.189

1 Like

Thank you so much @rickkas7 giving the network teams this info is helping a lot.

I had struggles today on a new network - the particle went through it’s normal cycle but got stuck with connecting- it flash cyan fast then orange 3 times - then back to cyan fast then orange (repeat)

The network info is below - I’m guessing the issue might be the IP address range?

WiFi-ReceivArea wifi has no blocks on outbound traffic. All ports are open for outbound traffic from that network interface.

DHCP provides 8.8.8.8 as DNS.

DHCP IP range is 10.10.100.100 to 10.10.100.254

Gateway is 10.10.100.1

DNS is 8.8.8.8