@jasgot said in Understanding STUN???:
I am trying to understand what STUN does. I have some UniFi APs out in the wild behind a NAT device, and I have a Network Controller in an office behind a NAT device.
I am getting STUN errors on the APs, but I'm not sure if I need to worry about it.
when I look at this statement in the UI documentation:
In simple terms, STUN provides a way for devices to securely communicate with
other devices when they're located behind a router.
It's unclear if they are discussion my scenario, where the APs and the Controller are not behind the same NAT device. Also, is STUN so APs behind NAT can talk to other APs behind the SAME NAT?
If they're behind the same NAT, nothing additional is needed for the APs to communicate between each other.
The problem is I have a configuration they do not specifically address, and I don't know if their statements apply to my secenario.
Thanks.
STUN allows a device to reach outside of it's local network. It does not allow devices behind two disparate networks to communicate.
You'll need to open network ports to the UniFi controller on the firewall it sits behind. See https://help.ui.com/hc/en-us/articles/218506997-UniFi-Ports-Used
I think you only need 8080/3478 if you are only managing devices remotely, been a while so I'm not 100% sure on that.