Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
VDS.net
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
CloudLinux
MeduzaVPN
Servury - Anonymous & Privacy-focused VPS Hosting
Animated Silicon Kiwi cloud ad featuring VPS from $4.90/month, 100 GB S3 storage from $1.49/month, Kiwi Apps from $12/month and cloud backup from $3/month

Categories

In this Discussion

Home › General
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

HostDZire IPv6 Allocation Violation: Service Terminated After Configuration Error

13»

Comments

  • NotFoundExceptionNotFoundException Member

    @Flanker said: YOU ALREADY HAVE THE FULL IP LIST, SO STOP REPEATING THE SAME DEMAND AND EXPLAIN EXACTLY HOW THOSE IPS PROVE MALICIOUS INTENT RATHER THAN A CONFIGURATION MISTAKE!

    You wanted to hear what the community thinks about this. Why aren't you sharing these details? How could we tell you if this was valid when we don't know the scope?

    If it's something like 2001:0000:0001::/64 instead of 2001:0000:0002::/64 it's much more plausible that it was a mistake than if it was 2001:0000:0001::/64 instead of 3333:4444:5555::/64

    and tbh, you already have your answer, you fucked up, that's it, take the L

    Thanked by 1buggedout
  • defaultdefault Veteran

    @Flanker said:
    So yes, the root cause was an AI-assisted configuration mistake combined with my failure to verify the result. The responsibility is still mine.

    You answered your own poll. I am happy LET was of assistance in identifying the issue.

    @angstrom - maybe this thread has run its course.

  • tommyluotommyluo Member

    It seems to say,I am the end user,I am the god,even though I am wrong,you should correct me! Even you refund me,but I am still not happen with your action!

    Thanked by 1buggedout
  • cchlopscchlops Member

    @xvps said:

    @kintaro said:

    @Flanker said:

    @kintaro said:

    @Flanker said:

    @HostDZire said:

    @Flanker said:

    @HostDZire said:

    @Flanker said:

    @HostDZire said:

    @Flanker said:

    @tzuli said:

    @Flanker said:

    @tzuli said:
    I just realized it was FAT32 Special, ouch

    @Flanker said:

    I also requested cancellation and a refund for another active service, given that the provider had made it clear it no longer wanted to continue the customer relationship.

    The provider declined to refund that separate service.

    Was your other service a Leaseweb VPS?

    Yeah, To be fair, Leaseweb's hosting has been much more stable in my experience.

    I was just trying to understand why they would refund this service but not another, especially if they believe you're malicious. Makes more sense if the other service is through Leaseweb

    ;) From my perspective, if you've already decided that I'm a malicious customer and no longer welcome on your network, then why not just cancel and refund all my remaining services?

    We could simply part ways on good terms. You'd be making a generous gesture, and I wouldn't have to deal with a provider that clearly doesn't want me as a customer anymore.

    Instead, I'm apparently too "malicious" to keep one VPS, but perfectly acceptable to keep paying for another.

    That's the inconsistency I find difficult to understand.

    Abuse that one also and this time we will terminate without refund :)

    First, please define what you mean by "abuse" before throwing accusations around.

    Don't casually label someone as an abuser without distinguishing between an accidental misconfiguration and intentional malicious activity.

    On HostDZire's India VPS, it was apparently possible to configure unassigned IPv6 addresses and actually use them without being blocked by the network.

    I acknowledge that my IPv6 configuration was incorrect, and I take responsibility for that.

    But is an accidental Docker networking misconfiguration automatically considered malicious abuse simply because the provider's network allowed those addresses to work?

    A configuration violation and intentional malicious abuse are not necessarily the same thing. Please don't confuse the two.

    What is the list of IPs you were using? Which IP did we assign to you?

    What exactly are you trying to imply by asking this?

    I've already acknowledged in the support ticket that I mistakenly configured IPv6 addresses outside my assigned allocation. I've never denied that, and I've taken responsibility for the misconfiguration.

    You've also already provided the list of those addresses in the ticket, so I'm not sure what repeating that information here is supposed to establish.

    My question is simple: Does accidentally configuring IPv6 addresses outside the assigned /64 automatically constitute malicious abuse in your view?

    I'm not disputing that it was a configuration violation. I'm asking you to distinguish between a technical misconfiguration and intentional malicious activity.

    Please address that distinction rather than implying that I've been denying something I've already admitted.

    Just give screenshots of the reply I sent you in the ticket, where I gave you the list of IPs you were using.

    What exactly is the point of this request? What are you trying to prove?

    You've already provided the list of IPs in the support ticket, and I've already acknowledged that I mistakenly configured addresses outside my assigned allocation.

    I'm not denying the facts, so what exactly would posting the same screenshots again establish?

    If your intention is to prove that unauthorized IPv6 addresses were configured, we already agree on that.

    But if you're trying to use that list as proof of malicious intent, then please explain how it establishes intent rather than simply confirming a configuration violation.

    That's the distinction I've been asking you to address all along.

    I think hes most likely implying the IPs you have used were not even close to the range that was assigned

    Yes, that's essentially what happened.

    I mistakenly configured IPv6 addresses from a completely different range, well outside my assigned allocation. However, the network connectivity actually worked, so I didn't notice anything unusual at the time.

    That was my incorrect assumption and my configuration mistake. I take full responsibility for it and have never denied that.

    I'm not trying to justify the misconfiguration. I'm simply explaining how it happened.

    So you knew you had assigned IPs you shouldnt have and "assumed" it was fine.

    No, he is writing that he by accident used the wrong IPs, and since it worked he didn't noticed anything wrong.

    His point is clear: once I decide you acted intentionally, don't bother explaining—I have the power to terminate the service, and you are simply the one on the receiving end. Perhaps their service has always been this way—much like a passerby accidentally damaging a concrete surface; regardless of whether it was intentional, I would assume it was and proceed to mock you mercilessly.

  • rcy026rcy026 Member

    @Flanker said:

    YOU ALREADY HAVE THE FULL IP LIST, SO STOP REPEATING THE SAME DEMAND AND EXPLAIN EXACTLY HOW THOSE IPS PROVE MALICIOUS INTENT RATHER THAN A CONFIGURATION MISTAKE!

    He might have the full list but we don't and he cant really show it to us without breaking a lot of rules. You on the other hand can show the list and that's probably why he keeps asking for it, but something tells me that the list shows something you do not want to be seen.

  • x0x0xx0x0x Member

    @Flanker said: the root cause was an AI-assisted configuration mistake combined with my failure to verify the result. The responsibility is still mine

    Thanked by 4NotFoundException buggedout mans_xd rpqu
  • deafcondeafcon Member

    What are the chances that this entire thing is because the user configured some stupid vanity IP with b00b or c0de in it?

  • FlankerFlanker Member

    @rcy026 said:

    @Flanker said:

    YOU ALREADY HAVE THE FULL IP LIST, SO STOP REPEATING THE SAME DEMAND AND EXPLAIN EXACTLY HOW THOSE IPS PROVE MALICIOUS INTENT RATHER THAN A CONFIGURATION MISTAKE!

    He might have the full list but we don't and he cant really show it to us without breaking a lot of rules. You on the other hand can show the list and that's probably why he keeps asking for it, but something tells me that the list shows something you do not want to be seen.

    Here is the IP list provided by HostDZire in the support ticket
    XXXX:XXXX:XXXX:0000:0000:0000:2686:0001 XX:XX:XX:XX:XX:XX - Assigned
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0002 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0008 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0009 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:000C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:000F XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0014 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0015 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0016 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0017 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0018 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0019 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001A XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001B XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001D XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001E XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0026 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0029 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002D XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002E XX:XX:XX:XX:XX:XX - Unauthorised

    as far as I remember, the control panel showed an IPv6 /64 allocation.

  • defaultdefault Veteran

    Thanked by 1buggedout
  • ailiceailice Member

    What amazing about it, bro just give full access clanker configuration their VPS and "assumed" by check got internet connection.
    Why ~MJJ~people not learning for it

  • deafcondeafcon Member

    @Flanker said:

    @rcy026 said:

    @Flanker said:

    YOU ALREADY HAVE THE FULL IP LIST, SO STOP REPEATING THE SAME DEMAND AND EXPLAIN EXACTLY HOW THOSE IPS PROVE MALICIOUS INTENT RATHER THAN A CONFIGURATION MISTAKE!

    He might have the full list but we don't and he cant really show it to us without breaking a lot of rules. You on the other hand can show the list and that's probably why he keeps asking for it, but something tells me that the list shows something you do not want to be seen.

    Here is the IP list provided by HostDZire in the support ticket
    XXXX:XXXX:XXXX:0000:0000:0000:2686:0001 XX:XX:XX:XX:XX:XX - Assigned
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0002 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0008 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0009 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:000C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:000F XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0014 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0015 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0016 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0017 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0018 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0019 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001A XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001B XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001D XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:001E XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0026 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:0029 XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002C XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002D XX:XX:XX:XX:XX:XX - Unauthorised
    XXXX:XXXX:XXXX:0000:CAFE:0000:0000:002E XX:XX:XX:XX:XX:XX - Unauthorised

    as far as I remember, the control panel showed an IPv6 /64 allocation.

    Nah dog. Codex didn't do that.

    Thanked by 4NotFoundException buggedout HostDZire default
  • defaultdefault Veteran
    edited 2:24PM

    This is becoming an IPv6 debate, so we might need to summon @yoursunny at this point.

  • FlankerFlanker Member

  • xvpsxvps Member

    TL;DR

    HostDZire kicked a mjj down the stairs.
    It was wong at so many levels.

    Thanked by 3mans_xd buggedout HostDZire
  • x0x0xx0x0x Member

    @Flanker said: s far as I remember

    Thanked by 1mans_xd
  • rpqurpqu Member

    🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣

    Thanked by 2buggedout HostDZire
  • defaultdefault Veteran

    @xvps said:
    TL;DR

    HostDZire kicked a mjj down the stairs.
    It was wong at so many levels.

    MJJ lives matter.

    Thanked by 2buggedout HostDZire
  • JasonMJasonM Member

    HostDzire's infrastructure seems really really un-secured and lame. Anybody can use any resources, hack them and do all nasty things.

    But I will side with OP. If it was not a deliberate action then OP needs to be given a chance AND not taken his VPS back. But still its the decision of the host to do business or not with OP and glad that they refunded whatever left.

    I remember something like ~15 years ago when I was with HVH, I could access their all customers folders via ftp (due to their own security failure). The moment I came across this I wrote and informed them to patch it. That's it. they just thankd me. Issue closed.

    Thanked by 7inaba rpqu Flanker buggedout drunkendog Nekopara Incognion
  • ObelousObelous Member

    I really can't be fucked reading all that so I just clicked your fault on the poll.

  • TimboJonesTimboJones Member

    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

  • FlankerFlanker Member

    @TimboJones said:
    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

    Thanks for the constructive feedback. Very helpful. /s

  • deafcondeafcon Member

    @Flanker said:

    @TimboJones said:
    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

    Thanks for the constructive feedback. Very helpful. /s

    I don't think you should be banned, but it's bullshit that you came here and lied about what happened. You very obviously stole those IPs simply because you could. If you're going to do shady shit, don't come here blaming the vendor when you get your hand slapped.

    I don't think HostD is free from blame here. I hope that they indeed are trying to clean up their security, and that's how this issue was found. I hope to stay a happy customer for a long time, but some of the security issues that have occurred in the last few months are concerning.

  • kkonekokkoneko Member

    @Flanker said:

    I was using Codex with MCP tools to configure the network. I only provided the AI agent with my assigned IPv6 /64 prefix and let it handle the configuration.

    AHAHAHAHAHAHAHAH

    Codex configure my VPS and make billions, make no mistake.

    What a clown.

  • TimboJonesTimboJones Member

    @Flanker said:

    @TimboJones said:
    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

    Thanks for the constructive feedback. Very helpful. /s

    You fucked up. You know it's your fault and yet expect no penalty and wasted time and resources of the provider and taking away time that could have been spent dealing with other customer's legit issues.

    You're an entitled snowflake with zero self-awareness. There's no "constructive feedback" that you won't ignore, because, again, you're a fucking snowflake. As evidenced by your idiotic OP.

    You asked, and now complaining about the answers.

    Fucking snowflake.

  • FlankerFlanker Member

    @deafcon said:

    @Flanker said:

    @TimboJones said:
    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

    Thanks for the constructive feedback. Very helpful. /s

    I don't think you should be banned, but it's bullshit that you came here and lied about what happened. You very obviously stole those IPs simply because you could. If you're going to do shady shit, don't come here blaming the vendor when you get your hand slapped.

    I don't think HostD is free from blame here. I hope that they indeed are trying to clean up their security, and that's how this issue was found. I hope to stay a happy customer for a long time, but some of the security issues that have occurred in the last few months are concerning.

    I think you've misunderstood what actually happened.

    I didn't knowingly "steal" any IPs. I used Codex with MCP tools to configure Docker networking, provided my assigned IPv6 /64 information, and the resulting configuration worked. I didn't discover the incorrect addresses until the suspension ticket arrived.

    I've openly acknowledged that I failed to verify the configuration. That's my responsibility, and I've never denied it.

    But there's an important distinction between using unauthorized IPs and knowingly stealing them. The former happened; the latter is your assumption, not an established fact.

    I'm also not blaming the provider for my mistake. My criticism has always been about how the situation was handled and the repeated accusations of deliberate abuse.

    You can disagree with me, but please don't misrepresent what I've said.

    What's done is done, and the matter is already settled.

    At this point, the only real question is whether I intentionally and knowingly "stole" those IPs, or whether it was an unintentional configuration mistake.

    I've acknowledged my responsibility for the misconfiguration from the beginning. What I refuse to accept is having malicious intent attributed to me without evidence.

    and honestly, none of this really matters anymore.

  • FlankerFlanker Member

    @TimboJones said:

    @Flanker said:

    @TimboJones said:
    Ban OP. Also, let other providers know he's a support nuisance.

    Fucking snowflake.

    Thanks for the constructive feedback. Very helpful. /s

    You fucked up. You know it's your fault and yet expect no penalty and wasted time and resources of the provider and taking away time that could have been spent dealing with other customer's legit issues.

    You're an entitled snowflake with zero self-awareness. There's no "constructive feedback" that you won't ignore, because, again, you're a fucking snowflake. As evidenced by your idiotic OP.

    You asked, and now complaining about the answers.

    Fucking snowflake.

    nice guy.

Sign In or Register to comment.