Idk

audio/behringer-x32.md

@@ -121,6 +121,6 @@ breadcrumbs:
 
 - On the Compact version, select two input layers at the same time to show the first on the left channel strips and the second on the right channel strips.
 - Enable color for the RTA.
-- Bring a 5GHz wireless router to set up your own out-of-band network for remote control. Consider hooking the WAN port up to the local network for internet access, if required. Also consider connecting the tablet using an RJ45 Ethernet adapter to avoid relying on WLAN.
+- Bring a 5GHz wireless router to set up your own out-of-band network for remote control. Consider hooking the WAN port up to the local network for internet access, if required. Also consider connecting the tablet using an RJ45 Ethernet adapter to avoid relying on unreliable WLAN.
 
 {% include footer.md %}

automation/ansible.md

@@ -9,9 +9,9 @@ breadcrumbs:
 
 - Specify SSH password: `--ask-pass`
 - Specify sudo password: `--ask-become-pass`
-- Specify username: `--username=<username>`
+- Specify username: `-u <username>`
 - Specify SSH key: `--private-key=<key>` (use `/dev/null` to explicitly avoid SSH keys)
-- Hide unchanged/skipped tasks: `export ANSIBLE_DISPLAY_SKIPPED_HOSTS=false; export ANSIBLE_DISPLAY_OK_HOSTS=false`
+- Hide unchanged/skipped tasks (add to your `.bashrc` or something): `export ANSIBLE_DISPLAY_SKIPPED_HOSTS=false; export ANSIBLE_DISPLAY_OK_HOSTS=false`
 
 ### Ad Hoc
 

cloud/azure.md

@@ -211,6 +211,7 @@ This sets up a simple VM (called `Yolo`) in its own resource group and its own r
     - *NAT Gateway* is not supported.
     - Virtual nodes are not supported.
     - Windows nodes pools are not supported.
+    - Reverse FQDNs for single public IPv6 addresses are not supported.
 - IPv6 in the Kubenet network model:
     - More info: [Microsoft Learn: Use dual-stack Kubenet networking in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/configure-Kubenet-dual-stack)
     - Dual-stack support must be specified during cluster creation, using argument `--ip-families=ipv4,ipv6`. This will cause all nodes and pods to automatically get IPv6 too.

networking/bgp.md

@@ -180,7 +180,7 @@ The path selection algorithm is used to select a single best path for a prefix.
 ## Best Practices
 
 - Announced prefix lengths (max /24 and /48): Generally, use a maximum length of 24 for IPv4 and 48 for IPv6, due to longer prefixes being commonly filtered. See [Visibility of IPv4 and IPv6 Prefix Lengths in 2019 (RIPE)](https://labs.ripe.net/Members/stephen_strowes/visibility-of-prefix-lengths-in-ipv4-and-ipv6).
-- IRR and RPKI: Add `route(6)` objects (for IRR) and ROAs (for RPKI) for all prefixes, both to avoid having your prefixes hijacked and to reduce the risk of getting filtered.
+- IRR and RPKI: Add `route(6)` objects (IRR) and ROAs (RPKI) for all prefixes, both to avoid having your prefixes hijacked and to reduce the risk of getting filtered.
 - Explicit import & export policies: Always explicitly define the input and output policies to avoid route leakage. Certain routers defaults to announcing everything if no policy is defined, but RFC 8212 defines a safe default policy of filtering all routes if no policy is explicitly defined.
 - Enable large communities: 2-byte communities are outdated, enable 12-byte communities to allow for more advanced policies and to keep up up to date with 4-byte ASNs. See RFCs 8092 and 8195.
 - Administrative shutdown message: When administratively shutting down a session (due to maintenance or something), set a message to explain why to the other peer. Peers should log received shutdown messages. See RFC 9003, which adds support for this free-form 128-byte UTF-8 message in the BGP notification message.

networking/juniper-hardware.md

@@ -1,17 +0,0 @@
----
-title: Juniper Hardware
-breadcrumbs:
-- title: Network
----
-{% include header.md %}
-
-### Related Pages
-{:.no_toc}
-
-- [Juniper Junos OS](/network/juniper-junos/)
-
-## EX3300
-
-- [Fan Mod](/guides/network/juniper-ex3300-fanmod/)
-
-{% include footer.md %}

networking/juniper-junos.md

@@ -426,10 +426,10 @@ Wait for the "The operating system has halted." text before pulling the power, s
 
 ## Tasks
 
-### Reset Root Password
+### Reset Config or Root Password
 
 1. Power on the device and prepare for the next step.
-1. Press space quickly as the "Hit \[Enter\] to boot immediately, or space bar for command prompt." message is shown (right before the kernel is loaded). You should immediately enter a `loader>` prompt.
+1. Wait for the "Hit \[Enter\] to boot immediately, or space bar for command prompt." message to be shown and then press space. You should immediately enter a prompt (typically `loader>`).
 1. Run `boot -s` to boot into single-user mode.
 1. When prompted for a shell, enter `recovery`.
 1. Wait for the device to fully boot.
@@ -458,6 +458,7 @@ This should work in most cases and is the most streamlined version, but may not
 
 1. (Info) For virtualized boxes like EX4600 and QFX5100, skip the `request system snapshot` parts as these boxes are built differently wrt. Junos.
 1. Cleanup old files: `request system storage cleanup`
+    - Do this *before* mounting the USB or downloading the files, as the upgrade files may get wiped.
 1. Make sure the alternate partition contains a working copy of the current version: See [Validate the Partitions](#validate-the-partitions).
 1. If downloading from a remote location:
     1. Get the file: `file copy <remote-url> /var/tmp/`
@@ -480,7 +481,7 @@ This should work in most cases and is the most streamlined version, but may not
     - For virtualized devices, add `force-host` to upgrade the host too.
     - If the date is significantly wrong on the device and NTP isn't used/synced, set it manually with `set date <YYYYMMDDhhmm>` first so validation doesn't fail.
     - It may produce some insignificant errors in the process (commands not found etc.).
-1. See [Validate the Partitions](#validate-the-partitions).
+1. See [Validate the Partitions](#validate-the-partitions) to copy the upgraded partition to the other partition.
 
 #### From the Loader
 
@@ -491,7 +492,7 @@ If the normal method did not work, try this instead.
 1. Reboot the device and press space at the right time to enter the loader.
     - The message to wait for should look like this: `Hit [Enter] to boot immediately, or space bar for command prompt.`
 1. Format and flash: `install --format file:///jinstall-whatever.tgz` (with correct name, no `/var/tmp/`)
-1. See [Validate the Partitions](#validate-the-partitions).
+1. See [Validate the Partitions](#validate-the-partitions) to copy the upgraded partition to the other partition.
 
 #### Validate the Partitions
 
@@ -500,14 +501,14 @@ Do this before as a check and after to make sure the new image is working and co
 1. Log into the CLI.
 1. Verify that the system is booted from the active partition of the internal media: `show system storage partitions` (should show `Currently booted from: active`)
 1. Verify that the current Junos version for the *primary* partition is correct: `show system snapshot media internal`
-1. Copy to the alternate root partition (may take several minutes): `request system snapshot slice alternate`
+1. Copy to the alternate root partition, so both have the same version (may take several minutes): `request system snapshot slice alternate`
 1. Verify that the primary and backup partitions have the same Junos version: `show system snapshot media internal`
     - If the command fails, wait a bit and try again. The copy may still be happening in the background.
 1. (Info) To boot from the alternative partition: `request system reboot slice alternate media internal`
 
 #### ISSU and NSSU
 
-Just info, no instructions here yet.
+Just info, no instructions here.
 
 - ISSU and NSSU may be used for upgrade without downtime, if the hardware supports it.
 - If using redundant hardware (multiple REs), ISSU may be use for upgrades without downtime. It may blow up. One RE is upgraded first, then state is transferred to it. Normal upgrade with reboot is more reliable if short downtime is acceptable.

networking/ptp.md

@@ -166,7 +166,7 @@ breadcrumbs:
 - Does not allow non-PTP bridges in the path.
 - Implicitly supports P2P TCs (not configurable).
 
-#### Telecom (ITU-T G.82751)
+#### Telecom (ITU-T G.8275.1)
 
 - Used for telecom and mobile backhaul.
 

networking/vyos.md

@@ -19,9 +19,12 @@ A Debian-based router OS, forked from Vyatta. Junos-like CLI.
 
 See [Installation (VyOS)](https://docs.vyos.io/en/latest/install.html).
 
-1. For physical instances, consider disabling Intel Hyper-Threading (it does little for memory-intensive applications like packet routing).
-1. If running as VM inside a hypervisor like Proxmox, disable memory ballooning/memory sharing.
-    - VyOS does not use swapping so accidental overprovisioning that could starve the VyOS VM could cause errors.
+1. For bare-metal:
+    - Consider disabling Intel Hyper-Threading. It does little for memory-intensive applications like packet routing.
+1. For PVE/QEMU VM:
+    - Set the disk size to e.g. 10GB. It will mostly only be used for 500MB VyOS images, logs, containers and other things you might have added.
+    - Disable memory ballooning/memory sharing. VyOS does not use swapping so accidental overprovisioning that could starve the VyOS VM could cause errors.
+    - Enable the QEMU agent option in PVE. VyOS comes with the agent installed.
 1. Download the latest rolling release (free) or LTS release (paid) ISO.
 1. Burn and boot from it (it's a live image).
 1. Log in using user `vyos` and password `vyos`.

swe/git.md

@@ -169,6 +169,9 @@ File: `~/.gitconfig`
 Note: Avoid quotation marks around values.
 
 ```ini
+# https://wiki.hon.one/swe/git/
+# https://github.com/HON95/configs/blob/master/git/config
+
 [user]
         name = <full_name>
         email = <email_addr>