We will halt all sales for the next 24 hours due to the fact that the 3 newly published /48 ( that get divided into /64 for you ) are only partially visible on global BGP
Plus we have an issue with the old 2A0D:8140::/48 that our ISP accidentally removed from the filters rather then adding the new ones. - this is a more pressing issue
We will be back tomorrow, but first we need to fix our stuff
@host_c said:
We will halt all sales for the next 24 hours due to the fact that the 3 newly published /48 ( that get divided into /64 for you ) are only partially visible on global BGP
Plus we have an issue with the old 2A0D:8140::/48 that our ISP accidentally removed from the filters rather then adding the new ones. - this is a more pressing issue
We support providers that treat IPv6 as an essential service rather than secondary to IPv4.
It is honorable to halt sales when IPv6 isn't working.
@host_c said: Plus we have an issue with the old 2A0D:8140::/48 that our ISP accidentally removed from the filters rather then adding the new ones. - this is a more pressing issue
What's the current status of this more pressing issue? :P
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.
The output from ip a was the following:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX.255 scope global eth0 // allocated IPv4
valid_lft forever preferred_lft forever
inet6 2a0d:XXXX:XXXX:XXXX::XX/64 scope global // allocated IPv6
valid_lft forever preferred_lft forever
inet6 fe80::XXXX:XXXX:XXXX:XXXX/64 scope link // link-local address
valid_lft forever preferred_lft forever
inet6 2a0d:XXXX:0:4b:XXXX:XXXX:XXXX:XXXX/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft XXXXXXXsec preferred_lft XXXXXXsec
inet6 2a0d:XXXX:0:125:XXXX:XXXX:XXXX:XXXX/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft XXXXXXXsec preferred_lft XXXXXXsec
I have no idea where the last two addresses (on some of my VPSes from @host_c there were even more) come from, I have set net.ipv6.conf.all.autoconf, net.ipv6.conf.all.accept_ra and net.ipv6.conf.all.use_tempaddr all to 0 and DHCP was disabled.
When I deleted the two addresses with ip a del ADDRESS dev eth0, IPv6 worked from inside the VPS, but after a few seconds those addresses reappeared.
But after some time (I think around 11 PM GMT+1), the addresses weren't added anymore and IPv6 works since then.
(This is no criticism in any way, I'm just interested in how that happened.)
Now my question is: where did these addresses come from and could I have disabled that?
If this is too off-topic, mods can maybe move this post to the cest pit.
Since you push IPv6 automagically through Router Advertisements for most(?) customers, why not just simply provide the "new IPv6 settings" in the Control Panel (under "Assigned IPs"), for the few customers clever enough to manage IPv6 manually?
@Shot² said:
Since you push IPv6 automagically through Router Advertisements for most(?) customers, why not just simply provide the "new IPv6 settings" in the Control Panel (under "Assigned IPs"), for the few customers clever enough to manage IPv6 manually?
these will be available there.
but we have to update ~500+ services, I doubt 50 will set the up manually.
@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.
Comments
Chicken? I want chicken.
Chicken and rice with a hole?
Damned right I will don't make send out the phone spiders!!
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Weird hole right? I'm going to tell them to not make holes to my food.
I think the hole is to put sauce in?
Never. We don't do that.
Fellas,
We will halt all sales for the next 24 hours due to the fact that the 3 newly published /48 ( that get divided into /64 for you ) are only partially visible on global BGP
Plus we have an issue with the old 2A0D:8140::/48 that our ISP accidentally removed from the filters rather then adding the new ones. - this is a more pressing issue
We will be back tomorrow, but first we need to fix our stuff
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
@host_c fix my stuffs!!!!!!!!!!!!!!!!!
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
We support providers that treat IPv6 as an essential service rather than secondary to IPv4.
It is honorable to halt sales when IPv6 isn't working.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
Self rdns change would be cool.
Amadex • Hosting Forums • Wie ist meine IP-Adresse? • AS215325
Forum for System Administrators: sysadminforum.com
I will quote @imok
Rest assured that the "Marketing Department" has enough funds to sustain these crazy deals.
If you read the beginning of of this thread, I have stated that we have other measures of income also.
With that said, we will make some more
, on IPV6 only as that does lower the expense on this.
We tried to implement NAT64, but it did not go as expected , so we dropped it and focus on more important stuff.
We managed to fix the IPV6 problems ( almost all ) since last night so sales will resume shortly.
We need a little time-off by the way, so see you shortly.
HOST-C
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
LETS GO FAT32 SPECIAL DEAL
食之无味 弃之可惜 - Too arduous to relish, too wasteful to discard.
What's the current status of this more pressing issue? :P
So, will the crazy IPV6 storage VPS deal make a comeback?
yes
if you do not have connectivity by now, open a ticket, this goes for any of you reading this.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
I have multiple vps ipv6
ping ipv6.google.com
PING ipv6.google.com(sof02s48-in-x0e.1e100.net (2a00:1450:4017:811::200e)) 56 data bytes
Do I need to open a work order as well?
What is the output of
ip a?cpu_logger | Recommended providers: Layer7, dataforest (Avoro/PHP-Friends), @host_c
please do,1 ticket, and we will take it from there.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Tonight? or Now?
ticket
open a ticket so we can fix these, this is not the place.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Thank you for those that already did
we will issue an official statement via e-mail once we sort all out.
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
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.
The output from
ip awas the following:I have no idea where the last two addresses (on some of my VPSes from @host_c there were even more) come from, I have set
net.ipv6.conf.all.autoconf,net.ipv6.conf.all.accept_raandnet.ipv6.conf.all.use_tempaddrall to 0 and DHCP was disabled.When I deleted the two addresses with
ip a del ADDRESS dev eth0, IPv6 worked from inside the VPS, but after a few seconds those addresses reappeared.But after some time (I think around 11 PM GMT+1), the addresses weren't added anymore and IPv6 works since then.
(This is no criticism in any way, I'm just interested in how that happened.)
Now my question is: where did these addresses come from and could I have disabled that?
If this is too off-topic, mods can maybe move this post to the cest pit.
cpu_logger | Recommended providers: Layer7, dataforest (Avoro/PHP-Friends), @host_c
The RA announcement were Meade wrongly by us. In attempt to preserve old configuration and the new one for /64 allocation
Check your e-mail, we already announced that we will modify all services to /64 from /127
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Since you push IPv6 automagically through Router Advertisements for most(?) customers, why not just simply provide the "new IPv6 settings" in the Control Panel (under "Assigned IPs"), for the few customers clever enough to manage IPv6 manually?
When will the IPv6 network update be implemented?
these will be available there.
but we have to update ~500+ services, I doubt 50 will set the up manually.
It has already started. It will take some time .....
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
As a pain i the but this is for most of you, we wished tu finalize these ASAP, so we can all enjoy quiet holidays and other “stuff”
Host-C - VPS Services Provider - AS211462
"If there is no struggle there is no progress"
Keep up to good work man I for one appreciate it
Free Hosting at YetiNode | Cryptid Security | URL Shortener | LaunchVPS | ExtraVM | Host-C | In the Node, or Out of the Loop?
Is this fixed? I've been there as well. They resolved it by manually whitelisting my subnet.