Bitcoin Forum
December 10, 2016, 04:47:59 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Sender\Receiver address info backward in Version message?  (Read 739 times)
Atheros
Sr. Member
****
Offline Offline

Activity: 249



View Profile WWW
July 26, 2011, 03:35:02 AM
 #1

I'm interested in some clarification. The documentation suggests that within a Version message, the Sender address info goes first, then the Recipient. But when I look at a packet, it is flipped as I show in the screenshot. (My external IP is in yellow, and is followed by the sender's IP).
Also, I underlined in green the port which is 8333 in both cases. Why is it 8333 in both cases instead of 62036 which Wireshark says is the port on the sender's end?
Thank You!

From the documentation on the Wiki:

Version message:
 9C 7C 00 00                                                                   - 31900 (version 0.3.19)
 01 00 00 00 00 00 00 00                                                       - 1 (NODE_NETWORK services)
 E6 15 10 4D 00 00 00 00                                                       - Mon Dec 20 21:50:14 EST 2010
 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 01 DA F6 - Sender address info - see Network Address
 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF 0A 00 00 02 20 8D - Recipient address info - see Network Address
 DD 9D 20 2C 3A B4 57 13                                                       - Node random unique ID
 00                                                                            - "" sub-version string (string is 0 bytes long)
 55 81 01 00                                                                   - Last block sending node has is block #98645


From my own connection:


BM-GteJMPqvHRUdUHHa1u7dtYnfDaH5ogeY
Bitmessage.org - Decentralized, trustless, encrypted, authenticated messaging protocol and client.
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
1481388479
Hero Member
*
Offline Offline

Posts: 1481388479

View Profile Personal Message (Offline)

Ignore
1481388479
Reply with quote  #2

1481388479
Report to moderator
theymos
Administrator
Legendary
*
expert
Offline Offline

Activity: 2506


View Profile
July 26, 2011, 04:34:14 AM
 #2

I'm pretty sure the wiki is wrong here. The code says:
Code:
PushMessage("version", VERSION, nLocalServices, nTime, addrYou, addrMe,
                    nLocalHostNonce, string(pszSubVer), nBestHeight);
addrYou comes first.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Atheros
Sr. Member
****
Offline Offline

Activity: 249



View Profile WWW
July 26, 2011, 04:53:49 AM
 #3

Okay, Thank You.

I'll update the wiki.

BM-GteJMPqvHRUdUHHa1u7dtYnfDaH5ogeY
Bitmessage.org - Decentralized, trustless, encrypted, authenticated messaging protocol and client.
JoelKatz
Legendary
*
Offline Offline

Activity: 1386


Democracy is vulnerable to a 51% attack.


View Profile WWW
July 26, 2011, 04:58:12 AM
 #4

Also, I underlined in green the port which is 8333 in both cases. Why is it 8333 in both cases instead of 62036 which Wireshark says is the port on the sender's end?
Each side already knows the port in use for this particular connection. The port they are exchanging is the port on which they accept inbound connections. That will tell the side that accepted the connection how other nodes can reach the node that connected to it.

I am an employee of Ripple.
1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!