• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Bittorrent / DHT / UDP Problem

Scheduled Pinned Locked Moved Firewalling
5 Posts 4 Posters 4.9k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    bob
    last edited by Nov 20, 2006, 1:41 PM

    Hi,
    one weird thing with pfSense. I installed Azureus and uTorrent (only ONE runs at a time). BT is using one port for TCP and UDP so I set up the forward. TCP is reachable but the DHT status always shows up as firewalled (which indicates UDP forward is not working).

    Strange enough, I then removed the forward and installed the UPnP package, activated the option in Azureus and uTorrent and everything is working.

    Makes we wonder if there is a bug with UDP forwarding if you set it up manually? I'm running 1.0.1.

    1 Reply Last reply Reply Quote 0
    • C Offline
      cappycdn
      last edited by Nov 20, 2006, 2:15 PM

      I have both pfsense 1.0.1 and Azureus and I have noticed the DHT firewalled, but it does go away after a short time.

      1 Reply Last reply Reply Quote 0
      • B Offline
        bob
        last edited by Nov 20, 2006, 2:26 PM

        Strange. My Azureus is running 24/7 and DHT always showed as firewalled. Only with the UPnP it's working fine. And the UPNP Status page shows nothing at all… but it's working.

        1 Reply Last reply Reply Quote 0
        • H Offline
          hoba
          last edited by Nov 20, 2006, 3:47 PM

          I'm using utorrent without upnp package. Only have one portforward in place for it and it does not show up as firewalled.

          1 Reply Last reply Reply Quote 0
          • D Offline
            databeestje
            last edited by Dec 9, 2006, 10:34 AM

            this may be attributed to NAT reflection not being enabled on all configurations.

            The clients checks itself by connecting to the outside port it forwarded and see if it works. eMule has some KAD network issues with this UDP port forward as well. So yes, it would actually work from the outside. But testing from the inside would/could fail.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              [[user:consent.lead]]
              [[user:consent.not_received]]