Hi everyone,
"Meet generates both TCP (port443) and UDP (ports 443 and 19302–19309)
traffic."
https://services.google.com/fh/files/blogs/enabling_remote_working_with_hangouts_meet_quick_deployment_guide.pdf
Are they allready open ?
Regards
Bertrand Friconneau
Le 12/01/2021 à 23:40, Diego Quintana Cruz a écrit :
Hello,
Regarding this previous email, I found out that the problem is webRTC,
as the relay connectivity is timing out using
https://test.webrtc.org/. Any ideas on how to solve this issue? I
tried route_filter=no in shorewall conf but the problem persists
e40dfa8d-8048-49e5-b056-51a1f56dec31.jpg
All the best,
Diego
El vie, 25 de dic. de 2020 a la(s) 21:46, Diego Quintana Cruz
(diegoquint...@gmail.com <mailto:diegoquint...@gmail.com>) escribió:
Hello everyone,
I have shorewall installed and allow all the traffic from loc to net.
However, whenever a client in loc starts a google meet call, the
remote party doesn't hear or see anything
In the dump attached, the IP 192.168.10.106 connects to a call,
but the other participants don't hear anything.
Any ideas of what can it be done?
All the best and merry christmas!
Diego Quintana
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
