pfsense and telegram
I am fully able to make and receive messages in telegram, but as soon as I try and make a voice call, pfsense apparently seems to fail the connection of the calls, and I have disabled all of my other packages that could possibly be interfering with this in an effort to pinpoint whats not playing nice, so squid is fully disabled, but as soon as I try and make a voice call in telegram using pfsense, it fails to connect, and hangs indefinitely till the call attempt drops
anybody have any ideas whats not playing nice on the firewall rules side of things?
if it helps, I'm using the setup recommended by this article, so I have pfsense set up as a default deny, so I know its something I need to add rules to let work, but that's where I'm not figuring out what I need to add. if anyone needs more information, like my rules, please let me know and I will add them accordingly
This is also happening with me. To summarize:
- Telegram Desktop refuses to work at all (on Linux, at least);
- Telegram Web gets stuck in the "generating keys" part, and eventually resets to asking for my phone number again (i.e. the beginning).
- Telegram Mobile (the normal one, not Telegram X) sometimes gets stuck in synchronization actions, like sending my messages, or retrieving new ones.
None of these things were happening with my previous TP-Link router. I have a single EWAN internet connection (but will get a second one soon, and will configure failover/LB).
Don't know if Telegram uses some sort of p2p connection to do whatever it needs to do, but even so, I've activated UPnP, and it doesn't seem to make any difference. Perhaps some extra ACL rule is needed, but due to the nature of the app/service, this will be difficult to put into practice.
Or perhaps MTProto has some peculiarity that takes advantage of common router configurations, or scenarios that may not be applicable to pfsense users. My firewall logs don't show anything relevant, as far as I could tell.
Got to investigate further...
Hello. I work with Telegram every day. But I have a Windows operating system. There have never been any problems with either the computer version or the phone application. Linux may not support Telegram or partially.
Maybe not naively, but when using this guide it's blocked thus what im trying to find out what to allow: https://forum.netgate.com/topic/70170/taming-the-beasts-aka-suricata-blueprint @DavidSmitis so let me ask you this if it works fine for you, how, if i may, do you have your lan rules set up?? Because mine are, per that article, set to only allow specific ports out from lan, I'm nearly positive that's what's blocking it, but not knowing what ports telegrams audio calls use means I've not yet fixed the audio calls being blocked
I HAVE FOUND THE SOLUTION AND THE SOURCE OF MY PROBLEM EVERYBODY: TO ANYONE ELSE WHO HAS AUDIO CALLS BEING BLOCKED, THE ANSWER IS THIS: telegram has a set collection of servers/hosts as we all know, what I DIDNT know is that apparently telegrams audio calls use UDP ports (I didnt do exact math, but just lumped the combination of ports I had collected logs from to a lump of 100) 500-600 on UDP to make/connect the calls!
SO the answer was allow telegram's servers UDP access to ports 500-600 just to lump it up and get it working and it connected right off the bat this time!
This post is deleted!