![]() |
| | |||||||
| Register | FAQ | Members List | Calendar | Arcade | Search | Today's Posts | Mark Forums Read |
| General Discussion For anything which doesn't fit somewhere else |
|
Welcome to Gnutella Forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. Once registered but before posting, members MUST READ the FORUM RULES (click here) and LimeWire/FrostWire users should include System details - help us to help you (click on blue link) in their posts if their problem relates to using the program. Whilst forum helpers are happy to help where they can, without these system details your post might be ignored. And wise to read How to create a New Thread Thank you |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Im capturing Gnutella network traffic sent to my laptop using Wireshark Network Analyzer (Seemed like a fun thing to do on a Friday night while drinking a beer) ![]() I can see the incoming searches in the "Search Monitor" in plain text, however when I try to locate those packets in the network analyzer, I cant identify them. I think they are UDP? I know the Gnutella syn packet headers are in plain text. How can I identify the incoming search packets? Is there a way that they are human readable? Dave |
| |||
| Well..that did work. Could you elaborate a little on what that did to make incoming data plain text at the NIC? Also...in the Search Monitor,...is the "routed from" ip address the actual host conducting the seacrh, or just the last hop it took? I dont see any additional IP addresses in the data. |
| |||
| Quote:
SourceForge.net Repository - [phex] View of /phex/trunk/docs/Gnutella/proposals/GNET compression.txt It only shows the IP of the last hop. The IP of the host conducting the search is not part of the standard query protocol. |
| |||
| I was under the impression that each time a search term query took a hop, it would say something like "who has this search...tell 192.168.1.1 (original host)" If the searching host ip address isnt sent along with the data, how does the host with the matching files three hops away know who is asking? |
| ||||
| The results gets sent back along the chain. That's why it suffices to get the connection to your Ultrapeers through your firewalls to be able to search. Sadly it doesn't work as well for downloads (passing them along the chain would kill the network - instead a non-firewalled third party is used to route the downloads (Push Proxy). This is different for OOB results (out of band) as far as I know.
__________________ -> put this banner into your own signature! <- -- Erst im Spiel lebt der Mensch. Nur ludantaj homoj vivas. GnuFU.net - Gnutella For Users Draketo.de - Shortstories, Poems, Music and strange Ideas. |
| Thread Tools | |
| Display Modes | |
| |