![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Search | Today's Posts | Mark Forums Read |
General Discussion For anything which doesn't fit somewhere else (for PHEX users) |
![]() |
| LinkBack | Thread Tools | Display Modes |
|
| ||||
![]() Could you add the headers being sent?
__________________ ![]() -> 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. |
| |||
![]() arne, i have the headers written to a binary file in disk for experimental parsing. where do i post or upload that? can u name any site where it could be uploaded. however, i think, this is the problem that i am facing. when i get connected to the phex ultrapeer which is also connected to other clients and ultrapeers, before it sends the pong message, i receive a set of query messages. i parsed the headers and found that message type is 0x80, and hence it must be the query message. this was not always the case and the flaw was in my experimental code, i think. but one thing that i would like to bring to ur notice is that, phex is sending me more than 20 pongs for a single ping. is it a good idea to send so much of pongs. { i mean going by the spec, it should return 10 pongs} and the messages are broken. that is receive the header and then the pong message. i think, my problem is solved now, and i could sucessfully parse query and pong messages. the next thing, that i have to look for is query hit, bye and push. thanks a lot.... |
| |||
![]() You should get one pong for the node itself and max 6 additional pongs from the pong cache for each additional hop your ping message would travel. So max. 7 pongs each with the MsgId of the Pong you send. Otherwise these pongs are likely not originating from Phex, just routed through Phex. Of course there could also be a bug somewhere, but that would require more details from you. Message dumps and if possible test cases... |
![]() |
Thread Tools | |
Display Modes | |
| |