@FrankZ said:
VirMach uses Equinix LA3 in El Segundo now for his Los Angeles location now. He recently moved out of QuadraNet Los Angeles. So tunnelbroker should work with @VirMach Los Angeles.
my node : LAX-A026
ip : 104.234.61.0/23
but Geo on Canada with isp QuadraNet
I expect that the geolocation service that you are using has not updated the AS to AS46261 which is QuickPacket not Quadranet.
I have a VM on node LAXA026 in IPv4 range 104.234.61.0/23 and just checked if tunnelbroker would allow a IPv6 tunnel to that VM.
It allowed it now, when in the past when it was at Quadranet it did not allow it. So you should be good to go.
EDIT: tunnelbroker may have had a change in policy and the statement above may no longer be accurate.
@FrankZ said:
VirMach uses Equinix LA3 in El Segundo now for his Los Angeles location now. He recently moved out of QuadraNet Los Angeles. So tunnelbroker should work with @VirMach Los Angeles.
my node : LAX-A026
ip : 104.234.61.0/23
but Geo on Canada with isp QuadraNet
I expect that the geolocation service that you are using has not updated the AS to AS46261 which is QuickPacket not Quadranet.
I have a VM on node LAXA026 in IPv4 range 104.234.61.0/23 and just checked if tunnelbroker would allow a IPv6 tunnel to that VM.
It allowed it now, when in the past when it was at Quadranet it did not allow it. So you should be good to go.
Aware. They'll be moved off at this point or to another disk. There's also still abuse, I need to wrap up LAXA004S first.
Hello my Virmach, i have sent an email to tunnelbroker.net to get an ipv6 tunnel but unfortunately it was rejected on the grounds that the ip of my node LAX-A026 already has native ipv6.
is there a solution for me to implement ipv6 on my service?
Any LESters have a VPS on CHIZ003 and if so are you experiencing issues? I am. When I run the Connection Troubleshooter in the client area:
Main Server IP: Offline
Node Server: Offline
Service Status: Active
Conclusion: Both your server and node appear to be offline. Please check the network status page for updates.
Aware. They'll be moved off at this point or to another disk. There's also still abuse, I need to wrap up LAXA004S first.
Hello my Virmach, i have sent an email to tunnelbroker.net to get an ipv6 tunnel but unfortunately it was rejected on the grounds that the ip of my node LAX-A026 already has native ipv6.
is there a solution for me to implement ipv6 on my service?
This seems to be something new from HE tunnelbroker. I expect they are allowing tunnels to still exist from IPv4 that have, or have had them in the past. Who know how long they will continue to allow this.
If this is HE tunnelbrokers new policy, that networks that announce IPv6 can not use tunnelbroker, this is going to be a problem.
I need to do some more digging on this and see if I can find an announcement from HE on what their policy is going to be going forward.
My apologies for the misinformation of my earlier statements. I have added a note so that others are not misinformed by them.
Knowledgebase articles on ticket submit removed as it was just annoying, buggy, and it's already basically replied with AI. Long overdue. If we integrate it back it'll be at the AI phase most likely.
Priority department removed (technically not fully, yet.) It'll be absorbed into the ticket creation process automatically.
Comments
I expect that the geolocation service that you are using has not updated the AS to AS46261 which is QuickPacket not Quadranet.
I have a VM on node LAXA026 in IPv4 range 104.234.61.0/23 and just checked if tunnelbroker would allow a IPv6 tunnel to that VM.
It allowed it now, when in the past when it was at Quadranet it did not allow it. So you should be good to go.
EDIT: tunnelbroker may have had a change in policy and the statement above may no longer be accurate.
many thanks Sir. i would open ticket on [email protected] 😀
Hello my Virmach, i have sent an email to tunnelbroker.net to get an ipv6 tunnel but unfortunately it was rejected on the grounds that the ip of my node LAX-A026 already has native ipv6.
is there a solution for me to implement ipv6 on my service?
Any LESters have a VPS on CHIZ003 and if so are you experiencing issues? I am. When I run the Connection Troubleshooter in the client area:
Main Server IP: Offline
Node Server: Offline
Service Status: Active
Conclusion: Both your server and node appear to be offline. Please check the network status page for updates.
This seems to be something new from HE tunnelbroker. I expect they are allowing tunnels to still exist from IPv4 that have, or have had them in the past. Who know how long they will continue to allow this.
If this is HE tunnelbrokers new policy, that networks that announce IPv6 can not use tunnelbroker, this is going to be a problem.
I need to do some more digging on this and see if I can find an announcement from HE on what their policy is going to be going forward.
My apologies for the misinformation of my earlier statements. I have added a note so that others are not misinformed by them.
by the way, what is the reason why virmach can't activate its native ipv6 ?
especially in the US region 😀
@VirMach, Ticket #401962 opened Feb.10th, please let me know one way or the other..
@VirMach screenshot dm'ed, can't contact Billing dept...
Knowledgebase articles on ticket submit removed as it was just annoying, buggy, and it's already basically replied with AI. Long overdue. If we integrate it back it'll be at the AI phase most likely.
Priority department removed (technically not fully, yet.) It'll be absorbed into the ticket creation process automatically.
Is node TYOC038 in problems or is just my vps offline in that node ?
AI replaced $15 tickets.
No hostname left!