Skip to main content


More thoughts on the STUN server fallback question:

· This is something other #XMPP Clients just do quietly without having a big debate about it¹

· I don't think users should configure this. Anyone who knows what a STUN server is will likely switch to a server offering one.

· Treat it like channel search. On first use (call, file transfer), ask once: Use our fallback STUN server? Yes/No.

¹: github.com/dino/dino/blob/v0.4…

#xmpp
in reply to Daniel Gultsch

with @pidgin we never officially had one nor did we default to anyone in particular. We looked at doing it for awhile but never went forward with it.

This is something we will be looking at again in the nearish future though, but we'd just be offering ip lookups and maybe udp hope punching, but we also don't want our servers to be used in illicit activity either which is where all of this becomes problematic.

in reply to Gary "grim" Kramlich

@grimmy @pidgin To be clear I’m only talking about STUN. I have no intention of running a TURN server.

The specific STUN server that we would be using (stun.conversations.im) is quasi public already.

in reply to Daniel Gultsch

@pidgin gotcha. Originally I was just looking at stun as well, but since that would typically be used for p2p file transfers and stuff, the idea of turn came up.

Also I was looking at using coturn as the actual service. I'll probably set that up soonish even though we're very far away from needing it in pidgin 3 but I could also point pidgin2 at it and get some basic usage monitoring on it.

in reply to Gary "grim" Kramlich

@grimmy @pidgin Offering TURN has diminishing returns. STUN gets you from not being able to establish any connections outside of your local network to 70%. TURN gets you the other 30% but at crazy costs as who ever runs it will be paying for the traffic.
in reply to Daniel Gultsch

@pidgin yea that's why I would rather support udp hole punching but there's not much support for that in existing protocols.
in reply to Daniel Gultsch

at monal we are offering a stun and turn server as fallback (you can disable this in the settings).

So far (over the last ~12 month) we didn't have any traffic excess.
Our stun and turn server seems to be used way less than originally anticipated.

This entry was edited (3 days ago)
in reply to Daniel Gultsch

Another thing to think about is that STUN servers being used in reflection attacks. Doesn't amplify a lot, unless you enable authentication(?!?). So encouraging all server operators to deploy more STUN servers isn't without its complications.