• 1 Post
  • 10 Comments
Joined 1Y ago
cake
Cake day: Sep 28, 2023

help-circle
rss
How to go about self hosting a wiki of repair guides?
I have a little side business of doing minor repairs on phones and tablets and such. I was wanting to host a wiki on my network with ifixit guides for the common devices I work on just in case my internet access goes out. I host a lot already but I'm not sure how to go about getting the data to upload to the wiki? Has anyone else done a similar thing?
fedilink

Ooookay… Took me a second to wrap my head around the layout… Originally I only looked at the picture, which only shows a single switch.

This is an odd topography. Typically when working with switches, you want them connecting directly to the router and not connected to another switch.

You are going to have bandwidth issues out the ass, along with having a troubleshooting nightmare when something goes wrong and you need to trace packets.

Right now you have a hub and a spoke inside a hub and spoke.

Since it looks like your Asus is just an AP in this scenario, you’d be better off:

  • hooking both switches to the ISP router
  • enabling DHCP on the ISP router for the 2.5g switch
  • set your 1g switch to a different subnet, with default gateway to your ISP router
  • enable dhcp for different subnet
  • add Asus for WiFi ability on new subnet

You can then play around with VLANing on the managed switch. You won’t be able to separate IoT and Personal WiFi signals with VLAN. Youd need to create a guest SSID for that functionality and change the channels to 6 and 11 so you get good bandwidth

Edit: this is assuming you have a layer 3 switch, if its a layer 2 I would use the Asus as a router/AP and hook it directly to the ISP router and hook the switch up to the Asus.


Looks like it’ll work. You should look into flashing that router with openwrt or pfsense and VLANing off those smart devices… They can be a security issue.

Also adding a second AP that you place on a different channel for guest and untrusted devices would work and increase bandwidth, but adds some routing complexity.


Yea, I haven’t played with it too much. You’ll ever have to host your own SMTP server to send it or use gmail or protons SMTP service.

Doing it yourself might cause big companies to send your mail to spam or possibly just drop the packets cause you’re not using a trusted IP, have the wrong DNS settings, etc. and your ISP may even block port 25

This can be circumvented by using a SMTP relay service but can still have some issues like mail sending limits.


I would have a failsafe, like use a major email provider for emails that you need to go through for like work order government stuff.

Hosting your own email is a great learning experience and is fun to do; but your emails will get marked as spam, you’ll have to constantly perform maintenance, and have major reliability issues.

Most of the issues youll have are fine for personal use, but is dicey if you plan to migrate 100%

Edit: receiving email is less of an issue of sending. The forwarder should be reliable, however, its the sending from the forwarding address that would possibly be an issue.



Personally I’d just spin up a wireguard container with a GUI, user friendly and you can add anyone to your VPN in like 2 minutes wherever you are.

Most advanced part would be forwarding port 51820


A reverse proxy like nginx can automatically implement it for you. Probably the easiest way of generating and using your own SSL with let’s encrypt is a reverse proxy.


So you don’t have the root database password, or just the Lemmy user password?

Might be worth it to make a new database and create a new Lemmy user and migrate data from the backup.

I found this article which might help: https://www.postgresqltutorial.com/postgresql-administration/postgresql-reset-password/

I’ve only ever used Maria dB so YMMV.


Did a little research and seems to be a PIA issue; they don’t provide config files… But there is a workaround: https://github.com/pia-foss/manual-connections

Or a Python script to obtain a config file: https://github.com/hsand/pia-wg

But there are other VPNs that will let you download config files for use, I have no idea why PIA makes it hard.

You would need to create a docker image or some sort of container/VM (container preferred) to host wireguard. This is what I personally use: https://github.com/wg-easy/wg-easy


Check out wireguard, its way smaller and faster than OpenVPN and still FOSS.

https://www.privateinternetaccess.com/vpn-features/wireguard

Very user friendly if you install it with a GUI, almost to plug and play level.