Closed LetDevDev closed 6 years ago
Position 1 and 2 will hold the Time to live. This must be between 0 and 255. This field MUST be decremented every time any node (Client or Router) repeats the message. Should it reach 0, it MUST be discarded.
Position 3 and 4 will hold the protocol. This is mainly informational, and its use is largely up to the higher level implementors. The exception is for ICMP and DHCP, which will later have definitions
Positions 5 to 10 contain the source address, this is the address that should be replied too.
Positions 11 to 16 contain the destination address, this is the address that should be routed for
Modem Driver contains the implementation of this. As this needs to be done on an interface level (And may not actually happen if the interface is particularly high in packet-size) I consider this complete.
Investigations have shown negligible performance and size benefits for binary manipulation of this header. Instead, a single string will be used, and the fields will be encoded and decoded as HEX. string.sub will be the driving force for this
TTPPSSSSSSDDDDDD T: Time to live P: Protocol S: Source GERT address D: Dest GERT address