Menu

#158 Local network IPs like 192.168.0.0 arent filtered

closed-invalid
nobody
None
5
2005-11-29
2005-11-09
krasnoj
No

Local not routable adressspaces aren't filtered and
lock download slots. Please make a filter for all
protokolls, where local adresses get filtered.

Discussion

  • Markus Kern

    Markus Kern - 2005-11-25

    Logged In: YES
    user_id=552604

    They aren't filtered where? How do they lock download slots?

    Please describe the symptoms of your specific problem
    without making guesses about the cause.

     
  • krasnoj

    krasnoj - 2005-11-29

    Logged In: YES
    user_id=1356443

    I added a screenshot. There you can see that I use Apollon
    as frontend and my problem.

    In Apollon under the download names there are the IPs from
    the persons I download. But the strange thing is that I have
    persons with the local IP 192.168.*.* in it and I'm sure
    that I am sure that I am the only running computer in my
    local network and I know, that Kazaa for windows has filter
    for local adresses. The 192.168.*.* is local and not
    routable and so it is senseless to try download from it.

    There is a limit for maximum connections and it seems that
    this local IPs also count as connection. gift makes only new
    connection for this file, after I delete this 192.168.*.*
    Ips. Everything clear now?

     
  • krasnoj

    krasnoj - 2005-11-29

    Logged In: YES
    user_id=1356443

    It seems like the upload of the screenshot was not possible:
    Here you find a link to it:
    <http://homepage.uibk.ac.at/~csae8252/screenshot1.png>

     
  • Nobody/Anonymous

    Logged In: NO

    Dude, you are seeing this because the hosts are NAT'd. They are reporting those
    ip's which most likely on their router are forwarding the correct port to the
    correct internal address. This is completely normal behavior. -Julian

     
  • Markus Kern

    Markus Kern - 2005-11-29
    • status: open --> closed-invalid
     
  • Markus Kern

    Markus Kern - 2005-11-29

    Logged In: YES
    user_id=552604

    Your screenshot shows IPs from Gnutella. The user are
    firewalled but are contacted using push requests involving
    the GUID which is shown afte the IP. This is normal
    behaviour and there is not bug here.

     
  • krasnoj

    krasnoj - 2005-11-29

    Logged In: YES
    user_id=1356443

    My problem with it is, that this NAT / Firewall stuff never
    works. If I see this 192.168.* I can be sure that there
    stands "awaiting connection", "timeout" or something
    simillar but never ever there is a file download. Cause of
    this I want to filter this IP range.

    I am not sure about the protocoll but AFAIK should a NAT
    rewrite the source IP Adress in the IP Header. Does the
    Gnutella protocoll transmit the IP a second time? This would
    be the only case I can think about that this could be
    happen, in all other cases the 192.168.* should be replaced
    with the public IP, except that the NAT is kaputt.

    If it is a firewall problem than gifT should use a filter,
    that automatically blocks all Ips that were not reachable.

    If it is a NAT Problem, than it should allow to filter local
    IPs. I think it is a NAT problem. And "kazaa light" allows
    to filter local IPs so I think this is a usefull feature.

     

Log in to post a comment.