You're probably not exposed to the big internet. But that's no excuse for poor security. I'd look up a hardening guide for your operating system.

You should also look up hardening guides for any applications you plan to run, and follow simple security measures like not logging in as root/admin, strong passwords, 2FA.

Not to say you're at risk, but its good practice to make secure your default. Doing this will help you understand the basics of system security and the risks that systems have.

Might be janky, but if you really wanted this for free you could get a speech to text program like futo, play the video and have it transcribe it and save it to a text file, then copy and paste in the subtitles

Surley there is a switch out there that can detect voltage used by the device and only deliver that amount.

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.

Depends on your definition of safe.

If you do a public port forward and set up basic security and proper SSL its safe from the majority of people.

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.

You could host a wireshark instance, and maybe even host a SIEM like security onion.

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.

Honestly servers don't need to be speced out of oblivion. I use a 10 year old desktop and added a 1TB ssd and it does 99% of what I want it too.

Most important thing for a server is probably the CPU and making sure it has as many cores as possible and maybe hyper threading because you'll be running a lot if simultaneous services and users.

No only the server, you can host an openssh server and have clients connect remotely.

Sorta like how you can host a webserver and a client doesn't need 443 open. Except a reverse shell is possible with ssh, allowing a client to be controlled without their port 22 open.

You can tunnel RDP over SSH. Then you'd only open a port that requires authentication to access and is encrypted.