commit - 0b32208741c97f1ba58adeea44e6da5ac7b50041
commit + 5fb0d18a1a9504f1fd4037f998eae34b0622660b
blob - /dev/null
blob + 762ff6816ea03e7780867a6ba4e386ce9c57ead6 (mode 644)
Binary files /dev/null and uploads/Buyvm/routedsubnet1.png differ
blob - /dev/null
blob + e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 (mode 644)
blob - /dev/null
blob + e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 (mode 644)
blob - /dev/null
blob + 90e67fddb6f54190442e18cb64e0d29cf7956534 (mode 644)
Binary files /dev/null and uploads/Buyvm/routedsubnet2.png differ
blob - /dev/null
blob + 282d22adce2be8cf4dbe1be0ba7ec72e38c0a5d1 (mode 644)
--- /dev/null
+++ wiki.d/Buyvm.Ipv6
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650493119
+host=38.87.162.154
+name=Buyvm.Ipv6
+rev=2
+targets=
+text=BuyVM now gives a /48 subnet to each VPS as well as the ability to run your own nameserver for rDNS. Here's how to configure it:%0a%0a 2605:6400:864b::/48 %0a%0aAttach:routedsubnet1.png%0aAttach:routedsubnet2.png%0a
+time=1650497761
+author:1650497761=jrmu
+diff:1650497761:1650493119:=4,6d3%0a%3c %0a%3c Attach:routedsubnet1.png%0a%3c Attach:routedsubnet2.png%0a
+host:1650497761=38.87.162.154
+author:1650493119=jrmu
+diff:1650493119:1650493119:=1,3d0%0a%3c BuyVM now gives a /48 subnet to each VPS as well as the ability to run your own nameserver for rDNS. Here's how to configure it:%0a%3c %0a%3c 2605:6400:864b::/48 %0a
+host:1650493119=38.87.162.154
blob - /dev/null
blob + e830b2c45ccd389733a36d5c4de47bb6e07d340c (mode 644)
--- /dev/null
+++ wiki.d/Buyvm.RecentChanges
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+charset=UTF-8
+ctime=1650493119
+host=38.87.162.154
+name=Buyvm.RecentChanges
+rev=2
+text=* [[Buyvm/Ipv6]] . . . April 20, 2022, at 11:36 PM by [[~jrmu]]: [==]%0a
+time=1650497761
blob - /dev/null
blob + 911f6e535195c21de0cd9a7664f24766a42fb46a (mode 644)
--- /dev/null
+++ wiki.d/Ntpd.Configure
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650435430
+host=38.87.162.154
+name=Ntpd.Configure
+rev=1
+targets=
+text=(:title NTPd:)%0a%0aNTPd is very important for ensuring the accurate time on your server.%0a%0aMake sure to specify your non-ddos filtered IPv4 address in /etc/ntpd.conf:%0a%0a[@%0alisten on 192.168.0.1%0aquery from 192.168.0.1%0a@]%0a
+time=1650435430
+title=NTPd
+author:1650435430=jrmu
+diff:1650435430:1650435430:=1,10d0%0a%3c (:title NTPd:)%0a%3c %0a%3c NTPd is very important for ensuring the accurate time on your server.%0a%3c %0a%3c Make sure to specify your non-ddos filtered IPv4 address in /etc/ntpd.conf:%0a%3c %0a%3c [@%0a%3c listen on 192.168.0.1%0a%3c query from 192.168.0.1%0a%3c @]%0a
+host:1650435430=38.87.162.154
blob - /dev/null
blob + 060947c4dc5681750926eac09f24ce9cb945a439 (mode 644)
--- /dev/null
+++ wiki.d/Ntpd.RecentChanges
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+charset=UTF-8
+ctime=1650435430
+host=38.87.162.154
+name=Ntpd.RecentChanges
+rev=1
+text=* [[Ntpd/Configure]] . . . April 20, 2022, at 06:17 AM by [[~jrmu]]: [==]%0a
+time=1650435430
blob - /dev/null
blob + 0a278e53acedfde3c674571044d89506310a0370 (mode 644)
--- /dev/null
+++ wiki.d/Route.RecentChanges
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+charset=UTF-8
+ctime=1650435752
+host=38.87.162.154
+name=Route.RecentChanges
+rev=1
+text=* [[Route/Usage]] . . . April 20, 2022, at 06:22 AM by [[~jrmu]]: [==]%0a
+time=1650435752
blob - /dev/null
blob + 2519125281b1e6d71592ee3d3b4d642fd74e4d72 (mode 644)
--- /dev/null
+++ wiki.d/Route.Usage
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650435752
+host=38.87.162.154
+name=Route.Usage
+rev=1
+targets=
+text='''Route is a tool for viewing and manipulating the kernel's IP routing table'''%0a\\%0aWith route you can configure your network routing to other hosts and gateways. You may have a bunch of virtual machines with a certain routing scheme, or physical computers with many NICs (Network Interface Card, or just network adapter). If you have a OpenBSD shell access you can try to show the current routing parameters of the machine.\\%0a\\%0aSome example usages:\\%0a''route -n show'' // Show routing table without resolving DNS names\\%0a''route show'' // Show routing table and solve DNS names\\%0a\\%0aTo add a route to the network 192.168.5.0/24 use:\\%0a''route add -inet 192.168.5.0/24 192.168.0.1''\\%0awhere the latter address is the gateway\\%0a\\%0aTo change the default gateway:\\%0aedit the file ''/etc/mygate'' directly\\%0a\\%0aPlease consider the route manual page for more information.%0a
+time=1650435752
+author:1650435752=jrmu
+diff:1650435752:1650435752:=1,16d0%0a%3c '''Route is a tool for viewing and manipulating the kernel's IP routing table'''%0a%3c \\%0a%3c With route you can configure your network routing to other hosts and gateways. You may have a bunch of virtual machines with a certain routing scheme, or physical computers with many NICs (Network Interface Card, or just network adapter). If you have a OpenBSD shell access you can try to show the current routing parameters of the machine.\\%0a%3c \\%0a%3c Some example usages:\\%0a%3c ''route -n show'' // Show routing table without resolving DNS names\\%0a%3c ''route show'' // Show routing table and solve DNS names\\%0a%3c \\%0a%3c To add a route to the network 192.168.5.0/24 use:\\%0a%3c ''route add -inet 192.168.5.0/24 192.168.0.1''\\%0a%3c where the latter address is the gateway\\%0a%3c \\%0a%3c To change the default gateway:\\%0a%3c edit the file ''/etc/mygate'' directly\\%0a%3c \\%0a%3c Please consider the route manual page for more information.%0a
+host:1650435752=38.87.162.154
blob - /dev/null
blob + 8df68fe8f107cbda21e7e89cf88d06453c11f008 (mode 644)
--- /dev/null
+++ wiki.d/Signify.RecentChanges
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+charset=UTF-8
+ctime=1650478121
+host=38.87.162.154
+name=Signify.RecentChanges
+rev=3
+text=* [[Signify/Verify]] . . . April 20, 2022, at 06:24 PM by [[~jrmu]]: [==]%0a
+time=1650479056
blob - /dev/null
blob + 48ec43da22ebd615484e598bbd0cc67cc679a21c (mode 644)
--- /dev/null
+++ wiki.d/Signify.Verify
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650478121
+host=38.87.162.154
+name=Signify.Verify
+rev=3
+targets=
+text=[[https://man.openbsd.org/signify|signify]] is a utility that lets you%0aeasily sign and verify files using cryptography.%0a%0aTo verify an OpenBSD ISO using signify:%0a%0a[@%0a$ ftp https://ftp.openbsd.org/pub/OpenBSD/7.1/amd64/install71.iso%0a$ ftp https://ftp.openbsd.org/pub/OpenBSD/7.1/amd64/SHA256.sig%0a$ signify -C -p /etc/signify/openbsd-71-base.pub -x SHA256.sig install71.iso%0aSignature Verified%0ainstall71.iso: OK%0a@]%0a%0a-C verifies a signed checksum list, -p provides the public key, and -x provides the signature file.%0a%0aIf you see this message:%0a%0a[@%0aSignature Verified%0ainstall71.iso: FAIL%0a@]%0a%0aThis may mean that your ISO is either corrupt or has been tampered with. You%0awill want to download it again and make sure it verifies properly.%0a%0aOn the other hand, if you see this message:%0a%0a[@%0asignify: verification failed: checked against wrong key%0a@]%0a%0aYou may have the wrong public key.%0a
+time=1650479056
+author:1650479056=jrmu
+diff:1650479056:1650478132:=1,3d0%0a%3c [[https://man.openbsd.org/signify|signify]] is a utility that lets you%0a%3c easily sign and verify files using cryptography.%0a%3c %0a7,11c4,6%0a%3c $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.1/amd64/install71.iso%0a%3c $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.1/amd64/SHA256.sig%0a%3c $ signify -C -p /etc/signify/openbsd-71-base.pub -x SHA256.sig install71.iso%0a%3c Signature Verified%0a%3c install71.iso: OK%0a---%0a> $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.0/amd64/install70.iso%0a> $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.0/amd64/SHA256.sig%0a> $ signify -C -p /etc/signify/openbsd-70-base.pub -x SHA256.sig install70.iso%0a13,32d7%0a%3c %0a%3c -C verifies a signed checksum list, -p provides the public key, and -x provides the signature file.%0a%3c %0a%3c If you see this message:%0a%3c %0a%3c [@%0a%3c Signature Verified%0a%3c install71.iso: FAIL%0a%3c @]%0a%3c %0a%3c This may mean that your ISO is either corrupt or has been tampered with. You%0a%3c will want to download it again and make sure it verifies properly.%0a%3c %0a%3c On the other hand, if you see this message:%0a%3c %0a%3c [@%0a%3c signify: verification failed: checked against wrong key%0a%3c @]%0a%3c %0a%3c You may have the wrong public key.%0a
+host:1650479056=38.87.162.154
+author:1650478132=jrmu
+diff:1650478132:1650478121:=3d2%0a%3c [@%0a7d5%0a%3c @]%0a
+host:1650478132=38.87.162.154
+author:1650478121=jrmu
+diff:1650478121:1650478121:=1,5d0%0a%3c To verify an OpenBSD ISO using signify:%0a%3c %0a%3c $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.0/amd64/install70.iso%0a%3c $ ftp https://ftp.openbsd.org/pub/OpenBSD/7.0/amd64/SHA256.sig%0a%3c $ signify -C -p /etc/signify/openbsd-70-base.pub -x SHA256.sig install70.iso%0a
+host:1650478121=38.87.162.154
blob - /dev/null
blob + 86a19cbdf754fde434244c11dd7f8c24f63c9ad1 (mode 644)
--- /dev/null
+++ wiki.d/Team.Testing
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650491106
+host=38.87.162.154
+name=Team.Testing
+rev=1
+targets=Openbsd.FilePermissions,Openbsd.Shell,Openbsd.Setuid
+text=Testing servers contain shell accounts, giving users more freedom to run their own software. However, it also requires more maintenance because malicious users have greater ability to harm the network.%0a%0aAt a minimum, you will need to consult:%0a%0a|| border=1 width=100%25 class="sortable simpletable"%0a||! Training ||||%0a|| [[Openbsd/FilePermissions|File Permissions Guide]] ||||%0a|| [[Openbsd/Shell|Shell Guide]] ||||%0a|| [[Openbsd/Setuid|Setuid Guide]] ||||%0a
+time=1650491106
+author:1650491106=jrmu
+diff:1650491106:1650491106:=1,9d0%0a%3c Testing servers contain shell accounts, giving users more freedom to run their own software. However, it also requires more maintenance because malicious users have greater ability to harm the network.%0a%3c %0a%3c At a minimum, you will need to consult:%0a%3c %0a%3c || border=1 width=100%25 class="sortable simpletable"%0a%3c ||! Training ||||%0a%3c || [[Openbsd/FilePermissions|File Permissions Guide]] ||||%0a%3c || [[Openbsd/Shell|Shell Guide]] ||||%0a%3c || [[Openbsd/Setuid|Setuid Guide]] ||||%0a
+host:1650491106=38.87.162.154
blob - /dev/null
blob + 29a0e611797c97b395de5e197aa7b04c16bf31e8 (mode 644)
--- /dev/null
+++ wiki.d/Team.Welcome
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650430517
+host=38.87.162.154
+name=Team.Welcome
+rev=6
+targets=Team.Announce,Ircnow.Dogfood,ZNC.Admin,ZNC.Support,Police.Intro,Ambassador.Ilines,Mlmmj.Install,Pmwiki.Install,Iked.Configure,Openbsd.Dump,Openrsync.Usage
+text=(:title Welcome to the Team!:)%0a%0aTeam Leaders:%0a%0a# Assign and coordinate additional tasks to team members%0a# Before making changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify them.%0a%0aTeam Responsibilities%0a%0a# Please use your team's services: [[ircnow/dogfood|dogfood]]!%0a# Take a look at your team's website. Are there any broken links? Are all your services advertised?%0a# After joining a team, you will need to create the following accounts:%0a # Create a ZNC account on your team's bouncer%0a # Create an email account (username@example.com) on your team's mail server%0a # Configure your mail server to forward emails sent from support@example.com to your email account%0a# Log all actions taken on the server. Either:%0a # Report each action on IRC to your team channel, or%0a # Email the entire team at support@example.com%0a # Set up a webpage / file to keep track of admin actions%0a# Before editing a configuration file, save a backup copy with a timestamp and serial number. For example, @@doas cp doas.conf doas.conf.2022042001@@. The timestamp is in the form of YYYYMMDD followed by two digits.%0a# Join your team's IRC channel, #example-team, and read your team email daily%0a%0aIRC:%0a%0a# Join the networks and channels that your team offers to provide customer support on. Please use your team's bouncer or use an IRC client that can remain permanently online.%0a# Please add yourself as IRC operator to your team's ngircd. From now on, please connect to your team's IRC server and log in as oper. Join us on #opers for oper-related discussion%0a# Connect to your own IRC server to ensure it is running properly.%0a# Be present on #team to meet new teammates and to meet our new trainees.%0a%0aZNC:%0a%0a# Use your own ZNC server. That way, if there are bugs, you will notice them right away.%0a# Follow the [[ZNC/Admin|ZNC Admin]] and [[ZNC/Support|support guide]]%0a# If you see a user with frequent disconnects, fix his network connection%0a# If you see a user that has been banned, [[police/intro|investigate abuse]] or [[Ambassador/Ilines|request an iline]].%0a%0aEmail:%0a%0a# Please check support@example.com emails daily%0a# If your team has not yet done so, please set up either mail forwarding or a [[mlmmj/install|mailing list]] for support@example.com. That way, users can use their own individual email accounts rather than sharing a single account%0a%0aWebsite:%0a%0a# Please make sure your webpage is up-to-date and free of dead links%0a# For every service you add, please update your website to advertise them%0a%0aWiki:%0a%0a# Please create your team [[pmwiki/install|wiki]]. IRCNow uses pmwiki but you are free to use any wiki software.%0a%0aVPN:%0a%0a# Configure an IPSec VPN using [[iked/configure|openiked]]%0a%0aBackups:%0a%0a# Make regular backups of your server using [[openbsd/dump|dump and restore]] and [[openrsync/usage|openrsync]]. Your team will be responsible for its own backups.%0a
+time=1650431503
+title=Welcome to the Team!
+author:1650431503=jrmu
+diff:1650431503:1650431428:=53c53%0a%3c # Configure an IPSec VPN using [[iked/configure|openiked]]%0a---%0a> # Configure an IPSec VPN using [[iked/install|openiked]]%0a
+host:1650431503=38.87.162.154
+author:1650431428=jrmu
+diff:1650431428:1650431247:=46c46,47%0a%3c %0a---%0a> # %0a> %0a49,50c50,51%0a%3c # Please create your team [[pmwiki/install|wiki]]. IRCNow uses pmwiki but you are free to use any wiki software.%0a%3c %0a---%0a> # Please configure your team website%0a> %0a53,54c54,55%0a%3c # Configure an IPSec VPN using [[iked/install|openiked]]%0a%3c %0a---%0a> # If not done yet, please configure a VPN%0a> %0a56,57d56%0a%3c %0a%3c # Make regular backups of your server using [[openbsd/dump|dump and restore]] and [[openrsync/usage|openrsync]]. Your team will be responsible for its own backups.%0a
+host:1650431428=38.87.162.154
+author:1650431247=jrmu
+diff:1650431247:1650431055:=3,9c3,4%0a%3c Team Leaders:%0a%3c %0a%3c # Assign and coordinate additional tasks to team members%0a%3c # Before making changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify them.%0a%3c %0a%3c Team Responsibilities%0a%3c %0a---%0a> Team Orientation%0a> %0a40,56c35,39%0a%3c # If your team has not yet done so, please set up either mail forwarding or a [[mlmmj/install|mailing list]] for support@example.com. That way, users can use their own individual email accounts rather than sharing a single account%0a%3c %0a%3c Website:%0a%3c %0a%3c # Please make sure your webpage is up-to-date and free of dead links%0a%3c # For every service you add, please update your website to advertise them%0a%3c # %0a%3c %0a%3c Wiki:%0a%3c %0a%3c # Please configure your team website%0a%3c %0a%3c VPN:%0a%3c %0a%3c # If not done yet, please configure a VPN%0a%3c %0a%3c Backups:%0a---%0a> %0a> Team Leaders:%0a> %0a> # Assign and coordinate additional tasks to team members%0a> # Before making changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify them.%0a
+host:1650431247=38.87.162.154
+author:1650431055=jrmu
+diff:1650431055:1650430894:=30,31c30,31%0a%3c # If you see a user that has been banned, [[police/intro|investigate abuse]] or [[Ambassador/Ilines|request an iline]].%0a%3c %0a---%0a> # If you see a user that has been banned, [[police/intro|investigate abuse]] or [[openbsd/ilines|request an iline]].%0a> %0a34,35c34,35%0a%3c # Please check support@example.com emails daily%0a%3c %0a---%0a> # All team members '''must''' check support@example.com emails daily%0a> %0a39a40,41%0a> %0a> %0a
+host:1650431055=38.87.162.154
+author:1650430894=jrmu
+diff:1650430894:1650430517:=15c15%0a%3c # Before editing a configuration file, save a backup copy with a timestamp and serial number. For example, @@doas cp doas.conf doas.conf.2022042001@@. The timestamp is in the form of YYYYMMDD followed by two digits.%0a---%0a> # Before editing a configuration file, save a backup copy with a timestamp and serial number. For example, @@doas cp doas.conf doas.conf.2020123100@@%0a17a18,20%0a> # The team leader should assign and coordinate additional tasks to team members%0a> # Before making any changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify users.%0a> %0a22d24%0a%3c # Connect to your own IRC server to ensure it is running properly.%0a27,33c29,35%0a%3c # Use your own ZNC server. That way, if there are bugs, you will notice them right away.%0a%3c # Follow the [[ZNC/Admin|ZNC Admin]] and [[ZNC/Support|support guide]]%0a%3c # If you see a user with frequent disconnects, fix his network connection%0a%3c # If you see a user that has been banned, [[police/intro|investigate abuse]] or [[openbsd/ilines|request an iline]].%0a%3c %0a%3c Email:%0a%3c %0a---%0a> # Log in to your own ZNC server every day. You should use the same ZNC that you provide to your users. That way, if there are any bugs, you will notice them right away.%0a> # Each day, check /home/znc/home/znc/.znc/moddata/adminlog/znc.log to check for any connection issues.%0a> # If you see a user with frequent disconnects, fix his network connection for him.%0a> # If you see a user GLINEd, you need to either [[openbsd/police|investigate abuse]] or [[openbsd/ilines|request an iline]].%0a> %0a> SMTP:%0a> %0a35,41d36%0a%3c %0a%3c Team Leaders:%0a%3c %0a%3c # Assign and coordinate additional tasks to team members%0a%3c # Before making changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify them.%0a%3c %0a%3c %0a
+host:1650430894=38.87.162.154
+author:1650430517=jrmu
+diff:1650430517:1650430517:=1,36d0%0a%3c (:title Welcome to the Team!:)%0a%3c %0a%3c Team Orientation%0a%3c %0a%3c # Please use your team's services: [[ircnow/dogfood|dogfood]]!%0a%3c # Take a look at your team's website. Are there any broken links? Are all your services advertised?%0a%3c # After joining a team, you will need to create the following accounts:%0a%3c # Create a ZNC account on your team's bouncer%0a%3c # Create an email account (username@example.com) on your team's mail server%0a%3c # Configure your mail server to forward emails sent from support@example.com to your email account%0a%3c # Log all actions taken on the server. Either:%0a%3c # Report each action on IRC to your team channel, or%0a%3c # Email the entire team at support@example.com%0a%3c # Set up a webpage / file to keep track of admin actions%0a%3c # Before editing a configuration file, save a backup copy with a timestamp and serial number. For example, @@doas cp doas.conf doas.conf.2020123100@@%0a%3c # Join your team's IRC channel, #example-team, and read your team email daily%0a%3c %0a%3c # The team leader should assign and coordinate additional tasks to team members%0a%3c # Before making any changes that may cause downtime for users, follow the [[team/announce|announcements guide]] to notify users.%0a%3c %0a%3c IRC:%0a%3c %0a%3c # Join the networks and channels that your team offers to provide customer support on. Please use your team's bouncer or use an IRC client that can remain permanently online.%0a%3c # Please add yourself as IRC operator to your team's ngircd. From now on, please connect to your team's IRC server and log in as oper. Join us on #opers for oper-related discussion%0a%3c # Be present on #team to meet new teammates and to meet our new trainees.%0a%3c %0a%3c ZNC:%0a%3c %0a%3c # Log in to your own ZNC server every day. You should use the same ZNC that you provide to your users. That way, if there are any bugs, you will notice them right away.%0a%3c # Each day, check /home/znc/home/znc/.znc/moddata/adminlog/znc.log to check for any connection issues.%0a%3c # If you see a user with frequent disconnects, fix his network connection for him.%0a%3c # If you see a user GLINEd, you need to either [[openbsd/police|investigate abuse]] or [[openbsd/ilines|request an iline]].%0a%3c %0a%3c SMTP:%0a%3c %0a%3c # All team members '''must''' check support@example.com emails daily%0a
+host:1650430517=38.87.162.154
blob - /dev/null
blob + 82a48da15030d2bbe65d82b987ad35fe8761e81d (mode 644)
--- /dev/null
+++ wiki.d/Vmm.Linux
+version=pmwiki-2.2.130 ordered=1 urlencoded=1
+agent=w3m/0.5.3+git20210102
+author=jrmu
+charset=UTF-8
+csum=
+ctime=1650432795
+host=38.87.162.154
+name=Vmm.Linux
+rev=1
+targets=
+text=(:Install Linux on OpenBSD VMM:)%0a%0aYou can run any Linux or BSD-based operating system on your VPS as a guest inside OpenBSD.%0a%0aYou will be given a username and password for your account. This will create a username on our host system:%0a%0a[@%0a$ ssh username@coconut.ircnow.org%0a@]%0a%0aECDSA key fingerprint is SHA256:a0LIR/BRZkpYqMho/YvkISPEm7vkus5QfOSqAeu+tYc.%0a%0a**Please note**: This is the host machine, not your VM. The host machine is running OpenBSD but your guest VPS can run any OS.%0a%0aOnce you log in, you can access the serial console:%0a%0a[@%0a$ vmctl console %3cvm-name>%0a@]%0a%0aTo shutdown the VM:%0a%0a[@%0a$ vmctl stop %3cvm-name>%0a@]%0a%0aTo boot the VM:%0a%0a[@%0a$ vmctl start %3cvm-name>%0a@]%0a%0aTo pause the VM:%0a%0a[@%0a$ vmctl pause %3cvm-name>%0a@]%0a%0aTo unpause the VM:%0a%0a[@%0a$ vmctl unpause %3cvm-name>%0a@]%0a%0aTo escape serial console, type ~~. %0a%0a----%0a%0aTo connect to your VM, you will be given an IP address. In case you forget, your IP address can be found by running $ dig username.coconut.ircnow.org. Our default gateway is 38.87.162.1.%0a%0aFor convenience, you can log in to your VPS as follows:%0a%0a[@%0a$ ssh username@username.coconut.ircnow.org%0a@]%0a%0aPlease note that this hostname is different from the host; there is an extra username in username.coconut.ircnow.org.%0a%0a----%0a%0aTo reinstall OpenBSD 6.6:%0a%0a[@%0a$ ssh username@coconut.ircnow.org%0a$ cd ~%0a$ rm username.qcow2%0a$ vmctl create -s 20G username.qcow2%0a$ vmctl start username%0a$ vmctl start username%0a$ vmctl console username%0a@]%0a%0aMake sure to configure static networking as well as to set up ping in the background as outlined below.%0a%0a----%0a%0aFor OpenBSD, here is how you statically assign your IP address:%0a%0aInside /etc/hostname.vio0:%0a%0a[@%0ainet 38.87.162.xxx 255.255.255.0%0a@]%0a%0aReplace 38.87.162.xxx with your assigned IP address.%0a%0aInside /etc/mygate:%0a%0a[@%0a38.87.162.1%0a@]%0a%0aFor Alpine:%0a%0aTo restart networking:%0a%0a[@%0a# service networking restart%0a@]%0a%0aFor Debian:%0a%0a[@%0asystemctl restart networking%0a@]%0a%0aInside /etc/network/interfaces:%0a%0a[@%0asource /etc/network/interfaces.d/*%0a%0a# The loopback network interface%0aauto lo%0aiface lo inet loopback%0a%0a# The primary network interface%0aauto enp0s2%0aiface enp0s2 inet static%0a address 38.87.162.x%0a netmask 255.255.255.0%0a gateway 38.87.162.1%0a@]%0a%0a----%0a%0aLosing network connectivity:%0a%0aFor OpenBSD, put this in your crontab:%0a%0a[@%0a@reboot /usr/bin/tmux new -d 'while true; do /sbin/ping -i5 38.87.162.1; done' \;%0a@]%0a%0aAfterwards, to ensure it runs right away, execute this once:%0a%0a[@%0a/usr/bin/tmux new -d 'while true; do /sbin/ping -i5 38.87.162.1; done' \;%0a@]%0a%0aFor Debian:%0a%0a[@%0a@reboot /usr/bin/tmux new -d 'while true; do /usr/bin/ping -i5 38.87.162.1; done' \;%0a@]%0a%0aAfterwards, to ensure it runs right away, execute this once:%0a%0a[@%0a/usr/bin/tmux new -d 'while true; do /usr/bin/ping -i5 38.87.162.1; %0a@]%0a%0aFor Alpine:%0a%0a[@%0a@reboot /usr/bin/tmux new -d 'while true; do /bin/ping -i5 38.87.162.1; done' \;%0a@]%0a%0aAfterwards, to ensure it runs right away, execute this once:%0a%0a[@%0a/usr/bin/tmux new -d 'while true; do /bin/ping -i5 38.87.162.1; done' \;%0a@]%0a%0a----%0a%0aTo reinstall OpenBSD:%0a%0aFirst, log in to the host:%0a%0a[@%0a$ ssh username@coconut.ircnow.org%0a$ vmctl stop username%0a$ rm username.qcow2%0a$ vmctl create -s 20G username.qcow2%0a$ vmctl start username%0a$ vmctl console username%0a@]%0a%0aThen, do the installation as usual.%0a
+time=1650432795
+author:1650432795=jrmu
+diff:1650432795:1650432795:=1,179d0%0a%3c (:Install Linux on OpenBSD VMM:)%0a%3c %0a%3c You can run any Linux or BSD-based operating system on your VPS as a guest inside OpenBSD.%0a%3c %0a%3c You will be given a username and password for your account. This will create a username on our host system:%0a%3c %0a%3c [@%0a%3c $ ssh username@coconut.ircnow.org%0a%3c @]%0a%3c %0a%3c ECDSA key fingerprint is SHA256:a0LIR/BRZkpYqMho/YvkISPEm7vkus5QfOSqAeu+tYc.%0a%3c %0a%3c **Please note**: This is the host machine, not your VM. The host machine is running OpenBSD but your guest VPS can run any OS.%0a%3c %0a%3c Once you log in, you can access the serial console:%0a%3c %0a%3c [@%0a%3c $ vmctl console %3cvm-name>%0a%3c @]%0a%3c %0a%3c To shutdown the VM:%0a%3c %0a%3c [@%0a%3c $ vmctl stop %3cvm-name>%0a%3c @]%0a%3c %0a%3c To boot the VM:%0a%3c %0a%3c [@%0a%3c $ vmctl start %3cvm-name>%0a%3c @]%0a%3c %0a%3c To pause the VM:%0a%3c %0a%3c [@%0a%3c $ vmctl pause %3cvm-name>%0a%3c @]%0a%3c %0a%3c To unpause the VM:%0a%3c %0a%3c [@%0a%3c $ vmctl unpause %3cvm-name>%0a%3c @]%0a%3c %0a%3c To escape serial console, type ~~. %0a%3c %0a%3c ----%0a%3c %0a%3c To connect to your VM, you will be given an IP address. In case you forget, your IP address can be found by running $ dig username.coconut.ircnow.org. Our default gateway is 38.87.162.1.%0a%3c %0a%3c For convenience, you can log in to your VPS as follows:%0a%3c %0a%3c [@%0a%3c $ ssh username@username.coconut.ircnow.org%0a%3c @]%0a%3c %0a%3c Please note that this hostname is different from the host; there is an extra username in username.coconut.ircnow.org.%0a%3c %0a%3c ----%0a%3c %0a%3c To reinstall OpenBSD 6.6:%0a%3c %0a%3c [@%0a%3c $ ssh username@coconut.ircnow.org%0a%3c $ cd ~%0a%3c $ rm username.qcow2%0a%3c $ vmctl create -s 20G username.qcow2%0a%3c $ vmctl start username%0a%3c $ vmctl start username%0a%3c $ vmctl console username%0a%3c @]%0a%3c %0a%3c Make sure to configure static networking as well as to set up ping in the background as outlined below.%0a%3c %0a%3c ----%0a%3c %0a%3c For OpenBSD, here is how you statically assign your IP address:%0a%3c %0a%3c Inside /etc/hostname.vio0:%0a%3c %0a%3c [@%0a%3c inet 38.87.162.xxx 255.255.255.0%0a%3c @]%0a%3c %0a%3c Replace 38.87.162.xxx with your assigned IP address.%0a%3c %0a%3c Inside /etc/mygate:%0a%3c %0a%3c [@%0a%3c 38.87.162.1%0a%3c @]%0a%3c %0a%3c For Alpine:%0a%3c %0a%3c To restart networking:%0a%3c %0a%3c [@%0a%3c # service networking restart%0a%3c @]%0a%3c %0a%3c For Debian:%0a%3c %0a%3c [@%0a%3c systemctl restart networking%0a%3c @]%0a%3c %0a%3c Inside /etc/network/interfaces:%0a%3c %0a%3c [@%0a%3c source /etc/network/interfaces.d/*%0a%3c %0a%3c # The loopback network interface%0a%3c auto lo%0a%3c iface lo inet loopback%0a%3c %0a%3c # The primary network interface%0a%3c auto enp0s2%0a%3c iface enp0s2 inet static%0a%3c address 38.87.162.x%0a%3c netmask 255.255.255.0%0a%3c gateway 38.87.162.1%0a%3c @]%0a%3c %0a%3c ----%0a%3c %0a%3c Losing network connectivity:%0a%3c %0a%3c For OpenBSD, put this in your crontab:%0a%3c %0a%3c [@%0a%3c @reboot /usr/bin/tmux new -d 'while true; do /sbin/ping -i5 38.87.162.1; done' \;%0a%3c @]%0a%3c %0a%3c Afterwards, to ensure it runs right away, execute this once:%0a%3c %0a%3c [@%0a%3c /usr/bin/tmux new -d 'while true; do /sbin/ping -i5 38.87.162.1; done' \;%0a%3c @]%0a%3c %0a%3c For Debian:%0a%3c %0a%3c [@%0a%3c @reboot /usr/bin/tmux new -d 'while true; do /usr/bin/ping -i5 38.87.162.1; done' \;%0a%3c @]%0a%3c %0a%3c Afterwards, to ensure it runs right away, execute this once:%0a%3c %0a%3c [@%0a%3c /usr/bin/tmux new -d 'while true; do /usr/bin/ping -i5 38.87.162.1; %0a%3c @]%0a%3c %0a%3c For Alpine:%0a%3c %0a%3c [@%0a%3c @reboot /usr/bin/tmux new -d 'while true; do /bin/ping -i5 38.87.162.1; done' \;%0a%3c @]%0a%3c %0a%3c Afterwards, to ensure it runs right away, execute this once:%0a%3c %0a%3c [@%0a%3c /usr/bin/tmux new -d 'while true; do /bin/ping -i5 38.87.162.1; done' \;%0a%3c @]%0a%3c %0a%3c ----%0a%3c %0a%3c To reinstall OpenBSD:%0a%3c %0a%3c First, log in to the host:%0a%3c %0a%3c [@%0a%3c $ ssh username@coconut.ircnow.org%0a%3c $ vmctl stop username%0a%3c $ rm username.qcow2%0a%3c $ vmctl create -s 20G username.qcow2%0a%3c $ vmctl start username%0a%3c $ vmctl console username%0a%3c @]%0a%3c %0a%3c Then, do the installation as usual.%0a
+host:1650432795=38.87.162.154
