Créer un compteSe connecter

Recherches récentes

Aucune recherche récente

Options de recherche

Disponible uniquement lorsque vous êtes connecté.
pouet.chapril.org est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Chapril https://www.chapril.org est un projet de l'April https://www.april.org

Administré par :

Statistiques du serveur :

1,1K
comptes actifs

pouet.chapril.org: À proposAnnuaire des profilsPolitique de confidentialité

Mastodon: À proposTélécharger l’applicationRaccourcis clavierVoir le code sourcev4.3.7

#gateway

2 messages2 participants0 message aujourd’hui
Public *
Dendrobatus Azureus

My ISP gave me an interesting scare a couple of minutes ago. As you know if you do not want to pay them for a permanent IPv4 address, which I consider obsolete networking, they remotely reboot your gateway device and assign it a random IP out of one of their IPv4 pools.

This time it didn't take the usual long 30 to 90 Seconds to reboot the device and transfer credentials to obtain the new IP.
The Gateway got in an infinite loop somewhere and I had to Power it off, then had to wait 90 seconds to power cycle it before it took 180 seconds for the device to finally get the new IP.

Someone screwed up the login sequences for the xDSL devices of which the hashtag is in the toot and now we as the paying customer again have to pay for it in wasted time.

Luckily this power cycling off xDSL devices occurs only once in 6 weeks and usually I do not use the internet at that point in time.

In case you are wondering my Gateway uses obsolete technology, is forcibly assigned by the ISP and it's also cursed with a extremely low transfer speed.

I just included a speedtest after first draft of this toot

As you can see the speeds here are so low the connection is virtually unusable for anything where you have to move a big bites of data. They still manage to extort more than USD 30 a month for this connection

#xDSL#ISP#Services
Public
adingbatponder

#Settings in #reticulum #meshchat #reticulummeshchat #rns for #lora #radio #mesh Always set your stationary / radio #rnode #rnodes to be #gateway nodes (#interfaces) for effective #routing in your #mesh. See Sect 6.14 of rns #reticumlumnetworkstack manual
reticulum.network/manual/Retic
(and of course always also as #transport node else message packets from other nodes won't spread) Set the settings in the #configuration file or #update the #meshchat program now & set to gateway in the settings menu.

image of relevant part of rns manual: the default mode is full. In this mode, all discovery, meshing and transport functionality is activated. • The gateway mode (or shorthand gw) also has all discovery, meshing and transport functionality available, but will additionally try to discover unknown paths on behalf of other nodes residing on the gateway interface. If Reticulum receives a path request for an unknown destination, from a node on a gateway interface, it will try to discover this path via all other active interfaces, and forward the discovered path to the requestor if one is found. If you want to allow other nodes to widely resolve paths or connect to a network via an interface, it might be useful to put it in this mode. By creating a chain of gateway interfaces, other nodes will be able to immediately discover paths to any destination along the chain. Please note! It is the interface facing the clients that must be put into gateway mode for this to work, not the interface facing the wider network (for this, the boundary mode can be useful, though)
ExplorerFlux en direct
À propos