Idk

index.md

@@ -109,6 +109,7 @@ _(Alphabetically sorted, so the ordering might seem a bit strange.)_
 - [802.1X & EAP](/networking/dot1x-eap/)
 - [FS FSOS Switches](/networking/fs-fsos-switches/)
 - [General](/networking/general/)
+- [HPE/Aruba General](/networking/hpe-aruba-general/)
 - [IPv4 Theory](/networking/ipv4/)
 - [IPv6 Theory](/networking/ipv6/)
 - [Juniper EX3300 Fan Mod](/networking/juniper-ex3300-fanmod/)

networking/cisco-general.md

@@ -123,6 +123,29 @@ General Cisco networking equipment stuff.
 - An IEEE protocol (defined in IEEE 802.1AB) for interchanging device information to neighbor devices.
 - **TODO** LLDP and LLDP-MED
 
+## Other Features
+
+### ACL Based Forwarding (ABF)
+
+- Supported by ASR9000 (certain line cards) (Cisco IOS XR).
+- Basically policy-based ruting (PBR), implemented using ACLs.
+- Supports ingress ACLs only.
+- Nexthops:
+    - Up to 3 alternative nexthops can be specified for a rule using the `nexthop<n> [vrf <vrf>] [{ipv4|ipv6} <nexthop-ip>]` clause.
+    - If multiple nexthops are specified then the first one with an up interface with a connected subnet will be used.
+    - If none of the nexthops are "up" then the normal default route is used instead.
+    - If the `default` clause is specified then the nexthops will only be used in place of a default route and not if any specific routes in the routing table match.
+- VRFs:
+    - Egress VRFs can be specified as part of the nexthop clause.
+    - If no IP address is specified for the nexthop then the routing table of the VRF is used.
+    - If no VRF is specified for a nexthop clause then the default VRF is used.
+- If traffic should be dropped if the first next hops are down, then create a `DROP_VRF` VRF with a null default route and use that as the last nexthop.
+- **TODO** If all nexthops are down, does ut use the normal routing table or specifically the normal default route? Something about null route not working mentioned.
+- An example usage for ABFs is to route RFC 1918 networks heading through a GW toward the Internet into a NAT VRF or separate NAT router.
+- Examples:
+    - Some rule: `10 permit ipv4 any 100.100.100.0/24 nexthop1 VRF RED ipv4 1.1.1.1 nexthop2 VRF BLUE ipv4 2.2.2.2 nexthop3 ipv4 3.3.3.3`
+    - Show that the ABF id programmed correctly in HW: `show access-lists ipv4 abf-1 hardware ingress location 0/1/cpu0`
+
 ## Miscellanea
 
 ### Version and Image String Notations

networking/hpe-aruba-general.md

@@ -0,0 +1,17 @@
+---
+title: HPE/Aruba General
+breadcrumbs:
+- title: Network
+---
+{% include header.md %}
+
+General HPE/Aruba networking equipment stuff.
+
+## Technologies
+
+### Virtual Switching Framework (VSF)
+
+- For switch stacking, makes multiple physical switches operate as one logical with a single config file.
+- Uses normal Ethernet ports (or a LAG/trunk) between the physical switches.
+
+{% include footer.md %}

networking/ipv6.md

@@ -51,7 +51,7 @@ breadcrumbs:
     - While still needed for the full internet, internal networks may be IPv6-only.
 - Larger address space.
     - Simpler and more structured address plans.
-    - All subnets are /64 regardless of the number of hosts/interfaces (excluding e.g. /127 linknets).
+    - All subnets are (shoul be) /64 regardless of the number of hosts/interfaces (excluding e.g. /127 linknets).
     - Extra information can be embedded in the address.
 - No need for NAT.
     - Restores end-to-end princible.
@@ -407,10 +407,11 @@ breadcrumbs:
     - Find out how much space you need before requesting it.
     - If you didn't get enough, ask for more.
 - All subnets should be /64.
-    - Event point-to-point links.
-    - Does not focus on address conservation.
-    - Does not require any VLSM.
-    - Required by SLAAC and many other mechanisms and protocols.
+    - Convention where all networks are of the same length, making "/64" synonymous with "network" and makes all networks addressable with exactly 64 bits or 16 hexadecimals (ignoring zero compression).
+    - Address conservation should not be taken into account, there's enough /64 prefixes.
+    - Avoids pointless VLSM, a thing of the past.
+    - Required by e.g. SLAAC and unicast-prefix-based IPv6 multicast addresses (RFC 3306).
+    - Even for point-to-point links (/127) and loopbacks (/128), such that uplinks always use ":0", downlinks always use ":1" and loopbacks always use in ":0".
 - Topology aggregation VS policy/service aggregation.
 - Suggested information to include in the prefix:
     - Region.

virt-cont/docker.md

@@ -41,10 +41,11 @@ Main config: `/etc/docker/daemon.json`
 1. (Optional) Change the logging options (JSON file driver):
     - It defaults to the JSON file driver with a single file of unlimited size.
     - Configured globally in the main config.
-    - Set the driver (explicitly): `"log-driver": "json-file"`
-    - Set the max file size: `"log-opts": {"max-size": "10m"}`
-    - Set the max number of files (for log rotation): `"log-opts": {"max-file": "5"}`
-    - Set the compression for rotated files: `"log-opts": {"compress": "enabled"}`
+    - Set the driver (explicitly): `"log-driver": "json-file"` (default `local`)
+    - Set log options in `"log-opts": {}`:
+        - Set the max number of files (for log rotation): `"max-file": "5"` (default 5)
+        - Set the max file size: `"max-size": "10m"` (default 20m)
+        - Set the compression for rotated files: `"compress": "true"` (default true)
 1. (Recommended) Disable the userland proxy:
     - It's no longer recommended to keep this enabled, future Docker versions will brobably disable it by default.
     - Disabling it _may_ break your published IPv6 ports, so you may want to test that.