Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Firefox Ports Outbound: 50000 - 65535

  • 1 èsì
  • 1 ní ìṣòro yìí
  • 12 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ cor-el

underpasscaviar
underpasscaviar
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?
Ìsopọ̀ yíyà aṣàfihàn

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See Loopback connection =>