NAT traversal в embedded P2P-мессенджере на Go: почему overlay routing, а не STUN/TURN/ICE
NAT traversal в embedded P2P-мессенджере на Matrix-протоколе. Стек: форк Dendrite, Pinecone overlay routing, gomobile bind. Разбор почему overlay routing, а не STUN/TURN/ICE или libp2p, и где этот подход начинает течь.
https://habr.com/ru/articles/1043134/
#nat_traversal #p2p #matrix #overlay_routing #gomobile #pinecone #webrtc #libp2p #dendrite #stun
SIU investigating as man killed after shot by Barrie police stun gun
https://misryoum.com/us/canada-news/siu-investigating-as-man-killed-after-shot-by/
Ontario’s police watchdog says a man in Barrie is dead after police shot him with a stun gun. Barrie police say they pulled over a vehicle in the area of Dunlop Street West and Frances Street around 3:30 a.m....
#SIU #investigating #man #killed #after #shot #Barrie #police #stun #gun #US_News_Hub #misryoum_com
An XMPP developer pointed me to configuration issues with the trashserver.net TURN/STUN service.
This service is required for video call setups and is probably not used by a lot of people, but still: It was broken and might have caused some issues with video calls (haven't observed any issues with it myself, though...)
Nonetheless: The issues _should_ be fixed now.
Few days ago I successfully configured #coturn to have a TURN/STUN server for in-family calls. But … looks like bots or some bad guys constantly trying to connect to my TURN server to use it for something :-(
Of course, it is impossible, since anonymous access or any other access without right key is impossible. But, there are no IPs of attackers in the log file, even wth "Verbose" directive — only my local and public IPs and my server's hostname 
Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?
Had to open 5060 inbound to get one providers trunk to signal inbound calls (either #STUN isn't working there or some #NAT issues), with predictable results..
Got older version of #fail2ban on this box to yeet all blighters trying to get in - by turning on security logging in /etc/asterisk/logfiles_custom.conf (add entry security_log => security), updating regexes in /etc/fail2ban/filter.d and pointing failt2ban jail to check /var/log/asterisk/security_log (main Asterisk log is in wrong format and I don't know enough regex to fix that)
Also registered a #Voipfone virtual PBX extension to use as an extra trunk (needs contact-user and from-user set in #PJSIP config)
The picture @alex drew a few months back sums up exactly what dealing with these #VOIP #trunks is like
Habr
Kpop News Hub
misryoum global news network
650thz.de Services
Dragon of BSDCafe 
Alex@rtnVFRmedia Suffolk UK
BlablaLinux
Dave 
iroh