This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
| { | |
| "name": "Discord RTC Regions", | |
| "description": "allowlist for all Discord voice regions", | |
| "rules": [ | |
| { | |
| "action": "allow", | |
| "process": "/Applications/Discord.app/Contents/MacOS/Discord", | |
| "remote-addresses": "5.200.3.71,5.200.3.100,5.200.3.119,5.200.6.179,5.200.14.132,5.200.14.138,5.200.14.172,5.200.14.186,5.200.14.196,5.200.14.231,5.200.14.243,31.204.133.6,31.204.133.9,31.204.133.14,31.204.133.16,31.204.133.22,31.204.133.27,31.204.133.30,31.204.133.31,31.204.133.37,31.204.133.43,31.204.133.44,31.204.133.48,31.204.133.49,31.204.133.52,31.204.133.58,31.204.133.74,31.204.133.76,31.204.133.80,31.204.133.81,31.204.133.82,31.204.133.87,31.204.133.95,31.204.133.97,31.204.133.101,31.204.133.102,31.204.133.103,31.204.133.104,31.204.133.105,31.204.134.11,31.204.134.16,31.204.134.19,31.204.134.26,31.204.134.28,31.204.134.30,31.204.134.32,31.204.134.34,31.204.134.36,31.204.134.40,31.204.134.50,31.204.134.54,31.204.134.58,31.204.134.61,31.204.134.63,31.204.134.64,31.204.134.69,31.204.134.72,31.2 |
| ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key | |
| # Don't add passphrase | |
| openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub | |
| cat jwtRS256.key | |
| cat jwtRS256.key.pub |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000