It is a postfix representing the subnet „set bit“ prefix. Can we agree on this ?

Third: with your /24 subnet you told your system it has that many address to talk to. With the /32 you told it has none to talk to. With adding a route you gave the additional info „there is another network called … with a subnet of … wich you can talk to“ So your second solution is more or less equivalent but with extra steps. I don’t know how it’s implemented in the backend but it is different as in the second there is no network per default but you add routes to some. In contrast to there is a network and no routing is needed

Second, a bit of a nitbit. It’s a postfix not a prefix, as it is after the IP address

First: it seems you got some things mixed up. 192.168.0.1/24 isn’t a IP address, strictly speaking. It’s Network information wich translates to „your IP is 192.168.0.1 and your subnet mask is 255.255.255.0“. The /dd is the amount of bits set in the subnet mask. An within the first and last address are reserved for network and broadcast. With your /32 assignments you basically told your system, it has no network to talk to.

You’re right. I just gave a very simplified answer. VLAN isn’t part of the default network communication and therefore every „node“ needs to support it and be correctly set up, or otherwise the VLAN tag will be removed at that point.

And in my other comment I emphasized, that my main issue with multiple WAP is, to distribute the amount of devices each has to talk to. Multi SSID wouldn’t solve that

Since VLAN isn’t officially part of the standard, you’d need all your network devices support it. And I wanted to give a device-load-balance. So not increase coverage but reduce the amount of devices per AP. Separate SSIDs and VLAN aren’t helping that it just makes it easier to track, wich group is causing the load

The main issue is your 30+ Wi-Fi devices. One AP can only handle this much total bandwidth. But first, it looks like you waste 2gb of your fibre speed? Get a compatible router.

For your setup it almost looks like you’re better off with a total 10gb internal speed. And get 2 more AP, one dedicated for your smart home, one for „less important devices“ and use the ASUS for the rest. - remember to use different channels on each AP.

So in short hook your HV,NAS,PC,[new router w/ AP?],[AP2],[AP3],[AP1?] on a new 10GB switch. Split your devices over the 3 AP, on different channels

Edit: or you could get one of those for cheaper „Qnap QSW-M2108R-2C“ That is a 2.5G with two additional 10G ports so you could plug your new router into one of them and use the other for later use of the NAS if it supports that speed

The limiting factor is mostly your upload speed. And also you need to have a good QoS set up, or you have very limited internet usability. Where as on-site you can get way higher speeds for cheaper

https://youtu.be/vvr9AMWEU-c

Afaik they used it as redundant off-site backup

Just do the Tesla MO. Say it’s almost ready, just needs a few optimisations and will be rolled out next year

deleted by creator

Imagine doing this on a dial-up 56K modem

There is also a whole OS written in scratch. A very basic one but still

I want to tell the computer what it should do, not what the computer things I can do. That’s why I use scratch

Im very curious about what was the actual violation

How do you know that hosting isn’t a football match ?

I have mine in a DMZ, so it can be fully exposed with software firewall. I thought it’ll be less work to setup and maintain. Wich it is, when I have a small project I can just plug my pi into the DMZ and it’s good to go.

Self hosted usually refers to onside hosting. The VPS you are using is hosted offside. So basically it refers to where the server is, not who manages it. But there is a big overlap and many use them synonymous. It’s more of a „well actually“ that only happens to apply here

Yea, that’s the whole deal with self hosting. Offside hosting or cloud hosting doesn’t mean you just have SAAS, you can have lower level access or even IAAS