Cursed Silicons Wiki - Recent changes [en]

CGHMN-IP-Allocations

PurpleJillybeans — Fri, 01 May 2026 03:56:26 GMT

Member-Delegated (Sub-) Domains

@@ Line 361: / Line 361: @@
 |kirk.loganius.retro
 |100.96.9.3
 | -
 |}

User:Chromaryu

Snep — Wed, 29 Apr 2026 10:21:30 GMT

User account Chromaryu was created by Snep

Services people are running

Ch0ccyra1n — Tue, 28 Apr 2026 01:19:40 GMT

Proposed Services

@@ Line 134: / Line 134: @@
 |Raspberry Pi OS Lite
 |Nginx
-|Homepage for retro macintosh computers
+|Homepage and web directory for primarily for retro macintosh computers
+|
 |-
@@ Line 360: / Line 360: @@
 |Public email and webmail for retro macs
 |Most likely will use SquirrelMail for webmail
 |-
 |[[User:Ch0ccyra1n|ch0ccyra1n]]
@@ Line 384: / Line 366: @@
 |Personal website for [[User:Ch0ccyra1n|ch0ccyra1n]]
+|
 |-
 |someone?

CGHMN-IP-Allocations

Ch0ccyra1n — Mon, 27 Apr 2026 23:26:42 GMT

Member-Delegated (Sub-) Domains

← Older revision		Revision as of 16:26, 27 April 2026
Line 335:		Line 335:
	\|ch0ccyra1n		\|ch0ccyra1n
	\|oohay.retro		\|oohay.retro
			\|ns1.oohay.retro
			\|100.96.11.197
			\| -
			\|-
			\|ch0ccyra1n
			\|mac
	\|ns1.oohay.retro		\|ns1.oohay.retro
	\|100.96.11.197		\|100.96.11.197

How to Get Connected

Bredo — Sun, 26 Apr 2026 21:35:26 GMT

Add note about OpenWRT 25.12 as the minimum (due to apk transition)

← Older revision		Revision as of 14:35, 26 April 2026
Line 27:		Line 27:
	# Run the following commands on the router:		# Run the following commands on the router:
	## <code>ash setup-cghmn.sh install-pkgs</code>		## <code>ash setup-cghmn.sh install-pkgs</code>
			### If you run into issues at this step, please make sure you are on OpenWRT 25.12 or later - the setup script only supports version 25.12 and up.
	## Reboot the router, this step is necessary if you intend to use the web UI for any other configuration or see the status of the CGHMN connection, to make LuCI recognize WireGuard connections.		## Reboot the router, this step is necessary if you intend to use the web UI for any other configuration or see the status of the CGHMN connection, to make LuCI recognize WireGuard connections.
	## <code>ash setup-cghmn.sh init</code>		## <code>ash setup-cghmn.sh init</code>

Known Bugs

CursedSilicon — Wed, 22 Apr 2026 22:55:08 GMT

← Older revision		Revision as of 15:55, 22 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	== Just a scratchpad for "stuff that is known to not work and needs fixing" ==		=== Just a scratchpad for "stuff that is known to not work and needs fixing" ===

			===== PvPGN =====
			PvPGN, the BattleNet emulator on the network seems to error out when StarCraft clients running Mac OS X (PowerPC) connect with game client 1.16.1

	~~===== PvPGN =====~~		1.15.2 on Mac OS 9 works.

	~~PvPGN, the BattleNet emulator on the network seems to error out when StarCraft clients running Mac OS X (PowerPC) connect with game client 1.16.1. 1.15.2 on Mac OS 9 works.~~ Unsure if x86 Mac is also broken?		'''Unsure if x86 Mac is also broken?'''

Known Bugs

CursedSilicon — Wed, 22 Apr 2026 22:53:04 GMT

Created page with "== Just a scratchpad for "stuff that is known to not work and needs fixing" == ===== PvPGN ===== PvPGN, the BattleNet emulator on the network seems to error out when StarCraft clients running Mac OS X (PowerPC) connect with game client 1.16.1. 1.15.2 on Mac OS 9 works. Unsure if x86 Mac is also broken?"

New page

== Just a scratchpad for "stuff that is known to not work and needs fixing" ==

===== PvPGN =====

PvPGN, the BattleNet emulator on the network seems to error out when StarCraft clients running Mac OS X (PowerPC) connect with game client 1.16.1. 1.15.2 on Mac OS 9 works. Unsure if x86 Mac is also broken?

Services people are running

PurpleJillybeans — Mon, 13 Apr 2026 11:21:43 GMT

Game servers

← Older revision		Revision as of 04:21, 13 April 2026
(3 intermediate revisions by the same user not shown)
Line 95:		Line 95:
	\|OpenBSD 3.0		\|OpenBSD 3.0
	\|Artifact-RJS mod with custom maps. Info at [http://www.n8fq.retro/quakeworld www.n8fq.retro/quakeworld]		\|Artifact-RJS mod with custom maps. Info at [http://www.n8fq.retro/quakeworld www.n8fq.retro/quakeworld]
	\|-
	~~\|PurpleJillybeans~~
	~~\|master.n8fq.retro~~
	~~\|100.68.39.1~~
	~~\|QuakeSpy/GameSpy~~
	~~\|Debian Trixie~~
	~~\|Must specify manually for QuakeWorld and Quake 2. DNS override in place for Heretic II, Quake 3, and Doom 3.~~
	\|}		\|}
	'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''		'''NOTE: Some services are "patched" at DNS level. Other games (such as Halo) require connecting to a server via IP. Check the notes!'''
Line 199:		Line 192:
	\|nginx		\|nginx
	\|Random stuff		\|Random stuff
			\|
			\|-
			\|PurpleJillybeans
			\|http://weather.retro
			\|Debian Trixie
			\|Apache
			\|Worldwide weather conditions and forecasts
	\|		\|
	\|}		\|}
Line 374:		Line 374:
	\|-		\|-
	\|[[User:Ch0ccyra1n\|ch0ccyra1n]]		\|[[User:Ch0ccyra1n\|ch0ccyra1n]]
	\|oldgrounds.~~mac~~		\|oldgrounds.retro
	\|Other communications		\|Other communications
	\|Website for uploading Macromedia Flash (.swf) to play in the browser		\|Website for uploading Macromedia Flash (.swf) to play in the browser
Line 384:		Line 384:
	\|Personal website for [[User:Ch0ccyra1n\|ch0ccyra1n]]		\|Personal website for [[User:Ch0ccyra1n\|ch0ccyra1n]]
	\|		\|
	\|-
	~~\|PurpleJillybeans~~
	~~\|weather.retro~~
	~~\|Websites~~
	~~\|Worldwide weather conditions and forecasts~~
	~~\|PHP, Open-Meteo or AccuWeather API (could also use [https://api.met.no/ ''Meteorologisk Institutt's API''])~~
	\|-		\|-
	\|someone?		\|someone?

How to Get Connected

Bredo — Wed, 08 Apr 2026 11:11:17 GMT

Wireguard -> WireGuard

Services people are running

Ch0ccyra1n — Tue, 07 Apr 2026 21:28:07 GMT

Proposed Services

← Older revision		Revision as of 14:28, 7 April 2026
(One intermediate revision by the same user not shown)
Line 372:		Line 372:
	\|Forum for retro mac enthusiasts		\|Forum for retro mac enthusiasts
	\|Debating between PHPbb or Simple Machines. Either way I'd write a custom theme to make it aqua just like the other services (besides oldgrounds)		\|Debating between PHPbb or Simple Machines. Either way I'd write a custom theme to make it aqua just like the other services (besides oldgrounds)
	\|-
	~~\|[[User:Ch0ccyra1n\|ch0ccyra1n]]~~
	~~\|time.mac~~
	~~\|Time~~
	~~\|NTP server, synced to time.apple.com~~
	\|
	\|-		\|-
	\|[[User:Ch0ccyra1n\|ch0ccyra1n]]		\|[[User:Ch0ccyra1n\|ch0ccyra1n]]
Line 395:		Line 389:
	\|Websites		\|Websites
	\|Worldwide weather conditions and forecasts		\|Worldwide weather conditions and forecasts
	\|PHP, Open-Meteo or AccuWeather API		\|PHP, Open-Meteo or AccuWeather API (could also use [https://api.met.no/ ''Meteorologisk Institutt's API''])
			\|-
			\|someone?
			\|status.retro
			\|Other communications
			\|Status page to know if certain services are up
			\|
	\|}		\|}
	[[Category:Compu-Global-Hyper-Mega-Net]]		[[Category:Compu-Global-Hyper-Mega-Net]]

← Older revision		Revision as of 04:11, 8 April 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	[[Signup\|'''Let us know you'd like to connect!''']]		[[Signup\|'''Let us know you'd like to connect!''']]

	(We'll need information from you such as your ~~Wireguard~~ Pubkey to let you connect to the network)[[File:CGHMN.png\|thumb\|319x319px\|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]		(We'll need information from you such as your WireGuard Pubkey to let you connect to the network)[[File:CGHMN.png\|thumb\|319x319px\|Example CGHMN Router Setup using a GL-AR300M and basic network switch]]

	=== Hardware requirements ===		=== Hardware requirements ===
Line 13:		Line 13:
	*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''		*'''An Ethernet connection on your retro device(s) of choice, with a TCP/IP (v4) stack for now! TrumpetWinSock, Microsoft TCP/IP, whatever. It all works.'''

	* '''Something with the ability to run ~~Wireguard~~ and forward IPv4 packets at the minimum and, for any non-IP packets, <code>gretap</code> and <code>nftables</code>. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''		* '''Something with the ability to run WireGuard and forward IPv4 packets at the minimum and, for any non-IP packets, <code>gretap</code> and <code>nftables</code>. Personally we recommend something running OpenWRT, like the [https://www.gl-inet.com/products/gl-ar300m GL-AR300M] which we have successfully tested to work. We're currently working on a pre-built image for some select routers to make the setup easier for new members. A script to configure already existing OpenWRT instances can be found below.'''
	* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. <s>A basic script to set up a Linux machine as a router is posted below</s> (TODO!).		* Alternatively, you can also run the CGHMN routing on any standard Linux box which has at least one Ethernet port and either a second one or WiFi for internet connectivity. <s>A basic script to set up a Linux machine as a router is posted below</s> (TODO!).

Line 27:		Line 27:
	# Run the following commands on the router:		# Run the following commands on the router:
	## <code>ash setup-cghmn.sh install-pkgs</code>		## <code>ash setup-cghmn.sh install-pkgs</code>
	## Reboot the router, this step is necessary if you intend to use the web UI for any other configuration or see the status of the CGHMN connection, to make LuCI recognize ~~Wireguard~~ connections.		## Reboot the router, this step is necessary if you intend to use the web UI for any other configuration or see the status of the CGHMN connection, to make LuCI recognize WireGuard connections.
	## <code>ash setup-cghmn.sh init</code>		## <code>ash setup-cghmn.sh init</code>
	## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. <code>eth1</code>, then press <code>[Enter]</code> to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface and the default <code>br-lan</code> or any other bridge the interface might belong to, to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick\|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.		## You will be asked what network port you'd like to use for the Retro LAN. This is where you will plug in your retro machines to be part of the CGHMN. Choose a port that is not assigned to any OpenWRT interface like '''lan''' or '''wan''' or which not already part of a bridge and enter the Linux interface name, e.g. <code>eth1</code>, then press <code>[Enter]</code> to continue. If your router only has two ports and you're using one for WAN, then you first have to [https://openwrt.org/docs/guide-user/luci/luci.secure#allow_access_from_internet enable the web UI and SSH access via the '''wan''' OpenWRT interface], remove the entire '''lan''' OpenWRT interface and the default <code>br-lan</code> or any other bridge the interface might belong to, to free the network port and continue the setup over the IP address your router got on its WAN side. If you only have a single Ethernet port, you're running on a router setup we can't really recommend, however you can configure VLANs and use a managed switch to both get a WAN DHCP address for internet access and have a separate VLAN for the Retro LAN bridge over a single port. This is commonly referred to as "[[wikipedia:Router_on_a_stick\|router on a stick]]". Just enter the VLAN interface name here if you choose to go that route.
	# Now you will be given some information on the console, including a ~~Wireguard~~ public key. Head over to https://signup.cghmn.org, fill out the form there with your details like an e-mail address we can reach you under and copy over the ~~Wireguard~~ public key from the script output into the appropriate field on the web page. Once your request has been approved, you'll receive an e-mail with your CGHMN ~~Wireguard connections~~ details. Note: If you cannot copy-paste, for example, because you're on a VM VNC console, you can run <code>ash setup-cghmn.sh pubkey-qr</code> to get a QR code with your public key, which can be scanned with a phone, tablet or software QR code parser to get the key as copy-pastable text.		# Now you will be given some information on the console, including a WireGuard public key. Head over to https://signup.cghmn.org, fill out the form there with your details like an e-mail address we can reach you under and copy over the WireGuard public key from the script output into the appropriate field on the web page. Once your request has been approved, you'll receive an e-mail with your CGHMN WireGuard connection details. Note: If you cannot copy-paste, for example, because you're on a VM VNC console, you can run <code>ash setup-cghmn.sh pubkey-qr</code> to get a QR code with your public key, which can be scanned with a phone, tablet or software QR code parser to get the key as copy-pastable text.
	# In the e-mail from your sign-up server post approval, you will receive a tunnel IPv4 address (<code>100.65.x.x/32</code>) and a routed IPv4 subnet (<code>100.68.x.0/24</code> and up). These will be needed on the next step		# In the e-mail from your sign-up server post approval, you will receive a tunnel IPv4 address (<code>100.65.x.x/32</code>) and a routed IPv4 subnet (<code>100.68.x.0/24</code> and up). These will be needed on the next step
	# Run <code>ash setup-cghmn.sh set-tunnel-ip</code>, enter your new tunnel IP address with or without the <code>/32</code> subnet mask, enter your routed subnet '''with''' the CIDR netmask and supply your pre-shared key from the e-mail.		# Run <code>ash setup-cghmn.sh set-tunnel-ip</code>, enter your new tunnel IP address with or without the <code>/32</code> subnet mask, enter your routed subnet '''with''' the CIDR netmask and supply your pre-shared key from the e-mail.
	# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.		# Once the script completed successfully, reboot the router to ensure all interfaces are up properly. After the reboot, your retro devices should receive an IP address in your routed IPv4 subnet on the Retro LAN port you chose above and be able to communicate with other machines on the CGHMN network.

	=== Get Connected - Manually (Linux, ~~Wireguard~~/IP traffic only) ===		=== Get Connected - Manually (Linux, WireGuard/IP traffic only) ===
	In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:		In case you want to setup a connection into the network manually, here are the required steps and information you should be needing:

	* Generate a Wireguard private key and public key, this command writes a fresh ~~Wireguard~~ private key to <code>private-key</code> and the ~~corresponsing~~ public key to <code>public-key</code>:		* Generate a Wireguard private key and public key, this command writes a fresh WireGuard private key to <code>private-key</code> and the corresponding public key to <code>public-key</code>:

	$ wg genkey \| tee private-key \| wg pubkey > public-key		$ wg genkey \| tee private-key \| wg pubkey > public-key

	* NEVER share your private key, even with us! It should never be required outside of your own ~~Wireguard~~ setup!		* NEVER share your private key, even with us! It should never be required outside of your own WireGuard setup!
	* You will, however, need to share your public key with us. Head over to https://signup.cghmn.org, fill out the forms with some details like an e-mail address we can reach you under and paste the newly generated public key into the public key field.		* You will, however, need to share your public key with us. Head over to https://signup.cghmn.org, fill out the forms with some details like an e-mail address we can reach you under and paste the newly generated public key into the public key field.
	* After submitting your request, we'll approve it as soon as possible and you'll get two IP addresses sent over to your specified e-mail: Your tunnel IP address, with which ''your'' router talks to ''our'' router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.		* After submitting your request, we'll approve it as soon as possible and you'll get two IP addresses sent over to your specified e-mail: Your tunnel IP address, with which ''your'' router talks to ''our'' router, and a routed subnet, from which you can assign IPs to your own machines so they can talk to other CGHMN member devices on the network without NAT in the way.
	* In the e-mail, you will also find a full ~~Wireguard~~ configuration looking a little like this:		* In the e-mail, you will also find a full WireGuard configuration looking a little like this:

	[Interface]		[Interface]
Line 59:		Line 59:

	* Copy this configuration to a file, <code>wg-cghmn.conf</code>, for example.		* Copy this configuration to a file, <code>wg-cghmn.conf</code>, for example.
	* If you use wg-quick like below, you can also add the line <code>DNS = 100.64.12.2</code> in the [Interface] section to make use of our DNS resolvers and access other CGHMN member's services through domain names, though be adviced that we cannot guarantee public internet address lookups, which means this might break internet access for the host you're opening this ~~Wireguard~~ tunnel from! Alternatively, for advanced users, one can setup dnsmasq to automatically pull any domains we offer within the CGHMN and forward them to our DNS resolvers with the help of [https://raw.githubusercontent.com/CGHMN/openwrt-scripts/refs/heads/main/dns/update-dns-forwards.sh this script from our GitHub] and having it being run periodically through cron, systemd-timers or similar. See [[CGHMN DNS Information#dnsmasq Synchronization Script\|this Wiki article]] for more information.		* If you use wg-quick like below, you can also add the line <code>DNS = 100.64.12.2</code> in the [Interface] section to make use of our DNS resolvers and access other CGHMN member's services through domain names, though be adviced that we cannot guarantee public internet address lookups, which means this might break internet access for the host you're opening this WireGuard tunnel from! Alternatively, for advanced users, one can setup dnsmasq to automatically pull any domains we offer within the CGHMN and forward them to our DNS resolvers with the help of [https://raw.githubusercontent.com/CGHMN/openwrt-scripts/refs/heads/main/dns/update-dns-forwards.sh this script from our GitHub] and having it being run periodically through cron, systemd-timers or similar. See [[CGHMN DNS Information#dnsmasq Synchronization Script\|this Wiki article]] for more information.
	* Then, run <code>wg-quick up ./wg-cghmn.conf</code>, perhaps requiring <code>doas</code>/<code>sudo</code>, to bring the tunnel up and connect to the network!		* Then, run <code>wg-quick up ./wg-cghmn.conf</code>, perhaps requiring <code>doas</code>/<code>sudo</code>, to bring the tunnel up and connect to the network!

	This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is ~~congfigured~~ accordingly, of course.		This should bring whatever system you've set the tunnel up on onto the network and is now reachable for other members on the network, as long as the firewall on your device is configured accordingly, of course.

	==== Enabling routing ====		==== Enabling routing ====