bjo
bjo
About
- Username
- bjo
- Joined
- Visits
- 604
- Last Active
- Roles
- Member, OG
- Thanked
- 44
Comments
-
Glad I switched my backup box to @alwyzon
-
Same here with storage, but seems up again.
-
(Quote) But I moved around 2 TB :D
-
Seems like bandwidth accounting does not work any more. Stockholm storage is stuck at 300mb and Amsterdam has not used anything yet.
-
Seems like ICMP block. The last time fe80::1 did not reply was an indication that IPv6 connectivy was broken. But it works now.
-
Got a reply now (wow!) requesting to reconfigure the IPv6 address. Well, if fe80::1 is not pingable, that won't change anything...
-
No reply regarding the IPv6 issue since the storage outage since 2 days.
-
Same here: PING fe80::1(fe80::1) 56 data bytes^C--- fe80::1 ping statistics ---2 packets transmitted, 0 received, 100% packet loss, time 1024ms
-
Looking Glass available?
-
Support replied they had a hardware failure in Stockholm.
-
At leat the console is up again, so I can create a ticket regarding the boot issue.
-
It's a common 1TB storage box, no special LET offer.
-
The routing to NC is really, erm, interesting: HOST: store Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a0e:dc0:2::1 0.0% 10 26.2 17.8 9.4 26.2 5.7 2.|-- 2a02:6ea0:8:1070:5033::1 0.0% 10 …
-
They told me that a few dangling network filters had to be removed.
-
Besides that: fe80::1 still down.
-
The support said now: (Quote)
-
And IPv6 is down again with the new address.
-
Seems IPv4 and IPv6 switched to AS60068 / Datacamp/CDN77 as upstream. Edit: Ipv6 seems to switch between CDN77 and Portlane. Sometimes the firsthop is 2a00:1a28:1157::1, sometimes 2605:4840:ffff::1
-
Did they change it before?
-
Regarding their mail: some explanation would have been nice. Maybe I should move my borg backups to their ams location or to a storage box @mxmla
-
Don't know which tomorrow they ment. Maybe it's @cociu 's monday.
-
Last reply from HH: I am sorry for the inconvenience caused with the IPv6 issues. We will send out an email tomorrow with instructions and information regarding improving the IPv6 reliability in Stockholm.
-
Yesterday they asked if they could access the VM as they thought I have still issues. Some explanation what happened on 21.08. would be better.
-
(Quote) Do you have 2 IPv6 prefixes or only one?
-
I don't see the new prefix in your output.
-
I've deleted the old one now and activated the new one from 2a0e:dc0:2::/48 1.|-- 2a00:1a28:1157::1 0.0% 10 18.1 19.8 4.4 72.7 19.6 2.|-- fdca:f5d5:c3aa:cb2d::1 0.0% 10 8.0 14.5 3.4 58.5 16.4 3.|-- be-4-706.pe3…
-
(Quote) How? The docs says We do not support automatic (SLAAC) or dynamic (DHCPv6) IPv6 assignment
-
(Quote) 2a00:1a28:1157:yxz::/64 dev eth0 metric 256 fe80::/64 dev eth0 metric 256 default via fe80::1 dev eth0 metric 1024 multicast ff00::/8 dev eth0 metric 256 Got a reply to my ticket from the first outage which asked me to reconfigure acco…
-
"boot it back online" did not happen. Started it via control panel, IPv4 works, IPv6 are broken. IPv6-gateway is still 2a00:1a28:1157::1. Edit: Both up again.
-
Now down again since 22.12h CEST, within the announced timeslot.
-
For me both are working, but the gateway is from the old prefix.
-
I did not have any issues before.
-
And the outage began around 15:30 CEST or so, maybe @hosthatch srambled the dates and timezones?
-
(Quote) Well, it's still 21.08.23 CEST, not 22.08. The maintenance according to the announcement should be tomorrow.
-
(Quote) It's both? From Netcup: 3.|-- ae13-1386.RT.EQX.FKT.DE.r 0.0% 10 3.5 3.6 3.4 4.3 0.2 4.|-- RT.TC1.STO.SE.retn.net 0.0% 10 22.8 23.6 22.7 29.3 2.0 5.|-- GW-ObeNetwork.retn.net 0.0% 10 33.2 33.1 33.…
-
Old /64 seems up again OBE.
-
Tried bigger one now myself as I thought if it could replace a Netcup RS 1000 G9.5. It can't. Seems the same gambling as with the webtropia boxes. # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## Yet-Another-Bench-Script …
-
(Quote) Meerfarbig? A good choice as they have a PNI with my FTTH provider.
-
Which Transit provider is planned?