From 64b1fdffd18748917d237678877a4ef93102f7a0 Mon Sep 17 00:00:00 2001 From: Marty Sluijtman Date: Thu, 27 Jul 2023 02:48:45 +0200 Subject: [PATCH] typos --- content/rambles/i2p-on-nixos.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/rambles/i2p-on-nixos.md b/content/rambles/i2p-on-nixos.md index b20373e..4cadc4f 100644 --- a/content/rambles/i2p-on-nixos.md +++ b/content/rambles/i2p-on-nixos.md @@ -63,7 +63,7 @@ My initial goal was to be able to search the i2p net. To that end, the following will suffice. ```nix ... - # Exposing the nessecary ports in order to intefact with i2p from outside the container + # Exposing the nessecary ports in order to interact with i2p from outside the container networking.firewall.allowedTCPPorts = [ 7070 # default web interface port 4447 # default socks proxy port @@ -88,8 +88,9 @@ else than an HTTP connection to interact with i2p. Since I wanted to see what kinds of _linux distros_ the i2p network has to offer, I also enabled `services.i2pd.proto.sam` and added the corresponding -default port in order to get [XD](https://xd-torrent.github.io/) (which can be -found in the Nix repo) to work: +default port to the container's firewall in order to get +[XD](https://xd-torrent.github.io/) (which can be found in the Nix repo) to +behave properly: ```nix ... @@ -106,7 +107,7 @@ found in the Nix repo) to work: system.stateVersion = "23.05"; # If you don't add a state version, nix will complain at every rebuild - # Exposing the nessecary ports in order to intefact with i2p from outside the container + # Exposing the nessecary ports in order to interact with i2p from outside the container networking.firewall.allowedTCPPorts = [ 7656 # default sam port 7070 # default web interface port