Chryss Posted August 16, 2008 Report Share Posted August 16, 2008 Hi all. I feel silly even having to ask this, because I never had this problem before updating to 1.8, but port triggering seems to be causing issues for me now. The problem is that unless I have something downloading, the incoming port won't trigger. Makes sense, of course, however even when just seeding you're usually sending out enough packets to keep the port open. However this is no longer the case for me. Some small, private trackers don't seem to send enough data to keep the port open. I tried setting the outgoing port range to include the same port as incoming, but that only solved the problem for a short amount of time. Any suggestions? I'm not comfortable leaving that port permanently open as I don't always have UT running. Link to comment Share on other sites More sharing options...
DreadWingKnight Posted August 16, 2008 Report Share Posted August 16, 2008 Don't use port triggering.If there's nothing listening on the port, there's no security issue. Link to comment Share on other sites More sharing options...
Chryss Posted August 16, 2008 Author Report Share Posted August 16, 2008 Good to know, thanks for the quick response Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.