Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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

Thread ini telah diarkib. Sila tanya soalan baru jika anda perlu bantuan.

Firefox Ports Outbound: 50000 - 65535

  • 1 balasan
  • 1 ada masalah ini
  • 12 paparan
  • Balasan terakhir oleh 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?
Lampirkan skrinsyot

All Replies (1)

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

See Loopback connection =>