This fixed my KeyError: 'txdrp' problem:
pipx list
pipx uninstall-all
pipx install rns
pipx install lxmf
pipx install nomadnet
reboot
Started by Mark bc7291552be7a58f... ·
This fixed my KeyError: 'txdrp' problem:
pipx list
pipx uninstall-all
pipx install rns
pipx install lxmf
pipx install nomadnet
reboot
Mark, I am wondering, if I put RNS 1.5.4 on my server, will it still interoperate fine with devices running Sideband or MeshChat with RNS 1.4.2? I know that 1.5.0 began a shift in the way transport works, so I just want to make sure it would interoperate before beginning the transition.
There should be no interop problems, you can upgrade however is most practical. I will always note clearly if there are any backwards-incompatibility issues to be aware of clearly in the release notes.
Mark wrote:
There should be no interop problems, you can upgrade however is most practical. I will always note clearly if there are any backwards-incompatibility issues to be aware of clearly in the release notes.
Thank you!
Mark, to relax from all the AI and licence drama here is a little nitty kritty thing: When listing i2p peers with Fff0rnstatus -d i2pdf you get configuration hints like:
Fff0Configuration Entry: [[Discovered I2PInterface]] type = I2PInterface enabled = yes peers = hioyjs43a24ihdjhskpepct53veddb5g2am325t7dp73fu2e35gaf
Copying this into configuration gives an error, because peer must be defined with ending Fff0.b32.i2pf in the configuration as
Fff0peers = hioyjs43a24ihdjhskpepct53veddb5g2am325t7dp73fu2e35ga.b32.i2pf
Just a little hint from a user who struggeled a while with this.