You need VLANs if you want separate networks on the SAME router. But if you have separate routers, then you don’t need VLANs.

You will need two wireless access points. If the router you mentioned has two wireless access points built in, then just set one to connect to the shared network, and the other will act as an AP for your private network. Then the router can be configured to send WAN traffic out of the shared network AP.

If you use a router that only has a single AP built in, then you will need to purchase and additional AP to plug into one of your router’s LAN ports so that it has two total.

Some routers might have the ability to create multiple wireless networks on one router, but be sure the hardware can handle the load. I know my ubiquity UDM can create up to 5 wireless networks on that single device before you run into performance issues.

Honestly, if you’re using your own router, you won’t need to worry about VLANs as long as your router separates your private network from the shared one.

For example, if the shared network is 192.168.0.0/24, you can make your private network 192.168.5.0/24 and have your router’s firewall block incoming traffic from 192.168.0.0/24. Only allow WAN traffic out, and allow return traffic.

Then have your router or connected server act as the authoritative DNS and DHCP servers for the 192.168.5.0/24 private network.

One wireless AP will be used in client mode to connect to the 192.168.0.0/24 shared network. The other wireless AP will be used as an access point for other devices to connect to the 192.168.5.0/24 private network.

Its perfect for a small VPS. Been using it for years.

I do occasionally get places where my email simply will not send to them, even though it follows every email standard properly and isnt blacklisted. For those rare occasions, ill use a third party email address to send, which then forwards everything to my main email.

Yes, its fine to have your OS on a separate SSD and use your HDD as data storage.

Its also important to maintain your drives. Be sure to have SMART alerts, and do spinrite or badblocks occasionally to let the drive firmware remove bad sectors from use.

Check out Mail-in-a-Box

This blog is specifically for websites that are public facing. Sure, you can wireguard into your local network, but you can also SSH into your local network. Either way you have to poke a hole.

Good read.

I would just like to add some additional information that favors changing your SSH port to something other than the default. When crawlers are going around the internet looking for vulnerable SSH servers, they’re more than likely going to have an IP range and specifically look for port 22.

Now can they go through and scan your IP and all of its ports to look for the SSH service? Yes. But you will statistically have less interactions with bad actors this way since they might specifically be looking for port 22.

You must be one of those self-driven, motivated, and energetic developers

Its up to your distros package maintainer to make the patched version available. You can find who maintains it and contact them so they are aware.

https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3

Security concerns can vary between traditional Linux distributions and rolling release distributions.

Traditional Linux Distributions:

1. Stability: Traditional distributions like Ubuntu LTS tend to prioritize stability over the latest software updates. While this can reduce the risk of new software vulnerabilities, it may also mean that security patches for certain software components are not as up-to-date as in rolling releases.

2. Delayed Updates: Security updates for software packages may take longer to reach users in traditional distributions because they go through a more extensive testing and validation process. This delay could potentially leave systems vulnerable for a longer period.

3. Predictability: Traditional distributions have predictable release cycles, making it easier to plan and apply security updates. However, this predictability can also make it easier for attackers to anticipate when certain software versions will be in use.

Rolling Release Distributions:

1. Up-to-Date Software: Rolling releases like Arch Linux or Manjaro provide the latest software updates as soon as they are available. While this ensures access to new security features and patches quickly, it can also introduce new bugs and vulnerabilities.

2. Frequent Updates: Rolling releases typically require more frequent updates, which can be time-consuming and potentially introduce compatibility issues if not managed properly.

3. User Responsibility: Users of rolling releases have a greater responsibility to stay informed about security updates and apply them promptly. Failure to do so can leave systems vulnerable.

4. Testing: Rolling releases often have a testing phase where updates are evaluated by the community before being rolled out to all users. This helps catch issues, but it can still result in occasional instability.

In summary, the main security concern with traditional Linux distributions is the potential delay in receiving security updates, while rolling releases offer up-to-date software but may require more user vigilance and can occasionally introduce instability due to frequent updates. The choice between them should depend on your specific use case and your willingness to manage updates and stability.

Not yet…

Its a rolling release, so will always have the most up to date and patched packages the fastest. That concept is the antivirus.

Can’t infect your machine if the vulnerabilities are already fixed.

Honestly, the best antivirus for Linux is Arch.

To connect your blog to an RSS feed, you’ll need to follow these general steps:

1. Check if your blogging platform supports RSS: Most blogging platforms, like WordPress, Blogger, and Tumblr, automatically generate an RSS feed for your blog. You can usually find the feed URL in the format “yourblogurl.com/rss” or “yourblogurl.com/feed”.

2. Verify the RSS feed URL: Confirm that your blog’s RSS feed is working by opening the URL in a web browser. You should see a list of your blog’s recent posts in XML format.

3. Promote your RSS feed: Add an RSS subscription button on your blog’s website to make it easy for visitors to subscribe. You can use an RSS icon and link it to your feed URL.

4. Submit your RSS feed to RSS directories: This step is optional but can help increase your blog’s visibility. Submit your RSS feed URL to popular RSS directories like Feedburner, Feedly, or Bloglovin’.

5. Test your RSS feed: Use online RSS feed validators to ensure your feed is well-formed and doesn’t have any errors.

By following these steps, you can connect your blog to an RSS feed and allow your readers to subscribe and stay updated with your latest content. If you need specific instructions for your blogging platform, let me know which one you’re using, and I can provide more detailed guidance.

RSS stands for Really Simple Syndication. It is a web feed format used to publish frequently updated content such as blog posts, news articles, podcasts, and videos. RSS allows users to subscribe to their favorite websites or blogs and receive updates automatically without having to visit each site individually. It’s a convenient way to stay up-to-date with the latest content from multiple sources in one place.

RSS has been around for quite some time. It was first introduced in 1999 by Netscape as part of their Netscape Netcenter platform. Later, it gained wider adoption and became more popular in the early 2000s. Over the years, it has undergone various versions and improvements to make it more efficient and versatile. Despite the rise of other content distribution methods and social media platforms, RSS still remains a useful tool for content consumption and distribution for many users.