RNS Logo

rns.recipes

◈ 9ce92808be498e9e05590ff27cbfdfe4
https://rns.recipes/forum/general/important-security-notice-media-conversion-in-rngit-and-nomadnet

Clearing up confusion about Reticulum MTU and MDU

Question

Started by welo ·

#1

I've been looking through the api recently and I can't get a grip on these two values.

 

My basic understanding is that all reticulum packets are limited to 500 byte and that while transmitting say link packets, you have to be within those 500 bytes + overhead from headers (both reticulum and link specific), but links have this function associated with them mdu discovery, which is strange because normal packets seem to have a static mdu (which makes sense to me, that's the 500 byte MDU - overhead). Does that mean that links can use packets bigger than 500 bytes? or is that mdu discovery just figuring out the possible minimal link packet overhead within the 500 byte limit that all packets have.

 

There's also mtu, which I've noticed more often when using rnstatus for example here's a little ctrl-c ctrl-v of my rnstatus on my backbone

BackboneInterface[Crouton's Lower Silesia Node/83.168.89.108:4242]
    Source    : Auto-connect via <e96dc468e835956398a7f99be0cfc999>
    Status    : Up, gravity 15
    Mode      : Gateway
    Rate      : 5.00 Mbps, MTU 8192 <-------- this
    Flt. Hits : 47
    Traffic   : ↑492.40 MB  19.53 Kbps
                ↓255.28 MB  1.59 Kbps

 RNodeInterface[Rnode medium range]
    Status    : Up, gravity 25
    Mode      : Gateway
    Rate      : 1.30 kbps, MTU 508  <-------- this
    Noise Fl. : -115 dBm
    Intrfrnc. : -64 dBm 6m and 9s ago
    CPU temp  : 43°C
    Battery   : 100% (charged)
    Airtime   : 0.0% (15s), 3.25% (1h)
    Ch. Load  : 1.64% (15s), 4.67% (1h)
    Traffic   : ↑1.53 MB    0 bps
                ↓793 B      0 bps

 

I initially thought MTU was just block sizes for sending out of socket.sendall(data) (because sending each individual packet with a separate call from my limited python experience would cause a bottleneck on the python side due to having to call that function so often, so instead the implementation batches multiple reticulum packets and then sends it at once) but there's also a function to get link mtu, which is weird because I'd assume that all packet would be transparent to this value and not care about the underlying MTU, or are those two unrelated values things i'm conflating.

 

I've probably confused MTU and MDU at least once asking this question but hopefully someone can clear up my confusion here.

Zenith Admin
edited #2

MDU is the the MTU minus packet overhead, meaning the actual data you can carry

 

With the default 500 byte MTU FOr plain (unencrypted) packets thats 464 bytes, 383 for a encrypted packet to a destination, and 431 for a packet over the link

 

Links can carry packets bigger than 500 bytes. There is MTU discovery that happens on the link level which works by having the sender put the MTU of its outgoing interface into the link request

 

Transport nodes along the path will lower the MTU value if they don't support it and the destination sends the final value back in the link proof and both ends will use that MTU

 

 

Post a Reply

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Quote
Copied to clipboard