Solved Understanding STUN???
-
@scottalanmiller said in Understanding STUN???:
You have a Unifi controller that does not have ports forwarded to it?
It does, just not the STUN port.
-
@jasgot said in Understanding STUN???:
@travisdh1 said in Understanding STUN???:
@jasgot said in Understanding STUN???:
@travisdh1 said in Understanding STUN???:
You'll need to open network ports to the UniFi controller on the firewall it sits behind.
Except I'm not certain I even want STUN. If it does not provide a required component for these APS to work (they are working without it now) , I'll likely to leave those ports closed on the controller side.
That's the thing, they'll work in the current configuration, but you can't update any settings.
How so? I can make all kinds of changes and even open a debug terminal to it without STUN working.
Right, because the APs reach out to the controller. They are not audio/visual equipment so they can't use STUN. They have single communications channels to their controller. It's just HTTPS, nothing more. HTTPS can't use STUN and has no need for it.
STUN Is used with SIP + RDP because it is three connections that have to act as one. STUN helps to coordinate them.
-
@jasgot said in Understanding STUN???:
@scottalanmiller said in Understanding STUN???:
You have a Unifi controller that does not have ports forwarded to it?
It does, just not the STUN port.
I don't think Unifi offers STUN services anyway.
-
@jasgot said in Understanding STUN???:
@scottalanmiller said in Understanding STUN???:
The APs themselves have STUN errors? I've never seen that. Can you show the error?
The errors are listed in the controller.
Can you show them?
-
-
@jasgot apparently Unifi uses STUN for some UDP traffic stuff in some cases. None of the normal stuff, must be log shipping which is a communications channel. They recommend having the port opened and forwarded. But it shouldn't cause problems. They noted that they only added the warning recently so it might have always had the issue without reporting it previously.
-
@scottalanmiller said in Understanding STUN???:
They noted that they only added the warning recently so it might have always had the issue without reporting it previously.
Okay. Sounds like I can just ignore it. I would like to be able to turn off the warning, though!
-
@jasgot said in Understanding STUN???:
@scottalanmiller said in Understanding STUN???:
They noted that they only added the warning recently so it might have always had the issue without reporting it previously.
Okay. Sounds like I can just ignore it. I would like to be able to turn off the warning, though!
Yeah, very ignorable. But... why not just open the port and make it go away?
-
@scottalanmiller said in Understanding STUN???:
Yeah, very ignorable. But... why not just open the port and make it go away?
That was a good idea. It worked. Now I won't stress because something is less than perfect.
-
@jasgot said in Understanding STUN???:
@scottalanmiller said in Understanding STUN???:
Yeah, very ignorable. But... why not just open the port and make it go away?
That was a good idea. It worked. Now I won't stress because something is less than perfect.
LOL
-
@scottalanmiller said in Understanding STUN???:
@jasgot apparently Unifi uses STUN for some UDP traffic stuff in some cases. None of the normal stuff, must be log shipping which is a communications channel. They recommend having the port opened and forwarded. But it shouldn't cause problems. They noted that they only added the warning recently so it might have always had the issue without reporting it previously.
If by recently they mean 3 years ago, then I guess that was recent.. I've been having those errors for what seems like ages.
-
@dashrender said in Understanding STUN???:
@scottalanmiller said in Understanding STUN???:
@jasgot apparently Unifi uses STUN for some UDP traffic stuff in some cases. None of the normal stuff, must be log shipping which is a communications channel. They recommend having the port opened and forwarded. But it shouldn't cause problems. They noted that they only added the warning recently so it might have always had the issue without reporting it previously.
If by recently they mean 3 years ago, then I guess that was recent.. I've been having those errors for what seems like ages.
Correct, this has been there for ages now. STUN errors are common on Cloud Controllers which is all we have.
-
J JasGot has marked this topic as solved on
