AfghanEB

Established Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AfghanEB

  • Rank
    Member
  1. Alright, it looks as though the automatic upload limiting works again but is it possible to have the upload rate status messages appear in the logger tab again without having to enable the verbose option?
  2. I noticed this in the release notes for v1.7 beta 1825: - Change: more even distribution of random listening port on startup So far, however, this beta has not auto-generated a port number higher than 3 digits (it usually sticks to the low 100s range) and even chooses ports in the double-digit(!) range on startup. Is this the intended behavior of the change? I wonder if this could be problematic if it generates a port number that's used by other software such as NewsLeecher which depends on ports such as 119, 443 or 563 for NNTP access. Interestingly enough, if the random port button in the connections option page is clicked, the port numbers there are much higher. On another matter, is it just me or is the automatic upload limiting not working in this latest beta? The status log makes no mention of it even when it's enabled in the options.
  3. This may have been discussed already, but in these newest betas, is there any particular reason as to why UPnP random port mapping seems to be limited to lower (4-digit) port values whereas previous versions had values that ranged all the way up to the tens of thousands? Aside from that difference, UPnP presently works as well as v1.6 does on my Linksys WRT54GX4 router so keep up the nice work.
  4. Excellent, I look forward to trying out the next beta to see how UPnP performs. If it works as well as it did in v1.6 and v1.6.1 then it should be fine.
  5. After further testing with this beta, UPnP does appear to be working (when I have the automatic upload option enabled) but it still encounters the initial "unable to map" delay. [01:02:43] Unable to map UPnP Port. [01:02:43] Unable to map NAT-PMP Port. [01:04:28] Uplink limit auto adjusted to 50.0 kB/s [01:04:34] UPnP: Discovered new device: http://192.168.1.1:5431/uuid:0016b663-6e0e-0016-b663-6e0e02ec0000/WANIPConnection:1 [01:04:35] UPnP: Mapped port 29381 -> 192.168.1.102:29381 In cases where the automatic upload option is disabled, it still starts off with the "unable to map" error and takes the software over 10 minutes to get UPnP working on a later attempt.
  6. This beta isn't having any success with UPnP on my Linksys WRT54GX4 router. [23:29:37] Unable to map UPnP Port. [23:29:37] Unable to map NAT-PMP Port. uTorrent v1.6.1 experienced no such problems. In one instance, v1.7 Beta 1092 reported that it found the router and mapped the port but the uTorrent port checker did not confirm my IP address as being connectable and neither did any of the private tracker sites that I'm connected to.
  7. AfghanEB

    WebUI v0.315

    Alright! I finally realized why I've never been able to have the WebUI automatically update its statistics when I try to access it using my browsers at home. It turns out that having the Ad Muncher utility enabled in the background interferes with the WebUI's statistical updates. Based on what I can see in Ad Muncher's filtering log, there are two ways to get around this problem. TEMPORARY SOLUTION Right-click the Ad Muncher system tray icon and disable its filtering before accessing the WebUI. PERMANENT SOLUTION 1. Ad Muncher Configuration >> Options >> Advanced >> Make sure that the "Prevent interference with mouse usage option" at the bottom is UNCHECKED. 2. Ad Muncher Configuration >> Options >> Filter Targets >> Select your browser name from the program list on the right-hand side. Click on the "don't filter" button then edit the entry in the left-hand box so that it shows a minus sign and the browser's file name followed by the µTorrent port number. In my case, having -iexplore:33525 and -firefox:33525 in the exclude list allows the WebUI to update its statistics properly while Ad Muncher is still enabled. You can repeat this procedure for any other port numbers that are in use by µTorrent. I don't know how many users here use Ad Muncher, but I figure this information might prove useful in getting the WebUI to run properly for those who do. As a side note, something else I've noticed is that if you're trying to access the WebUI on another computer in your network, the proper LAN IP address needs to be typed in to connect since using the WAN IP address doesn't seem to work.
  8. AfghanEB

    WebUI v0.315

    I tried that just now and still no dice. I guess this is one of those things that may have to be worked out in future WebUI updates. Personally, I think it would be nice to see IE6 support since it's still one of the most commonly used browsers today and my default browser of choice.
  9. AfghanEB

    WebUI v0.315

    I tried what you suggested but it did not solve the problem. Updating from v1.5.0.6 to v1.5.0.7 made no difference either. Even the latest FireFox v2.0 Beta 2 experiences these same error messages.
  10. AfghanEB

    WebUI v0.315

    Hmmm. It already is enabled in FireFox by default. But if it's of any relevance, when I click on Tools >> Javascript Console, I see the following error messages in the new window... Error: Unknown property 'zoom'. Declaration dropped. Source File: http://XX.XX.XX.XXX:62862/gui/style.css Line: 149 Error: Unknown property 'filter'. Declaration dropped. Source File: http://XX.XX.XX.XXX:62862/gui/style.css Line: 154 Error: this.WxwInterval is not a function Source File: http://XX.XX.XX.XXX:62862/gui/script.js Line: 54
  11. AfghanEB

    WebUI v0.315

    I can access the WebUI through Mozilla FireFox, but is the display supposed to stay static until it's reloaded? The settings in the WebUI options to have the GUI updated every 3000 ms (or any value that I've tested so far) doesn't seem to work for me... or maybe I'm missing something here.
  12. Okay, I think I found a bug with the preferences in beta 464. It seems like there's a conflict between "Show current speed in the title bar" (General) and "Append .!ut to incomplete files" (Downloads) because enabling the second option seems to enable the first. On that note, disabling the first option also seems to disable the second option. I've noticed this behavior on two different systems.
  13. I just tried out µTorrent v1.5.1 Beta 462 and it looks as though the UPnP feature does work with my Linksys WRT54GX4 router. I enabled the setting to randomize the port each time µTorrent is loaded and it hasn't given me any problems through multiple test runs. I suppose the UPnP log could use some clean-up but the functionality is there. UPDATE: After leaving the program running for an extended period of time, the log indicates repeated UPnP mapping attempts every 10 minutes. Is this normal? [3:33:45] UPnP: Mapped port 25179 -> 192.168.1.101:25179 [3:43:46] UPnP: Port 25179 is already mapped. Not re-mapping. [3:53:47] UPnP: Port 25179 is already mapped. Not re-mapping. [4:03:48] UPnP: Port 25179 is already mapped. Not re-mapping.
  14. --- 2006-04-28: Version 1.5.1 (build 453) - Feature: Add a way to make µt startup in bosskey mode Maybe I'm just missing something here, but can anyone explain how this option is enabled? I'm using v1.5.1 Beta Build 160 and can't seem to find any mention of that in the preferences (including the advanced options).