Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so začiniła a archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Firefox Ports Outbound: 50000 - 65535

  • 1 wotmołwa
  • 1 ma tutón problem
  • 12 napohladow
  • Poslednja wotmołwa wot cor-el

more options

Why does Firefox use dynamic ports in the 50K+ range when I use it to browse the web?

I have included screen shots with netstat -AB as well as currports.

Furthermore, if I set a rule in Windows Firewall blocking outbound traffic on ports 50000 - 65535, it breaks DNS with Firefox, even though 53 UDP is open.

I'm not overly concerned with any connection that is localhost / 127.0.0.1.

I've tried prohibiting these ports by modifying user.js - No impact, only works if I implicitly call out the port (example.com:55000)

What do? Why is FF using these ports?

Why does Firefox use dynamic ports in the 50K+ range when I use it to browse the web? I have included screen shots with netstat -AB as well as currports. Furthermore, if I set a rule in Windows Firewall blocking outbound traffic on ports 50000 - 65535, it breaks DNS with Firefox, even though 53 UDP is open. I'm not overly concerned with any connection that is localhost / 127.0.0.1. I've tried prohibiting these ports by modifying user.js - No impact, only works if I implicitly call out the port (example.com:55000) What do? Why is FF using these ports?

Wšě wotmołwy (2)

more options
more options

This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.