#meshchatx — Public Fediverse posts

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

I seem to be seeing that the #ip #ipv4 addresses of some legit #reticulum #nodes are being included in some of the lists used by #suricata #IDS #intrustiondetectionsystem to #blacklist IP addresses, and so they might well end up blocked by your #firewall or #IPS #intrusionprotectionsystem
in particular e.g. database #CINS might be flagging mesh nodes
Please take steps for port 4242
#port4242 normally used by #rns #reticulum to not let bad data spoil the #mesh #nomadnet #meshchat #meshchatx

Dat was rap hersteld .. MeshChatX 4.8.0 had een probleem met nomadnet pagina's laden. Via lxmf contact gezocht en aangeven met logregel foutmelding en uur later docker opnieuw geladen .. opgelost 😃

https://meshchatx.com

#meshchatx #reticulum

Leuk al die #reticulum clients , maar dan heb je verschillende ID's .. das niet zo handig.
Nu #meshchatx in #docker draaiend en dan met #nginx ervoor als reverse proxy.
Alles in 1 client en via de browser op meerdere devices en maar 1 ID :-)
en dan kom ik weer een ander iets tegen relay chat (een soort irc)

Leuk al die #reticulum clients , maar dan heb je verschillende ID's .. das niet zo handig.
Nu #meshchatx in #docker draaiend en dan met #nginx ervoor als reverse proxy.
Alles in 1 client en via de browser op meerdere devices en maar 1 ID :-)
en dan kom ik weer een ander iets tegen relay chat (een soort irc)

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3

Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3

Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3

Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3

Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3

@reticulum I am seeing #meshchatx uses #LXST 0.4.6 but seems not to be in any repo. Any ideas where the LXST 0.4.6 source code is? (Am building #nixos derivation). Edit: code available via

pip download --no-deps lxst==0.4.6

unzip lxst-0.4.6-py3-none-any.whl -d lxst-0.4.6/

@reticulum I am seeing #meshchatx uses #LXST 0.4.6 but seems not to be in any repo. Any ideas where the LXST 0.4.6 source code is? (Am building #nixos derivation). Edit: code available via

pip download --no-deps lxst==0.4.6

unzip lxst-0.4.6-py3-none-any.whl -d lxst-0.4.6/

Has anyone got #lxst 0.4.6 source code? Seem not to be able to find it in a repo. (Used by #meshchatx ) #reticulum
Edit> solution

pip download --no-deps lxst==0.4.6

unzip lxst-0.4.6-py3-none-any.whl -d lxst-0.4.6/

thanks to @circfruit

Has anyone got #lxst 0.4.6 source code? Seem not to be able to find it in a repo. (Used by #meshchatx ) #reticulum
Edit> solution

pip download --no-deps lxst==0.4.6

unzip lxst-0.4.6-py3-none-any.whl -d lxst-0.4.6/

thanks to @circfruit