@lukast__ said: While this is a bit off-topic, I have a question to those who know more about IPv6 than I do. I could reach the server from outside (via ssh and ICMP ping) over IPv6, however from inside the VPS I couldn't reach any IPv6.
Is this fixed? I've been there as well. They resolved it by manually whitelisting my subnet.
For me it works since around 11 PM GMT+1 yesterday, but I didn't need to open a ticket.
For us IPv6 nerds (who manage IPv6 manually): should we power-off the server before or after opening a ticket? it's not clear in the mail.
Is there a time limit? What happens if we don't open a ticket by then? Service cancelled?
@Shot² said:
For us IPv6 nerds (who manage IPv6 manually): should we power-off the server before or after opening a ticket? it's not clear in the mail.
Is there a time limit? What happens if we don't open a ticket by then? Service cancelled?
Nerds receive a ticket from us with the settings to set up ( "nerds" are identified by having custom install, 99% of the cases this is true, and most of them opened a ticket already )
All usual folks, we will set the new ip in cloud-init and issue a power-off / power on - they need to do nothing.
@localhost said: @host_c thanks for the /64
Any quick quides to enable ipv6 on AlmaLinux 9?
Seems when I installed via iso only ipv4 is enabled by default
@localhost said: @host_c thanks for the /64
Any quick quides to enable ipv6 on AlmaLinux 9?
Seems when I installed via iso only ipv4 is enabled by default
Thanks
nmtui and off you go.
Is there a way to use nmtui which would setup ipv6 like a dhcp does for ipv4? For me it is asking me to enter the details manually. Thnx
@localhost said: @host_c thanks for the /64
Any quick quides to enable ipv6 on AlmaLinux 9?
Seems when I installed via iso only ipv4 is enabled by default
Thanks
nmtui and off you go.
Is there a way to use nmtui which would setup ipv6 like a dhcp does for ipv4? For me it is asking me to enter the details manually. Thnx
You can set IPv6 to "automatic" and see what happens... But it depends on the network whether it works or not.
@localhost said: @host_c thanks for the /64
Any quick quides to enable ipv6 on AlmaLinux 9?
Seems when I installed via iso only ipv4 is enabled by default
Thanks
nmtui and off you go.
Is there a way to use nmtui which would setup ipv6 like a dhcp does for ipv4? For me it is asking me to enter the details manually. Thnx
You can set IPv6 to "automatic" and see what happens... But it depends on the network whether it works or not.
DHCP will do nothing on our infrastructure.
There is no such service enabled.
Ip addresses are allocated / service by a provisioning module ( that started working as it should , hence the posibility to allocate a whole /64 rather rather then 1 /127 )
@tmntwitw said: I might be wrong, but for a single IPv6 address, the subnet mask should be /128 right?
not in our setup, this whole shit started ~1 year back.
Let me give you all an insight.
We used IP Manager 2 from ModulesGarden, at that was and is awesome for IPV4 but not for IPV6, it could not allocate a whole /64 ( from a /48 or any )
So we did a temporary work around, ( these usually bit you in the ass or in other sensitive places) by setting a /64 on each subnet we have, allocating a single IP from that /64 to customer ( as that worked in the module ) and wait out the update to IPMANAGER 3.
Update came ~2 months ago, but by that time we had give out a bunch of manually assigned /64's.
Each of these had :1 set up on the router and usually :2,3,4 for the customer - yeah, I know, lame, but it is what it is.
We ditched IP Manager 2 ~2 months ago ( that was fun as it was a ton of work so you all do not loos the already assigned ip's at the moment we selected disabled module).
And by the tests we did over the past 1 month we manage to implement the correct way to allocate a /64 from a /48 set up on each IPV4 subnet. ( all IPV4 subnets are separated at layer 2, each one has it's own broadcast domain and separate IPV6 GW + firewall stuff and other )
So when our ISP took out by mistake a /48 we used before for the old setup, I said to myself that this is as any good moment to do the implementation.
And here we are, modifying all to standard so we can ditch the " open a tiket for IPV6 /64 " and also this give us the following flexibility wise:
allocate multiple /64 IPV6 at product check-out
create IPV6 only services ( save a few bucks / year )
create IPV6 only products that can select to allocate one IPV4 address if desired by the customer at check-out
I know we are not winning loyalty points stopping your services, but we had 2 options on the table:
A. send out 500-600 E-mails so customers set up the new IPV6 setup or do a power off power on to auto apply the stings - all this when they read the email. - most probably this would taken 1 Decade
B. kill the old setup, we do all the work + some of you that have "nerd" setups - this will take ~1 week by our estimates.
I chose option B, and if you want to blame someone, blame me.
I really did not want to drag with us into 2025 an "improvisation" but rather start the year clean and focus on the more important stuff.
@sh97 said: Even after the latest update? I think they had a bunch of improvements recently.
NOP:
"Hi,
No, does not looks like it will be there in GUI since the plans are not server wise but the storage is server wise which can cause issues/conflicts in some cases.
Was the filter helpful in your case ?"
AA, no, it was not helpful, at least not yet.
PS::
Do not think that we do not know about what you all want, it is always a question of cost and is it technically possible.
Now I will own the cost part for now, but if it is not technically possible, I will not re-write software ( we are not that big for now ).
Remember the questions we asked ( to-to list ) ? well we listened, some will come sooner some later.
now, back to IPV6 ( I swear if I see another 2a0d:8XXX:0:eX:: I will throw up )
Folks, He is the reason we are putting you thru so much pain right now, so we do not get on the "Accepting submissions for IPv6 less than /64 Hall of Incompetence."
Folks, He is the reason we are putting you thru so much pain right now, so we do not get on the "Accepting submissions for IPv6 less than /64 Hall of Incompetence."
So @yoursunny is the reason why we don't have new deals...
Comments
For me it works since around 11 PM GMT+1 yesterday, but I didn't need to open a ticket.
cpu_logger | Recommended providers: Layer7, dataforest (Avoro/PHP-Friends), @host_c
@host_c you fixering the Yeti's crapola today?
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Please open a ticket, forum is NOT* a valid place to ask for a support.
/s
Haven't bought a single service in VirMach Great Ryzen 2022 - 2023 Flash Sale.
https://lowendspirit.com/uploads/editor/gi/ippw0lcmqowk.png
Flagging
Have no clue, I left STU to fix as much as he can. I am out of town.
He is going over services 1 by 1
I will join him tomorrow on this.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Tell STU that you will sell him to the Yeti if he fails!!!
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
told him.
Now, going back to tickets, only a few hundred services remaining to fix.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
For us IPv6 nerds (who manage IPv6 manually): should we power-off the server before or after opening a ticket? it's not clear in the mail.
Is there a time limit? What happens if we don't open a ticket by then? Service cancelled?
Nerds receive a ticket from us with the settings to set up
( "nerds" are identified by having custom install, 99% of the cases this is true, and most of them opened a ticket already )
All usual folks, we will set the new ip in cloud-init and issue a power-off / power on - they need to do nothing.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
@host_c thanks for the /64
Any quick quides to enable ipv6 on AlmaLinux 9?
Seems when I installed via iso only ipv4 is enabled by default
Thanks
nmtuiand off you go.dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/
Is there a way to use nmtui which would setup ipv6 like a dhcp does for ipv4? For me it is asking me to enter the details manually. Thnx
You can set IPv6 to "automatic" and see what happens... But it depends on the network whether it works or not.
dnscry.pt - Public DNSCrypt resolvers hosted by LowEnd providers • Need a free NAT LXC? -> https://microlxc.net/
DHCP will do nothing on our infrastructure.
There is no such service enabled.
Ip addresses are allocated / service by a provisioning module ( that started working as it should , hence the posibility to allocate a whole /64 rather rather then 1 /127 )
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
lets goooooooooooooooooooooooooooooooooo
I bench YABS 24/7/365 unless it's a leap year.
I am happy to report, we have a lot of 'nerds', much more then I anticipated. I am proud of you all
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
I might be wrong, but for a single IPv6 address, the subnet mask should be /128 right?
This incident should definitely be recorded in HOST-C's history.
not in our setup, this whole shit started ~1 year back.
Let me give you all an insight.
We used IP Manager 2 from ModulesGarden, at that was and is awesome for IPV4 but not for IPV6, it could not allocate a whole /64 ( from a /48 or any )
So we did a temporary work around, ( these usually bit you in the ass or in other sensitive places) by setting a /64 on each subnet we have, allocating a single IP from that /64 to customer ( as that worked in the module ) and wait out the update to IPMANAGER 3.
Update came ~2 months ago, but by that time we had give out a bunch of manually assigned /64's.
Each of these had :1 set up on the router and usually :2,3,4 for the customer - yeah, I know, lame, but it is what it is.
We ditched IP Manager 2 ~2 months ago ( that was fun as it was a ton of work so you all do not loos the already assigned ip's at the moment we selected disabled module).
And by the tests we did over the past 1 month we manage to implement the correct way to allocate a /64 from a /48 set up on each IPV4 subnet. ( all IPV4 subnets are separated at layer 2, each one has it's own broadcast domain and separate IPV6 GW + firewall stuff and other )
So when our ISP took out by mistake a /48 we used before for the old setup, I said to myself that this is as any good moment to do the implementation.
And here we are, modifying all to standard so we can ditch the " open a tiket for IPV6 /64 " and also this give us the following flexibility wise:
I know we are not winning loyalty points stopping your services, but we had 2 options on the table:
A. send out 500-600 E-mails so customers set up the new IPV6 setup or do a power off power on to auto apply the stings - all this when they read the email. - most probably this would taken 1 Decade
B. kill the old setup, we do all the work + some of you that have "nerd" setups - this will take ~1 week by our estimates.
I chose option B, and if you want to blame someone, blame me.
I really did not want to drag with us into 2025 an "improvisation" but rather start the year clean and focus on the more important stuff.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Sorry but I am still a bit confused.
From your previous offers:
As I did not request for a /64 previously, will my "1 Dedicated IPv6 IP" continue to work?
Or does it has to be replaced with a /64?
It will be replaced by a independent /64, for each customer
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Got it! Thanks.
ModulesGarden ugh
Free NAT KVM | Free NAT LXC | Bobr
ITS WEDNESDAY MY DUDES
Virtualizor does not have the possibility to provision add-on drive on install, so that is a no go for us, otherwise that was option 1.
EDIT:
An we tryed, trust me.
Still have it installed if they update the module.
https://virt-panel.host-c.com:4083
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Even after the latest update? I think they had a bunch of improvements recently.
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
NOP:
"Hi,
No, does not looks like it will be there in GUI since the plans are not server wise but the storage is server wise which can cause issues/conflicts in some cases.
Was the filter helpful in your case ?"
AA, no, it was not helpful, at least not yet.
PS::
Do not think that we do not know about what you all want, it is always a question of cost and is it technically possible.
Now I will own the cost part for now, but if it is not technically possible, I will not re-write software ( we are not that big for now ).
Remember the questions we asked ( to-to list ) ? well we listened, some will come sooner some later.
now, back to IPV6 ( I swear if I see another 2a0d:8XXX:0:eX:: I will throw up
)
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
VPS panels ranked, from best to worst:
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
@yoursunny
Perfect, you are here.
Folks, He is the reason we are putting you thru so much pain right now, so we do not get on the "Accepting submissions for IPv6 less than /64 Hall of Incompetence."
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
So @yoursunny is the reason why we don't have new deals...
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
in other words, yess
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"