![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
But it is. They’re stopped and deallocated. They start up when demanded. And shutdown when below a threshold or a certain schedule.
But it is. They’re stopped and deallocated. They start up when demanded. And shutdown when below a threshold or a certain schedule.
No we shut them down. They get deallocated the same way as shutting down a virtual server does. They’re not containers, the scaling part just turns them on and off based on workload or schedule
Finally someone who gets it.
Is it shutting down servers… Yes. it just does it based on parameters and thresholds.
Then you get things like VDI servers and jump boxes that only need to be on between certain hours, so get shutdown outside them hours.
In pretty much any enterprise using the public cloud. Everything is auto scaling, so shutdowns when not needed. Dev environments shutdown over night… If you’re not shutting down and scaling in the public cloud, you’re doing it wrong.
We power off servers in the enterprise all the time and on schedules 😂. Its called saving money.
My solution is the correct way and easier way. You don’t need MAC address white-list. You just have a guest SSID with DHCP on, they get the IP from the subnet in that zone. No crazy subnet hacks etc.
Can I join your guest network, sure. Let me just grab your mac address, login to the DHCP server, create a reservation with a limited subnet mask that can still see the default gateway.
Or can I connect to you guest network, sure here is the code or scan that QR code. That’s it, they’re in the guest VLAN and subnet, zoned off on the firewall and have QOS applied to not saturate the network.
This is not the way to do it. The correct way would be multiple SSID’s with each tagged to their own VLAN.
Each VLAN has its own subnet. You can then use a zone based firewall, to allow the zones(subnets) to access each other.
You can also then apply QOS, to limit guest network speeds, prioritize LAN traffic etc.
And zone based firewalls are stateful, you can do rules such as LAN can reach IOT, but not the other way. Or IOT can only reach the IOT server, on specific ports.
SFP+ is 10Gb/s not SFP. The ASIC needs to be capable of the speeds for the transceiver to work. SFP+ is the name given for 10Gb/s module and transceivers.
So if a device supports SFP+ it supports 10Gb/s. It doesn’t automatically mean it will work with 5 or 2.5Gb/s transceivers.
The UK has two modes of “fibre” FTTC fibre to cabinet. Then copper to your property. Or FTTP, fibre to premise, which is as you describe fibre right to your property.
Its not loose. Its free, smile and wave boys, smile and wave.
I am just waiting for your switch shelf to collapse. That’s some serious flex. :)
You do understand, when you have VM’s set to auto scale, they shutdown when not in use, if you’re using horizontal scaling.