Feature request: boycotting IP ranges Thanks for the reply. You wrote:
>those IP Ranges 192.168.0.xxx are also used when running a
>firewall. That means it is a security feature. the force IP is not
>usefull in cases of a changing external IP address, like for dial-
>ups and even most DSL/Cable users.
>users would have to enter the IP everytime they run limewire.
I guess you're right, it woudn't make sense for those with dynamic IP addresses.
>also you can get files from the LAN IPs with PUSH (not if you
>have a firewall yourself)...
I do have a firewall, so this isn't an options for me.
>I have a LAN and a firewall and I can connect and
>download/upload.
I am curious to know, have you EVER managed to download from an IP address 192.168.xxx.xxx? I haven't. In fact I suspect that those addresses generate download requests to nonexistent computers inside my private network. Many files are tagged with those IP addresses, and invariably a download request from one of those addresses will fail.
I guess what I really want is a feature that hides any search results associated with those private-network addresses. For me, being behind a firewall, those addresses will never work.
-Alex |