home.social

#stun — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #stun, aggregated by home.social.

  1. Don't . Teach they are not worth using. My is set to .

  2. SIU investigating as man killed after shot by Barrie police stun gun

    misryoum.com/us/canada-news/si

    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

  3. #NATTraversal: Kỹ thuật giúp thiết bị đằng sau NAT kết nối trực tiếp bằng STUN (phát hiện địa chỉ công cộng), UDP hole punching (tạo lỗ hổng NAT) và TURN (hướng dẫn qua máy chủ trung gian). CGNAT & NAT đối xứng khiến 15-30% kết nối cần dùng thưc vụ trung chuyển.웹RTC cần TURN để đảm bảo kết nối ổn định. #WebRTC #IPv6 #Mạng Máy Tính #Công Nghệ #TechVN #Networking #STUN #TURN #ICENAT #CGNAT

    (Nguồn: Bài viết kỹ thuật giải thích NAT traversal từ nguyên lý cơ bản đến ứng dụng thực tế) #KỹThuậtMạng

  4. 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 :drgn_cry:

    Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?

    #TURN #STUN #selfhosting #networking #AskFedi

  5. 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 :drgn_cry:

    Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?

    #TURN #STUN #selfhosting #networking #AskFedi

  6. 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 :drgn_cry:

    Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?

    #TURN #STUN #selfhosting #networking #AskFedi

  7. 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 :drgn_cry:

    Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?

    #TURN #STUN #selfhosting #networking #AskFedi

  8. 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 :drgn_cry:

    Maybe, there is some way to force coturn to display IP addresses of connected clients, so I could ban them all with fail2ban?

    #TURN #STUN #selfhosting #networking #AskFedi

  9. 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

    #Asterisk #FreePBX

  10. 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

    #Asterisk #FreePBX

  11. 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

    #Asterisk #FreePBX

  12. 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

    #Asterisk #FreePBX

  13. 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

    #Asterisk #FreePBX

  14. Hier soir, je m'ennuyais !
    J'ai donc décidé de mettre en place deux serveurs backend haute performance #Talk ( #TURN / #STUN ) pour mes deux serveurs #cloud #NextCloud 😎
    👉 nextcloud-talk.readthedocs.io/
    👉 bytestash.blablalinux.be/s/e6b

  15. Hier soir, je m'ennuyais !
    J'ai donc décidé de mettre en place deux serveurs backend haute performance #Talk ( #TURN / #STUN ) pour mes deux serveurs #cloud #NextCloud 😎
    👉 nextcloud-talk.readthedocs.io/
    👉 bytestash.blablalinux.be/s/e6b

  16. Hier soir, je m'ennuyais !
    J'ai donc décidé de mettre en place deux serveurs backend haute performance #Talk ( #TURN / #STUN ) pour mes deux serveurs #cloud #NextCloud 😎
    👉 nextcloud-talk.readthedocs.io/
    👉 bytestash.blablalinux.be/s/e6b

  17. Hier soir, je m'ennuyais !
    J'ai donc décidé de mettre en place deux serveurs backend haute performance #Talk ( #TURN / #STUN ) pour mes deux serveurs #cloud #NextCloud 😎
    👉 nextcloud-talk.readthedocs.io/
    👉 bytestash.blablalinux.be/s/e6b

  18. Did you know that we like #QUIC?

    We like it so much we're replacing our use of #STUN over UDP with QUIC Address Discovery!

    We've contributed an implementation of that standard to the #Quinn #RustLang library, and are now using it.

    iroh.computer/blog/qad

  19. Did you know that we like #QUIC?

    We like it so much we're replacing our use of #STUN over UDP with QUIC Address Discovery!

    We've contributed an implementation of that standard to the #Quinn #RustLang library, and are now using it.

    iroh.computer/blog/qad

  20. Did you know that we like #QUIC?

    We like it so much we're replacing our use of #STUN over UDP with QUIC Address Discovery!

    We've contributed an implementation of that standard to the #Quinn #RustLang library, and are now using it.

    iroh.computer/blog/qad

  21. Did you know that we like #QUIC?

    We like it so much we're replacing our use of #STUN over UDP with QUIC Address Discovery!

    We've contributed an implementation of that standard to the #Quinn #RustLang library, and are now using it.

    iroh.computer/blog/qad

  22. Did you know that we like #QUIC?

    We like it so much we're replacing our use of #STUN over UDP with QUIC Address Discovery!

    We've contributed an implementation of that standard to the #Quinn #RustLang library, and are now using it.

    iroh.computer/blog/qad

  23. Звонки через Jabber в докер-контейнере за 5 минут

    В свете сами знаете чего, свой приватный мессенджер и возможность звонков на XMPP стали как никогда актуальны. Есть быстрый и простой способ: за несколько минут вы поднимаете собственный Jabber-сервер. Дальше — дело техники: рассылаете приглашения маме, бабушке, теще, жене и соседке Даше. После этого можно спокойно звонить и переписываться в защищённом мессенджере, который полностью под вашим контролем. Звонки идут в зашифрованном режиме, работают p2p. А если у собеседника хитрый NAT, то на помощь автоматически приходит встроенный STUN-сервер. Клиенты есть под все платформы: Android, iOS, Windows, macOS и Linux.

    habr.com/ru/articles/938760/

    #jabber #xmpp #docker #turn #stun

  24. Звонки через Jabber в докер-контейнере за 5 минут

    В свете сами знаете чего, свой приватный мессенджер и возможность звонков на XMPP стали как никогда актуальны. Есть быстрый и простой способ: за несколько минут вы поднимаете собственный Jabber-сервер. Дальше — дело техники: рассылаете приглашения маме, бабушке, теще, жене и соседке Даше. После этого можно спокойно звонить и переписываться в защищённом мессенджере, который полностью под вашим контролем. Звонки идут в зашифрованном режиме, работают p2p. А если у собеседника хитрый NAT, то на помощь автоматически приходит встроенный STUN-сервер. Клиенты есть под все платформы: Android, iOS, Windows, macOS и Linux.

    habr.com/ru/articles/938760/

    #jabber #xmpp #docker #turn #stun

  25. Звонки через Jabber в докер-контейнере за 5 минут

    В свете сами знаете чего, свой приватный мессенджер и возможность звонков на XMPP стали как никогда актуальны. Есть быстрый и простой способ: за несколько минут вы поднимаете собственный Jabber-сервер. Дальше — дело техники: рассылаете приглашения маме, бабушке, теще, жене и соседке Даше. После этого можно спокойно звонить и переписываться в защищённом мессенджере, который полностью под вашим контролем. Звонки идут в зашифрованном режиме, работают p2p. А если у собеседника хитрый NAT, то на помощь автоматически приходит встроенный STUN-сервер. Клиенты есть под все платформы: Android, iOS, Windows, macOS и Linux.

    habr.com/ru/articles/938760/

    #jabber #xmpp #docker #turn #stun

  26. Звонки через Jabber в докер-контейнере за 5 минут

    В свете сами знаете чего, свой приватный мессенджер и возможность звонков на XMPP стали как никогда актуальны. Есть быстрый и простой способ: за несколько минут вы поднимаете собственный Jabber-сервер. Дальше — дело техники: рассылаете приглашения маме, бабушке, теще, жене и соседке Даше. После этого можно спокойно звонить и переписываться в защищённом мессенджере, который полностью под вашим контролем. Звонки идут в зашифрованном режиме, работают p2p. А если у собеседника хитрый NAT, то на помощь автоматически приходит встроенный STUN-сервер. Клиенты есть под все платформы: Android, iOS, Windows, macOS и Linux.

    habr.com/ru/articles/938760/

    #jabber #xmpp #docker #turn #stun

  27. Needed a picture for some VoIP technical guide articles on SIP ALG, rport, STUN, etc... got to love a bit of #chatgpt #openai art 😂

    #voip #plexatalk #nat #sip #stun #pbx #tech #technology #WordPress #chatgpt5

  28. Needed a picture for some VoIP technical guide articles on SIP ALG, rport, STUN, etc... got to love a bit of #chatgpt #openai art 😂

    #voip #plexatalk #nat #sip #stun #pbx #tech #technology #WordPress #chatgpt5

  29. Needed a picture for some VoIP technical guide articles on SIP ALG, rport, STUN, etc... got to love a bit of #chatgpt #openai art 😂

    #voip #plexatalk #nat #sip #stun #pbx #tech #technology #WordPress #chatgpt5

  30. Needed a picture for some VoIP technical guide articles on SIP ALG, rport, STUN, etc... got to love a bit of #chatgpt #openai art 😂

    #voip #plexatalk #nat #sip #stun #pbx #tech #technology #WordPress #chatgpt5

  31. TURN/STUN — платить или крутить свой?

    Как выбрать между своим TURN-сервером, бесплатными решениями и платными сервисами: живой разбор без маркетинга

    habr.com/ru/articles/923862/

    #matrix #turn #stun

  32. TURN/STUN — платить или крутить свой?

    Как выбрать между своим TURN-сервером, бесплатными решениями и платными сервисами: живой разбор без маркетинга

    habr.com/ru/articles/923862/

    #matrix #turn #stun

  33. TURN/STUN — платить или крутить свой?

    Как выбрать между своим TURN-сервером, бесплатными решениями и платными сервисами: живой разбор без маркетинга

    habr.com/ru/articles/923862/

    #matrix #turn #stun

  34. TURN/STUN — платить или крутить свой?

    Как выбрать между своим TURN-сервером, бесплатными решениями и платными сервисами: живой разбор без маркетинга

    habr.com/ru/articles/923862/

    #matrix #turn #stun

  35. 🔐 No servers. No metadata. Just encrypted WebRTC over Tor.
    (@torproject)

    Privora now supports secure P2P calls & messages with full E2EE, self-hosted STUN/TURN & zero cloud.

    📖 Read more: privora.netlify.app/blog/secur

    #WebRTC #Tor #E2EE #PrivacyByDesign #Decentralized #CyberSecurity #STUN #TURN #Privora

  36. 🔐 No servers. No metadata. Just encrypted WebRTC over Tor.
    (@torproject)

    Privora now supports secure P2P calls & messages with full E2EE, self-hosted STUN/TURN & zero cloud.

    📖 Read more: privora.netlify.app/blog/secur

    #WebRTC #Tor #E2EE #PrivacyByDesign #Decentralized #CyberSecurity #STUN #TURN #Privora

  37. #news ⚡ Patienten verbringen Hunderte Millionen Stunden in Wartezimmern: Deutschlands Patienten verbringen jährlich Hunderte Millionen Stunden in Wartezimmern. Der volkswirtschaftliche Schaden dürfte in die... hubu.de/?p=274118 | #patienten #hunderte #millionen #stun

  38. #news ⚡ Patienten verbringen Hunderte Millionen Stunden in Wartezimmern: Deutschlands Patienten verbringen jährlich Hunderte Millionen Stunden in Wartezimmern. Der volkswirtschaftliche Schaden dürfte in die... hubu.de/?p=274118 | #patienten #hunderte #millionen #stun

  39. #news ⚡ Patienten verbringen Hunderte Millionen Stunden in Wartezimmern: Deutschlands Patienten verbringen jährlich Hunderte Millionen Stunden in Wartezimmern. Der volkswirtschaftliche Schaden dürfte in die... hubu.de/?p=274118 | #patienten #hunderte #millionen #stun

  40. Can someone help me with #WebRTC #STUN and #TURN with CoTurn?
    I have several WebRTC components (one server, local), one coturn server (local), one web frontend (local), and one browser (local).

    Coturn is eventually just drops:
    closed (2nd stage), user <> realm <hub.kerberos.home.xc> origin <>, local 172.19.66.66:3478, remote 192.168.178.52:58481, reason: allocation watchdog determined stale session state

    Not sure why though.

  41. Can someone help me with #WebRTC #STUN and #TURN with CoTurn?
    I have several WebRTC components (one server, local), one coturn server (local), one web frontend (local), and one browser (local).

    Coturn is eventually just drops:
    closed (2nd stage), user <> realm <hub.kerberos.home.xc> origin <>, local 172.19.66.66:3478, remote 192.168.178.52:58481, reason: allocation watchdog determined stale session state

    Not sure why though.

  42. WebRTC. Как установить p2p соединение между браузерами

    WebRTC позволяет браузерам обмениваться информацией напрямую без сервера. Можно передавать видео, звук и данные. Установить WebRTC соединение можно разными способами. В статье описано как WebRTC соединение устанавливается между пользователями редактора схем dgrm.net .

    habr.com/ru/articles/799863/

    #webrtc #stun #turn #javascript #p2p #p2pсети

  43. WebRTC. Как установить p2p соединение между браузерами

    WebRTC позволяет браузерам обмениваться информацией напрямую без сервера. Можно передавать видео, звук и данные. Установить WebRTC соединение можно разными способами. В статье описано как WebRTC соединение устанавливается между пользователями редактора схем dgrm.net .

    habr.com/ru/articles/799863/

    #webrtc #stun #turn #javascript #p2p #p2pсети

  44. WebRTC. Как установить p2p соединение между браузерами

    WebRTC позволяет браузерам обмениваться информацией напрямую без сервера. Можно передавать видео, звук и данные. Установить WebRTC соединение можно разными способами. В статье описано как WebRTC соединение устанавливается между пользователями редактора схем dgrm.net .

    habr.com/ru/articles/799863/

    #webrtc #stun #turn #javascript #p2p #p2pсети