I also received a few words from Virmach via DM. Thanks again to all of you. I shared it here because I knew I’d get some supportive words, even if we don’t know each other’s faces.
It’s ironic that I don’t do this with the people who actually know me in person.
Well, it only took a couple of reinstalls, and I think I'm actually satisfied with everything now. My first time playing with mdadm remotely, I only broke it twice. Installs and rescue cd working great for dedis at least! If anyone wants to save themselves some effort, if you've got a mix of SSDs and HDDs and want them in separate raids but you don't want to install from CD yourself, it's easiest to tell the template installer to do RAID1. Let it make a single raid1 across all drives, then drop the hdds and rebuild the array from the rescue cd to no longer expect 4 drives, and create your hdd array after. Don't be a dork like me and tell it to install on the smallest drive to build the array on root yourself, it's way more tedious that way.
I have to say, I'm pretty impressed with the dedi control panel, everything just works as expected. Smoother experience than setting up my Fiberstate dedi was, zero complaints here
I'm trying something new for your convenience, every time I end up writing a wall of text, you now get a concise summary. Actually let me just read through it and see if it's good enough to use as the only response. Just to be clear, I didn't ask the AI to write this for me, I wrote out a wall of text. Yeah, it's be cruel to post the original version, it's just a waste of everyone's time. This was a bad idea. This was originally in response to @imok and @bakageta
Oh no, the AI version sucks, and I overwrote my original wall of text.
I'll return at a later time to rewrite the wall of text. Experiment over.
(edit) Can you tell I just woke up recently? I forgot the original is literally there in the prompt with the AI. Let me just rewrite it later anyway, it's all over the place.
This is the rewritten wall of text, and applies only to dedicated server rentals.
Regarding HW RAID Controllers
I'm considering ordering a few different controllers, potentially considering an HBA, or a technically "lower-end" RAID controller that's actually technically an HBA, plus everything else that's within the required pricepoint, for testing.
JBOD script is set up and appears to be partially working, but I noticed the 9240 controllers we have are on an ancient firmware version and can't actually verify it any further.
The plan is to do two things for the 9240, a) flash them to latest firmware, and b) cross-flash them to 9211 for HBA (passthrough, so you can easily do JBOD and we can just use the existing software RAID profiles.) One of these two will be decided on as the default. This is what @Wonder_Woman's build is waiting on. I had to spend a good amount of time re-remembering all this information.
We also have 9260 controllers, but they are only currently used by @Kris and @skorous and I do not remember if I placed them into other active builds. Once another build is located that has it, I'll start going through these cards as well and testing our options.
There are some general issues I've noticed we'll be running into with HW RAID controllers, and these need to be addressed. I'll list each one as well as the current plan/my thoughts on it, in the next next section.
General list of things to be addressed
The control panel doesn't detect inventory automatically in relation to RAID controllers, and I bet it's not going to do aa very good job of wiping the configuration. I will likely add warnings on (a) the cancellation page for dedicated servers, and (b) overdue invoice email for dedicated servers reminding people to wipe their own sensitive data, as it is the only way to ensure that.
Beta testers should know that there's currently some important configurations that are not fully set up, such as the disk wiping after re-assignment, and you should keep that in mind if during the beta test period some "change" occurs, although odds are low, such as if we have to move you over to another physical server for any critical reason.
As time goes on, I'll likely try to add more specific configurations for disk grouping as @bakageta mentioned, as well as "walkthroughs" gathering the information everyone has collected for their specific builds. We need this to appear on the installation page or before it in some way, as well as perhaps in the welcome email. It should include specific OS compatibility info as well.
For configurations where we know there may some type of conflict, I need to add in an alert on the configuration page. For example, if you might be assigned a server with a RAID controller, and it has some limitations on what kernel it supports.
Some general information on how KVM works that gets displayed before you access the console, or knowledgebase article that's available somewhere, in terms of usage limits, other limitations, and potential security concerns. Some way of allowing people to request we "disable" it if it's not a feature on the control panel on your end, or even physically unplugging it.
Regarding IPv4 Subnets
@imok asked about this, we're about a week away. I need to either bring in another /24 block that will be used for this and pick out the best one with longest term we have, or just rent another block on month to month terms. I'm trying to set up the control panel to where each server is still always assigned at least 1x IPv4 from the shared block since we have that long-term.
@imok said: @VirMach before the invoice is due, are you able to sell a /29?
I'll add this to your invoice. If anyone else is interested in having a subnet, now is the best time for you to let me know if you want it to be at a discounted rate. Otherwise the non-discounted rate for adding a /29 later will likely be $14 per month and a /28 will be $30 per month. Once we run the sale, there will be a sale price for subnets, and that will also be honored for any existing servers if you want to add it on at a later date during the sale, at our discretion.
For anyone who is interested in a subnet such as @imok you can also click spoiler below to see a list of available /24 that are for lease, and let me know which one you'd prefer we lease, if you're into that.
I will likely start adding this into the control panel and configuring it, and we're going to stress that this is your server's primary allocation. It should be used in your setup for highest resiliency to IPv4 renumbering. This (IPv6) is the only assignment that will likely not need to ever be renumbered.
The allocation will most likely be a /56 IPv4 for dedicated servers. There's no current plans to allow the purchase of any larger IPv6 subnets, but that may occur at a later time.
Regarding Single IPv4 Assignments
These are currently on a shared /24 subnet. There's currently nothing preventing someone from using any IP address from this block, which will work out fine with people I trust for the beta test, but obviously will need some protection. The current plan is to have a simple setup that detects who should be using what IP address, and enforces it, ranging from communication alerts where possible, all the way to turning off the server's port if abuse is detected.
I've thought about it and this combination definitely beats only doing small subnets, since it heavily cuts down on wasted IP addresses where possible, and we can use those IPs from a subnet that has a lower chance of renumbering.
Regarding KVM Switch
The original plan was to do it in a very "VirMach" way which is to say the service technically is not sold with KVM access and you can pay to guarantee that access. Instead of doing that and upsetting maybe 50+ people in the process with uncertainty, we're going to go the upsetting 2+ people route of setting policy limitations for them, and should someone really need exceptions, that's where things such as purchasing access to a dedicated KVM can be discussed with the customer, instead of charging some additional feature port monthly fee or something like that.
Limits and policy:
I'm a big offender on this, where I accidentally leave one open, so I've already set an auto timeout to 30 minutes if inactive. This may be adjusted as required.
The system is 64 ports total, with a hardcoded limitation to, I believe, 8 active running sessions. However, it will have a technical limitation potentially before this number. So far I think we've been able to get 3 or 4 going simultaneously with no problems.
I've also confirmed there's two messages that appear. When active session numbers is exceeded, it properly tells you to come back later. There's another error that seems to happen when there's general connection issues, this could be from the control panel trying to generate multiple sessions too quickly, or from other physical limitations.
You'll have a "license" -- if you want to call it that, to use KVM during (1) initial setup process where it's absolutely required, (2) emergency situations. We can disconnect sessions for any reason at our discretion. Anything else is he honor system, if it becomes a problem, you may be contacted, so we can find a solution. Later on, this may evolve to some automated system of some kind, it all depends on how big of a problem it really is, like if out of the 64 ports, a good number of people decide they want to use this as the exclusive way to use their server, then we have a problem.
The motherboards themselves have limitations on what can actually be displayed on VGA, so think 2D, probably works. 3D, no.
I also need to make the security more robust. Right now there's already an ACL as mentioned, but I'm taking this further and do have a plan. I just don't want to describe our security measures in detail here, it likely wouldn't be a good idea.
Upgrade options:
$0 one-time is the low performance barely works version included, but it's been working.
$25 one-time if you want to upgrade to a dongle that does better mouse syncing and has virtual media support.
$50 one-time if you want BIOS virtual media support on top of better mouse syncing and general ISO support.
$100 one-time if you want your own dedicated KVM dongle.
All the above are as available, pricing changes based on availability. They are technically available used/open box at a cheaper price, but based on my experience so far, we definitely want to go brand new with these to avoid any potential problems as those potential problems can plague the entire switch in some ways. Pricing is based off how much the dongle reliably costs in larger quantities, so it'll be a little bit higher than what someone is listing one of them for on eBay. You can consider any of the rest of it my "tip" for doing free remote hands for it I guess.
I haven't added them as a configurable option yet, we might not bother doing it until we get our first interested buyer, it might just end up not being worth everyone's time to think about and treated as a customization request.
@bakageta said: I have to say, I'm pretty impressed with the dedi control panel, everything just works as expected. Smoother experience than setting up my Fiberstate dedi was, zero complaints here
Yeah, I am as well. It's good enough to the point where all I can really say negative about it seems to be minor annoyances or actual feature requests, instead of what we're used to with the other software we use which is where every reported bug is a feature request. Let's hope it lasts.
@imok said: @VirMach before the invoice is due, are you able to sell a /29?
I'll add this to your invoice. If anyone else is interested in having a subnet, now is the best time for you to let me know if you want it to be at a discounted rate. Otherwise the non-discounted rate for adding a /29 later will likely be $14 per month and a /28 will be $30 per month. Once we run the sale, there will be a sale price for subnets, and that will also be honored for any existing servers if you want to add it on at a later date during the sale, at our discretion.
For anyone who is interested in a subnet such as @imok you can also click spoiler below to see a list of available /24 that are for lease, and let me know which one you'd prefer we lease, if you're into that.
Nice. Definitely I want a /29, but depending on the price and if available, a /28 would be nicer.
The dedicated KVM dongle would also be great but maybe in 3 months after I recover financially from the current invoice 😂
@imok said: Why would anyone have a preference over a subnet?
Some people like IPs that are easy to remember. For instance, one of our subnets is 199.101.101.x and another is 199.233.233.x. We had a customer who was obsessed with 199.101.101.101 and 199.233.233.233. Not important to me, but I told him sure, whatever floats your boat. I assume that's what @VirMach is talking about.
@imok said: Why would anyone have a preference over a subnet?
Some people like IPs that are easy to remember. For instance, one of our subnets is 199.101.101.x and another is 199.233.233.x. We had a customer who was obsessed with 199.101.101.101 and 199.233.233.233. Not important to me, but I told him sure, whatever floats your boat. I assume that's what @VirMach is talking about.
$0 one-time is the low performance barely works version included, but it's been working.
$25 one-time if you want to upgrade to a dongle that does better mouse syncing and has virtual media support.
$50 one-time if you want BIOS virtual media support on top of better mouse syncing and general ISO support.
$100 one-time if you want your own dedicated KVM dongle.
I think I'm being dumb but I'm not sure I understand the difference between $25/$50 and $100. If you do the $25/$50 dongle you get a better one but you're just one of the 7 or 8 active sessions and have to limit your usage? If you pay $100 the pool increases to 8 or 9 and one of those is yours ?
@VirMach said: The allocation will most likely be a /56 IPv4 for dedicated servers. There's no current plans to allow the purchase of any larger IPv6 subnets, but that may occur at a later time.
Oh yeah, forgot to say I want a /56 of IPv4 plz. ;-)
@taizi said:
want a /29 too,one more /29 if i can get some good specs/pricing(nice CPU like 5500/5700X)
but can I know whats the /29 price during the sale
Will likely be, for the sale:
$4/MO - /29 IPv4
$8/MO - /28 IPv4
By the way, you had a dedicated server with us in the past and talked about wanting something, right? You should DM me with what you want as it'll be your best chance to get what you want at a good price during the "beta" for dedicated servers.
The 5500 has motherboard compatibility issues, you don't want that. I'm still trying to figure out what we can do to have no problems, it'll have to be whatever specs work out. The 5700X will cost extra one-time setup, likely at least $100 one-time, it's whatever the difference is between what you pick and the 5700X basically, depending on some other factors (could be full price of the processor, so around $150.)
$0 one-time is the low performance barely works version included, but it's been working.
$25 one-time if you want to upgrade to a dongle that does better mouse syncing and has virtual media support.
$50 one-time if you want BIOS virtual media support on top of better mouse syncing and general ISO support.
$100 one-time if you want your own dedicated KVM dongle.
I think I'm being dumb but I'm not sure I understand the difference between $25/$50 and $100. If you do the $25/$50 dongle you get a better one but you're just one of the 7 or 8 active sessions and have to limit your usage? If you pay $100 the pool increases to 8 or 9 and one of those is yours ?
First of all, there's a hidden option. There's one between the $0 and $25 that's actually more expensive brand new due to availability, and all it does is do what the $0 one is supposed to do but "officially."
The $25 and $50 options are just dongles that go into the server's VGA port and USB port(s) but then attach to the same 2U 64-Port KVM switch. This is just how they decided to do everything, there's a little chip that handles the VGA/USB per server, and then communicates to the 64-Port device via ethernet. And some of them are better than others.
The $100 option is a standalone dongle. It also has everything else that would usually get handled by the 64-Port switch, but does it on the dongle. The dongle's a little larger, etc. Doesn't plug into the 64-Port KVM switch. Plugs directly into the network switch. So you're the only user, and the device is only handling your connection. (Edit) I should probably actually take into consideration the extra setup required, and potential need for a VPN to secure it and so on, so that option will likely also have a monthly fee as well. I don't think anyone will actually go for it though.
@VirMach
I had a dedicated server with you that was disrupted due to colocrossing, Now that you have been able settle down with you setup at Oklahoma DC, I would like to be part of your early beta on dedication server here.
@taizi said:
want a /29 too,one more /29 if i can get some good specs/pricing(nice CPU like 5500/5700X)
but can I know whats the /29 price during the sale
@bula said: @VirMach
I had a dedicated server with you that was disrupted due to colocrossing, Now that you have been able settle down with you setup at Oklahoma DC, I would like to be part of your early beta on dedication server here.
Make a ticket and private message the ticket ID just so I can locate it more quickly, or just private message and include your email with us there, and let me know what specifications you are most interested in and your budget, or if you just want best specifications for same price you were paying.
@bula said: @VirMach
I had a dedicated server with you that was disrupted due to colocrossing, Now that you have been able settle down with you setup at Oklahoma DC, I would like to be part of your early beta on dedication server here.
Make a ticket and private message the ticket ID just so I can locate it more quickly, or just private message and include your email with us there, and let me know what specifications you are most interested in and your budget, or if you just want best specifications for same price you were paying.
"Ticket Created #212865", see what you can offer within what I was previously paying with flexibility of one-time payments for upgrades.
Two lose two per subnet. First one is the network, last is the broadcast. So technically 6 are usable on a /29 except one of them has to be used for the gateway. So 5 left for the server.
/30 - 1 out of 4 (25%)
/29 - 5 out of 8 (62%)
/28 - 13 out of 16 (81%)
This is the reason we're doing the shared IP address per server as the default instead of a /30.
I guess I don't know much about why people are adamant about including the gateway as being usable, but that's probably what ends up causing a lot of the confusion. I know it has something to do with it technically being usable in some situations. But then by that definition, a /31 is technically also 2 usable addresses, I guess because using the traditional definition of "usable" it'd be 0 so they go to the actual use case for that. It's just kind of weird that ends up with /31 being 2 usable, and /30 being 2 usable but under different definitions, and 1 under others.
I'm surprised some of you remember Perejilo. I'm glad about that. It's actually been more than 2 years since I lost him but I constantly talk about him (outside the forum).
I've added this to the invoice as you requested. Keep in mind it goes alongside same term, if that's not what you expected let me know, I won't be able to switch the IPv4 portion to monthly but you can move down to /29.
And for anyone else getting subnets: if you get annual services, subnet will be annual, there's no discount for subnets for term (aka, no 2 months free on 12 months, we don't get 2 months free so you don't get 2 months free.) The sale price is basically the price we pay for them plus however much lost on inefficiencies estimated, so we could technically make a bit of profit on them but it's much more likely we'll lose money on them. That's why I can't go any lower or include them for "free" on top of anything.
Comments
Sincerest condolences. Never easy.
That sucks :-(
So sorry for your loss imok.
So sorry to hear that
Thank you all. I really appreciate your kind words.
The next few days will be a bit tough. Our house is small, and she was always around, always in sight.
Sra. Inés (our other cat, Mrs. Agnes in your language), my wife and I will be missing her, just like we still miss our dear Perejilo.
I also received a few words from Virmach via DM. Thanks again to all of you. I shared it here because I knew I’d get some supportive words, even if we don’t know each other’s faces.
It’s ironic that I don’t do this with the people who actually know me in person.
I'm sorry to spoil the party.
Let’s carry on with the virmachadventures!
@VirMach before the invoice is due, are you able to sell a /29? If so, you can add it to the current invoice so I can track a single payment.
Additionally, please delete the duplicate invoice before any automatic payment is processed
is "duplicate" or "duplicated" invoice?
Well, it only took a couple of reinstalls, and I think I'm actually satisfied with everything now. My first time playing with mdadm remotely, I only broke it twice. Installs and rescue cd working great for dedis at least! If anyone wants to save themselves some effort, if you've got a mix of SSDs and HDDs and want them in separate raids but you don't want to install from CD yourself, it's easiest to tell the template installer to do RAID1. Let it make a single raid1 across all drives, then drop the hdds and rebuild the array from the rescue cd to no longer expect 4 drives, and create your hdd array after. Don't be a dork like me and tell it to install on the smallest drive to build the array on root yourself, it's way more tedious that way.
I have to say, I'm pretty impressed with the dedi control panel, everything just works as expected. Smoother experience than setting up my Fiberstate dedi was, zero complaints here
I'm trying something new for your convenience, every time I end up writing a wall of text, you now get a concise summary. Actually let me just read through it and see if it's good enough to use as the only response. Just to be clear, I didn't ask the AI to write this for me, I wrote out a wall of text. Yeah, it's be cruel to post the original version, it's just a waste of everyone's time. This was a bad idea. This was originally in response to @imok and @bakageta
Oh no, the AI version sucks, and I overwrote my original wall of text.
I'll return at a later time to rewrite the wall of text. Experiment over.
(edit) Can you tell I just woke up recently? I forgot the original is literally there in the prompt with the AI. Let me just rewrite it later anyway, it's all over the place.
This is the rewritten wall of text, and applies only to dedicated server rentals.
Regarding HW RAID Controllers
There are some general issues I've noticed we'll be running into with HW RAID controllers, and these need to be addressed. I'll list each one as well as the current plan/my thoughts on it, in the next next section.
General list of things to be addressed
Regarding IPv4 Subnets
@imok asked about this, we're about a week away. I need to either bring in another /24 block that will be used for this and pick out the best one with longest term we have, or just rent another block on month to month terms. I'm trying to set up the control panel to where each server is still always assigned at least 1x IPv4 from the shared block since we have that long-term.
I'll add this to your invoice. If anyone else is interested in having a subnet, now is the best time for you to let me know if you want it to be at a discounted rate. Otherwise the non-discounted rate for adding a /29 later will likely be $14 per month and a /28 will be $30 per month. Once we run the sale, there will be a sale price for subnets, and that will also be honored for any existing servers if you want to add it on at a later date during the sale, at our discretion.
For anyone who is interested in a subnet such as @imok you can also click spoiler below to see a list of available /24 that are for lease, and let me know which one you'd prefer we lease, if you're into that.
Regarding IPv6 Subnets
I will likely start adding this into the control panel and configuring it, and we're going to stress that this is your server's primary allocation. It should be used in your setup for highest resiliency to IPv4 renumbering. This (IPv6) is the only assignment that will likely not need to ever be renumbered.
The allocation will most likely be a /56 IPv4 for dedicated servers. There's no current plans to allow the purchase of any larger IPv6 subnets, but that may occur at a later time.
Regarding Single IPv4 Assignments
These are currently on a shared /24 subnet. There's currently nothing preventing someone from using any IP address from this block, which will work out fine with people I trust for the beta test, but obviously will need some protection. The current plan is to have a simple setup that detects who should be using what IP address, and enforces it, ranging from communication alerts where possible, all the way to turning off the server's port if abuse is detected.
I've thought about it and this combination definitely beats only doing small subnets, since it heavily cuts down on wasted IP addresses where possible, and we can use those IPs from a subnet that has a lower chance of renumbering.
Regarding KVM Switch
The original plan was to do it in a very "VirMach" way which is to say the service technically is not sold with KVM access and you can pay to guarantee that access. Instead of doing that and upsetting maybe 50+ people in the process with uncertainty, we're going to go the upsetting 2+ people route of setting policy limitations for them, and should someone really need exceptions, that's where things such as purchasing access to a dedicated KVM can be discussed with the customer, instead of charging some additional feature port monthly fee or something like that.
Limits and policy:
I also need to make the security more robust. Right now there's already an ACL as mentioned, but I'm taking this further and do have a plan. I just don't want to describe our security measures in detail here, it likely wouldn't be a good idea.
Upgrade options:
All the above are as available, pricing changes based on availability. They are technically available used/open box at a cheaper price, but based on my experience so far, we definitely want to go brand new with these to avoid any potential problems as those potential problems can plague the entire switch in some ways. Pricing is based off how much the dongle reliably costs in larger quantities, so it'll be a little bit higher than what someone is listing one of them for on eBay. You can consider any of the rest of it my "tip" for doing free remote hands for it I guess.
I haven't added them as a configurable option yet, we might not bother doing it until we get our first interested buyer, it might just end up not being worth everyone's time to think about and treated as a customization request.
Yeah, I am as well. It's good enough to the point where all I can really say negative about it seems to be minor annoyances or actual feature requests, instead of what we're used to with the other software we use which is where every reported bug is a feature request. Let's hope it lasts.
Nice. Definitely I want a /29, but depending on the price and if available, a /28 would be nicer.
The dedicated KVM dongle would also be great but maybe in 3 months after I recover financially from the current invoice 😂
Why would anyone have a preference over a subnet?
Some people like IPs that are easy to remember. For instance, one of our subnets is 199.101.101.x and another is 199.233.233.x. We had a customer who was obsessed with 199.101.101.101 and 199.233.233.233. Not important to me, but I told him sure, whatever floats your boat. I assume that's what @VirMach is talking about.
QuickPacket - Dedicated Servers in Ashburn, Los Angeles, Chicago
I would like @virmach to rent 1.1.1.1 then
Sorry to hear about ur loss -- my sincerest condolences @imok
even I am obsessed now 🙃🤝🤌
want a /29 too,one more /29 if i can get some good specs/pricing(nice CPU like 5500/5700X)
but can I know whats the /29 price during the sale
I think I'm being dumb but I'm not sure I understand the difference between $25/$50 and $100. If you do the $25/$50 dongle you get a better one but you're just one of the 7 or 8 active sessions and have to limit your usage? If you pay $100 the pool increases to 8 or 9 and one of those is yours ?
Oh yeah, forgot to say I want a /56 of IPv4 plz. ;-)
Will likely be, for the sale:
$4/MO - /29 IPv4
$8/MO - /28 IPv4
By the way, you had a dedicated server with us in the past and talked about wanting something, right? You should DM me with what you want as it'll be your best chance to get what you want at a good price during the "beta" for dedicated servers.
The 5500 has motherboard compatibility issues, you don't want that. I'm still trying to figure out what we can do to have no problems, it'll have to be whatever specs work out. The 5700X will cost extra one-time setup, likely at least $100 one-time, it's whatever the difference is between what you pick and the 5700X basically, depending on some other factors (could be full price of the processor, so around $150.)
First of all, there's a hidden option. There's one between the $0 and $25 that's actually more expensive brand new due to availability, and all it does is do what the $0 one is supposed to do but "officially."
The $25 and $50 options are just dongles that go into the server's VGA port and USB port(s) but then attach to the same 2U 64-Port KVM switch. This is just how they decided to do everything, there's a little chip that handles the VGA/USB per server, and then communicates to the 64-Port device via ethernet. And some of them are better than others.
The $100 option is a standalone dongle. It also has everything else that would usually get handled by the 64-Port switch, but does it on the dongle. The dongle's a little larger, etc. Doesn't plug into the 64-Port KVM switch. Plugs directly into the network switch. So you're the only user, and the device is only handling your connection. (Edit) I should probably actually take into consideration the extra setup required, and potential need for a VPN to secure it and so on, so that option will likely also have a monthly fee as well. I don't think anyone will actually go for it though.
@VirMach
I had a dedicated server with you that was disrupted due to colocrossing, Now that you have been able settle down with you setup at Oklahoma DC, I would like to be part of your early beta on dedication server here.
A /28 would be great for me then.
I should learn ipv6
Make a ticket and private message the ticket ID just so I can locate it more quickly, or just private message and include your email with us there, and let me know what specifications you are most interested in and your budget, or if you just want best specifications for same price you were paying.
"Ticket Created #212865", see what you can offer within what I was previously paying with flexibility of one-time payments for upgrades.
How many IPs will be usable with these?
May or may not be 5 and 13 usable IPs.
Sorry to hear that. I recall last time Perejilo passed away suddenly.
Hope you and missus get the strength to face this turbulent times.
God bless 🙌 🙏
Two lose two per subnet. First one is the network, last is the broadcast. So technically 6 are usable on a /29 except one of them has to be used for the gateway. So 5 left for the server.
/30 - 1 out of 4 (25%)
/29 - 5 out of 8 (62%)
/28 - 13 out of 16 (81%)
This is the reason we're doing the shared IP address per server as the default instead of a /30.
I guess I don't know much about why people are adamant about including the gateway as being usable, but that's probably what ends up causing a lot of the confusion. I know it has something to do with it technically being usable in some situations. But then by that definition, a /31 is technically also 2 usable addresses, I guess because using the traditional definition of "usable" it'd be 0 so they go to the actual use case for that. It's just kind of weird that ends up with /31 being 2 usable, and /30 being 2 usable but under different definitions, and 1 under others.
Thank you @localhost
I'm surprised some of you remember Perejilo. I'm glad about that. It's actually been more than 2 years since I lost him but I constantly talk about him (outside the forum).
Time really flies.
I've added this to the invoice as you requested. Keep in mind it goes alongside same term, if that's not what you expected let me know, I won't be able to switch the IPv4 portion to monthly but you can move down to /29.
And for anyone else getting subnets: if you get annual services, subnet will be annual, there's no discount for subnets for term (aka, no 2 months free on 12 months, we don't get 2 months free so you don't get 2 months free.) The sale price is basically the price we pay for them plus however much lost on inefficiencies estimated, so we could technically make a bit of profit on them but it's much more likely we'll lose money on them. That's why I can't go any lower or include them for "free" on top of anything.