v6Node Status / Changelog thread

iandk

Hey there!

We wanted to use this thread in order to keep you up to date with our newest developments and get some feedback for our next features!

iandk

Migration to Frankfurt

Last December, we began preparing our new location in Frankfurt am Main, which is intended to replace both Falkenstein and Nuremberg.
The installation of our infrastructure and networking equipment went flawlessly, but we soon started experiencing issues with our network connection.

It all started with occasional package loss, combined with lower than usual download/upload rates. We spent quite some time with our upstream provider (23M) to debug the issue, and thought we had solved it when they reported that the uplink we received to their core router seemed to be faulty. They assigned us a new port, and the issue disappeared.

However, a few weeks later, we started to see the same issue again. This time, it occurred randomly, and sometimes affected the upload speed, and sometimes the download speed.

Additionally, only some providers were affected. While testing with usual YABS iPerf3 targets, we sometimes saw results like 10-20 Mbit/s download to most providers, while still maintaining a solid 8 Gbit/s both ways to Novoserve.

We can rule out our side as a potential issue since it works flawlessly when we obtain external transit via our recently deployed crossconnect. However, our upstream still refuses to admit any issues on their side. They informed us yesterday that they will stop investigating as they cannot find any problems on their end.

This leaves us with two options which we are evaluating at the moment:

Stay with our current provider but only obtain the rack space from them and build out our own network, using it exclusively
Switch to a different facility where we would obtain rack space + transit and gradually build out our own network with a diverse upstream blend
We will most likely choose option two, but we are still evaluating our options.

I deeply apologize to all customers who have been affected by this situation, especially our preorder supporters.

We had planned for potential issues, but we were not expecting anything like this. Some preorders have already been fulfilled during a phase where we believed the issue was resolved, while others are still pending.

We can deploy the remaining preorders now, but we must warn you that the issue is still occurring randomly.

We are working as hard as we can to resolve this as soon as possible.

Thanks!
Ian

ehab

i have noticed network bursts and slowdowns.

Thanks for the update thou. and I have mine deployed already few days ago.

Encoders

i didn't use v6 as my vps provider, but seeing these kind of write-up are fun. you can also partially learn the approach to solve a certain problem. having someone else giving feedback are just the bonus

iandk

@ehab said:
i have noticed network bursts and slowdowns.

Thanks for the update thou. and I have mine deployed already few days ago.

Yea it's a shame.
But I am confident that we will sort this out in the coming days

mikho

moved it to the Industry News category.

Jab

So that explain why it was so quiet from you lately - like last offer was December iirc?

iandk

Yea we’ve been busy troubleshooting most of the time.
The few remaining hours went into the development of some upcoming features for the backend

But I’m sure there’ll be another offer once this has been finally sorted out

RendeRR

Port forwarding does not work and no one answers in support (

Jab

@RendeRR said:
Port forwarding does not work and no one answers in support (

Please show ticket.

also little confused - I don't recall v6node offering any NAT services that you would need to configure port forwarding in theirs panel (?)

sh97

@Jab said:

@RendeRR said:
Port forwarding does not work and no one answers in support (

Please show ticket.

also little confused - I don't recall v6node offering any NAT services that you would need to configure port forwarding in theirs panel (?)

The Hetzener based VMs are NAT, I used to have one.

RendeRR

@Jab said:

@RendeRR said:
Port forwarding does not work and no one answers in support (

Please show ticket.

also little confused - I don't recall v6node offering any NAT services that you would need to configure port forwarding in theirs panel (?)

They don't have a ticket system, just "We have received your message and will contact you shortly" to email and that's it.

Port forwarding for ipv4.

iandk

Can you DM me your mail address?
I'll have a look but I don't see any open tickets regarding mentioning port forwarding.

And yes, the automatic creation on the backend is currently unavailable and has to be done via ticket, this is due to the upcoming migration to Frankfurt.
The notification will be sent out tomorrow

RendeRR

Hello. Any news about migration?

iandk

@RendeRR said:
Hello. Any news about migration?

We sent out the mails earlier today

adef_1

We regret to inform you that due to frequent past abuses, we are currently unable to continue offering Shared IPv4 in Frankfurt. On a positive note, we can now provide Dedicated IPv4 addresses at a rate of €0.8 per month. Additionally, each Node will now come standard with a /56 IPv6 subnet.

What a pity.

iandk

@adef_1 said:

We regret to inform you that due to frequent past abuses, we are currently unable to continue offering Shared IPv4 in Frankfurt. On a positive note, we can now provide Dedicated IPv4 addresses at a rate of €0.8 per month. Additionally, each Node will now come standard with a /56 IPv6 subnet.

What a pity.

I'd love to continue offering it, but pretty much all abuse we've seen so far originated from Shared IPv4.

yoursunny

@iandk said:

@adef_1 said:

We regret to inform you that due to frequent past abuses, we are currently unable to continue offering Shared IPv4 in Frankfurt. On a positive note, we can now provide Dedicated IPv4 addresses at a rate of €0.8 per month. Additionally, each Node will now come standard with a /56 IPv6 subnet.

What a pity.

I'd love to continue offering it, but pretty much all abuse we've seen so far originated from Shared IPv4.

Throttle the shared IPv4:

• 1 Mbps per second
• 5 new incoming connections every 30 seconds
• enforce destination IP allowlist for outgoing connections: the user may request an IP to be added to allowlist only if they control the destination IP, which can be demonstrated by having them curl your API server from the destination IP

Neoon

@iandk said:

@adef_1 said:

We regret to inform you that due to frequent past abuses, we are currently unable to continue offering Shared IPv4 in Frankfurt. On a positive note, we can now provide Dedicated IPv4 addresses at a rate of €0.8 per month. Additionally, each Node will now come standard with a /56 IPv6 subnet.

What a pity.

I'd love to continue offering it, but pretty much all abuse we've seen so far originated from Shared IPv4.

Depending on abuse type, configure something like pmacctd, wait for a abuse, check logs, terminate user, go buy yourself something, like a box of beer.

RendeRR

No ipv6 == no ssh?)

iandk

@RendeRR said:
No ipv6 == no ssh?)

Drop me a PM with your registered email and we'll figure something out