#init7 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #init7, aggregated by home.social.
-
Das Rating erinnert mich an das Telekom Rating, das meistens der nicht Zahlende gewonnen hat... 😀
https://www.bilanz.ch/bilanz-sucht-die-besten-telekom-anbieter/b2c6c51
-
Das Rating erinnert mich an das Telekom Rating, das meistens der nicht Zahlende gewonnen hat... 😀
https://www.bilanz.ch/bilanz-sucht-die-besten-telekom-anbieter/b2c6c51
-
Das Rating erinnert mich an das Telekom Rating, das meistens der nicht Zahlende gewonnen hat... 😀
https://www.bilanz.ch/bilanz-sucht-die-besten-telekom-anbieter/b2c6c51
-
Das Rating erinnert mich an das Telekom Rating, das meistens der nicht Zahlende gewonnen hat... 😀
https://www.bilanz.ch/bilanz-sucht-die-besten-telekom-anbieter/b2c6c51
-
Das Rating erinnert mich an das Telekom Rating, das meistens der nicht Zahlende gewonnen hat... 😀
https://www.bilanz.ch/bilanz-sucht-die-besten-telekom-anbieter/b2c6c51
-
@tschaefer @JulianOliver: My #IPv6 /48 range at home is native: https://www.init7.net/en/support/faq/Statischer-IPv6-Range/
I could also get a static IPv4 address for some extra money, but it's not worth it anymore — static IPv6 suffices completely.
-
Falls jemand noch einen neuen Internetprivider sucht, #init7 kann ich nicht nur deswegen sehr empfehlen. 😊
https://www.republik.ch/2026/04/14/netzsperren-die-grossen-kuschen-der-rebell-kaempft
-
Falls jemand noch einen neuen Internetprivider sucht, #init7 kann ich nicht nur deswegen sehr empfehlen. 😊
https://www.republik.ch/2026/04/14/netzsperren-die-grossen-kuschen-der-rebell-kaempft
-
Falls jemand noch einen neuen Internetprivider sucht, #init7 kann ich nicht nur deswegen sehr empfehlen. 😊
https://www.republik.ch/2026/04/14/netzsperren-die-grossen-kuschen-der-rebell-kaempft
-
Falls jemand noch einen neuen Internetprivider sucht, #init7 kann ich nicht nur deswegen sehr empfehlen. 😊
https://www.republik.ch/2026/04/14/netzsperren-die-grossen-kuschen-der-rebell-kaempft
-
#init7 bei Cory Doctorow 😀 - „Switzerland’s Goldilocks fiber“ - beide Artikel lesenswert, auch die Quelle (Stefan Schüller). Dasselbe würde für Mobilfunknetze gelten, aber das hat leider auch die Schweiz nicht geschafft.
https://pluralistic.net/2026/04/07/swisscom/ -
#init7 bei Cory Doctorow 😀 - „Switzerland’s Goldilocks fiber“ - beide Artikel lesenswert, auch die Quelle (Stefan Schüller). Dasselbe würde für Mobilfunknetze gelten, aber das hat leider auch die Schweiz nicht geschafft.
https://pluralistic.net/2026/04/07/swisscom/ -
Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.
Tonight, my IPv6 connection to the internet went away.
https://as13030.net/status/?ticket=42375121
Is «IPv4 only» the new reliability? 🤔
Did I miss something? 😉 -
Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.
Tonight, my IPv6 connection to the internet went away.
https://as13030.net/status/?ticket=42375121
Is «IPv4 only» the new reliability? 🤔
Did I miss something? 😉 -
Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.
Tonight, my IPv6 connection to the internet went away.
https://as13030.net/status/?ticket=42375121
Is «IPv4 only» the new reliability? 🤔
Did I miss something? 😉 -
Tonight my service provider Init7 had a maintenance to improve performance and reliability of the network in the greater area of Bern.
Tonight, my IPv6 connection to the internet went away.
https://as13030.net/status/?ticket=42375121
Is «IPv4 only» the new reliability? 🤔
Did I miss something? 😉 -
-
-
-
-
-
An interesting problem when using #OpenBSD 7.8 with PPPoE over the Swisscom VDSL wholesale servce via #Init7. The PPPoE setup is bog standard as per the man page:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
pppoedev igc0 authproto chap \
authname ''xxx" authkey 'xxx' \
up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp \$if 0.0.0.1
!/sbin/route add -inet6 default -ifp \$if fe80::%\$ifEver since upgrading I have had two PPPoE "hangs" where suddenly pppoe reports that it has LCP timeouts:
Feb 12 11:32:09 gw-gva /bsd: pppoe0: LCP keepalive timeout
Feb 12 11:36:41 gw-gva /bsd: pppoe0: LCP keepalive timeoutand the connection is down. A tcpdump on the underlying interface shows traffic flowing (!!) but the interface shows that it is unauthenticated.
When it happened first, on 2nd January 2026, I opened a ticket with Init7 and we had a serious look at it as we thought this was Swisscom.
It turned out that my system had not authenticated with the VDSL for over a month so the connection was closed (!!).
Rebooting the firewall made it work immediately.
It just happened again now, the symptoms are identical to the ones in January so I tried taking the interface down with "ifconfig destroy" and up again but that didn't seem to work so I rebooted and bam, I'm back.
This _seems_ to be a novel issue with 7.8 but I am unsure of what other checks I could run, for sure 7.7 was up continuously since the upgrade from 7.6 except for kernel patches.
There is a mention on Reddit which might be tangential to it (or just a bad report):
https://www.reddit.com/r/openbsd/comments/1oi93on/trouble_with_pppoe_in_openbsd_78/
-
An interesting problem when using #OpenBSD 7.8 with PPPoE over the Swisscom VDSL wholesale servce via #Init7. The PPPoE setup is bog standard as per the man page:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
pppoedev igc0 authproto chap \
authname ''xxx" authkey 'xxx' \
up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp \$if 0.0.0.1
!/sbin/route add -inet6 default -ifp \$if fe80::%\$ifEver since upgrading I have had two PPPoE "hangs" where suddenly pppoe reports that it has LCP timeouts:
Feb 12 11:32:09 gw-gva /bsd: pppoe0: LCP keepalive timeout
Feb 12 11:36:41 gw-gva /bsd: pppoe0: LCP keepalive timeoutand the connection is down. A tcpdump on the underlying interface shows traffic flowing (!!) but the interface shows that it is unauthenticated.
When it happened first, on 2nd January 2026, I opened a ticket with Init7 and we had a serious look at it as we thought this was Swisscom.
It turned out that my system had not authenticated with the VDSL for over a month so the connection was closed (!!).
Rebooting the firewall made it work immediately.
It just happened again now, the symptoms are identical to the ones in January so I tried taking the interface down with "ifconfig destroy" and up again but that didn't seem to work so I rebooted and bam, I'm back.
This _seems_ to be a novel issue with 7.8 but I am unsure of what other checks I could run, for sure 7.7 was up continuously since the upgrade from 7.6 except for kernel patches.
There is a mention on Reddit which might be tangential to it (or just a bad report):
https://www.reddit.com/r/openbsd/comments/1oi93on/trouble_with_pppoe_in_openbsd_78/
-
An interesting problem when using #OpenBSD 7.8 with PPPoE over the Swisscom VDSL wholesale servce via #Init7. The PPPoE setup is bog standard as per the man page:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
pppoedev igc0 authproto chap \
authname ''xxx" authkey 'xxx' \
up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp \$if 0.0.0.1
!/sbin/route add -inet6 default -ifp \$if fe80::%\$ifEver since upgrading I have had two PPPoE "hangs" where suddenly pppoe reports that it has LCP timeouts:
Feb 12 11:32:09 gw-gva /bsd: pppoe0: LCP keepalive timeout
Feb 12 11:36:41 gw-gva /bsd: pppoe0: LCP keepalive timeoutand the connection is down. A tcpdump on the underlying interface shows traffic flowing (!!) but the interface shows that it is unauthenticated.
When it happened first, on 2nd January 2026, I opened a ticket with Init7 and we had a serious look at it as we thought this was Swisscom.
It turned out that my system had not authenticated with the VDSL for over a month so the connection was closed (!!).
Rebooting the firewall made it work immediately.
It just happened again now, the symptoms are identical to the ones in January so I tried taking the interface down with "ifconfig destroy" and up again but that didn't seem to work so I rebooted and bam, I'm back.
This _seems_ to be a novel issue with 7.8 but I am unsure of what other checks I could run, for sure 7.7 was up continuously since the upgrade from 7.6 except for kernel patches.
There is a mention on Reddit which might be tangential to it (or just a bad report):
https://www.reddit.com/r/openbsd/comments/1oi93on/trouble_with_pppoe_in_openbsd_78/
-
An interesting problem when using #OpenBSD 7.8 with PPPoE over the Swisscom VDSL wholesale servce via #Init7. The PPPoE setup is bog standard as per the man page:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
pppoedev igc0 authproto chap \
authname ''xxx" authkey 'xxx' \
up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp \$if 0.0.0.1
!/sbin/route add -inet6 default -ifp \$if fe80::%\$ifEver since upgrading I have had two PPPoE "hangs" where suddenly pppoe reports that it has LCP timeouts:
Feb 12 11:32:09 gw-gva /bsd: pppoe0: LCP keepalive timeout
Feb 12 11:36:41 gw-gva /bsd: pppoe0: LCP keepalive timeoutand the connection is down. A tcpdump on the underlying interface shows traffic flowing (!!) but the interface shows that it is unauthenticated.
When it happened first, on 2nd January 2026, I opened a ticket with Init7 and we had a serious look at it as we thought this was Swisscom.
It turned out that my system had not authenticated with the VDSL for over a month so the connection was closed (!!).
Rebooting the firewall made it work immediately.
It just happened again now, the symptoms are identical to the ones in January so I tried taking the interface down with "ifconfig destroy" and up again but that didn't seem to work so I rebooted and bam, I'm back.
This _seems_ to be a novel issue with 7.8 but I am unsure of what other checks I could run, for sure 7.7 was up continuously since the upgrade from 7.6 except for kernel patches.
There is a mention on Reddit which might be tangential to it (or just a bad report):
https://www.reddit.com/r/openbsd/comments/1oi93on/trouble_with_pppoe_in_openbsd_78/
-
An interesting problem when using #OpenBSD 7.8 with PPPoE over the Swisscom VDSL wholesale servce via #Init7. The PPPoE setup is bog standard as per the man page:
inet 0.0.0.0 255.255.255.255 NONE mtu 1500 \
pppoedev igc0 authproto chap \
authname ''xxx" authkey 'xxx' \
up
dest 0.0.0.1
inet6 eui64
!/sbin/route add default -ifp \$if 0.0.0.1
!/sbin/route add -inet6 default -ifp \$if fe80::%\$ifEver since upgrading I have had two PPPoE "hangs" where suddenly pppoe reports that it has LCP timeouts:
Feb 12 11:32:09 gw-gva /bsd: pppoe0: LCP keepalive timeout
Feb 12 11:36:41 gw-gva /bsd: pppoe0: LCP keepalive timeoutand the connection is down. A tcpdump on the underlying interface shows traffic flowing (!!) but the interface shows that it is unauthenticated.
When it happened first, on 2nd January 2026, I opened a ticket with Init7 and we had a serious look at it as we thought this was Swisscom.
It turned out that my system had not authenticated with the VDSL for over a month so the connection was closed (!!).
Rebooting the firewall made it work immediately.
It just happened again now, the symptoms are identical to the ones in January so I tried taking the interface down with "ifconfig destroy" and up again but that didn't seem to work so I rebooted and bam, I'm back.
This _seems_ to be a novel issue with 7.8 but I am unsure of what other checks I could run, for sure 7.7 was up continuously since the upgrade from 7.6 except for kernel patches.
There is a mention on Reddit which might be tangential to it (or just a bad report):
https://www.reddit.com/r/openbsd/comments/1oi93on/trouble_with_pppoe_in_openbsd_78/
-
RE: https://digitalcourage.social/@f09fa681/115655671178416133
Soeben habe ich entdeckt, dass ich mich auch im PlayStation Network nicht einloggen kann. Auf dem Mac funktioniert es. Verhält sich also exakt gleich wie die Webseite der #Bahn.
Sony geschenkt - Saftladen. Aber hat die #Bahn echt so eine shady Systemreputationsbewertungsscheisse nötig?
Mal #init7 gefragt, wie ich meine IPv4 forciert wechseln kann. Hab langsam genug.
-
RE: https://digitalcourage.social/@f09fa681/115655671178416133
Soeben habe ich entdeckt, dass ich mich auch im PlayStation Network nicht einloggen kann. Auf dem Mac funktioniert es. Verhält sich also exakt gleich wie die Webseite der #Bahn.
Sony geschenkt - Saftladen. Aber hat die #Bahn echt so eine shady Systemreputationsbewertungsscheisse nötig?
Mal #init7 gefragt, wie ich meine IPv4 forciert wechseln kann. Hab langsam genug.
-
RE: https://digitalcourage.social/@f09fa681/115655671178416133
Soeben habe ich entdeckt, dass ich mich auch im PlayStation Network nicht einloggen kann. Auf dem Mac funktioniert es. Verhält sich also exakt gleich wie die Webseite der #Bahn.
Sony geschenkt - Saftladen. Aber hat die #Bahn echt so eine shady Systemreputationsbewertungsscheisse nötig?
Mal #init7 gefragt, wie ich meine IPv4 forciert wechseln kann. Hab langsam genug.
-
RE: https://digitalcourage.social/@f09fa681/115655671178416133
Soeben habe ich entdeckt, dass ich mich auch im PlayStation Network nicht einloggen kann. Auf dem Mac funktioniert es. Verhält sich also exakt gleich wie die Webseite der #Bahn.
Sony geschenkt - Saftladen. Aber hat die #Bahn echt so eine shady Systemreputationsbewertungsscheisse nötig?
Mal #init7 gefragt, wie ich meine IPv4 forciert wechseln kann. Hab langsam genug.
-
"Wollen Sie zu einem lokalen Spiegelserver wechseln?"
Jaaaa! (danke weiterhin für den Mirror, #Init7 ♥️ ) -
"Wollen Sie zu einem lokalen Spiegelserver wechseln?"
Jaaaa! (danke weiterhin für den Mirror, #Init7 ♥️ ) -
"Wollen Sie zu einem lokalen Spiegelserver wechseln?"
Jaaaa! (danke weiterhin für den Mirror, #Init7 ♥️ ) -
"Wollen Sie zu einem lokalen Spiegelserver wechseln?"
Jaaaa! (danke weiterhin für den Mirror, #Init7 ♥️ ) -
"Wollen Sie zu einem lokalen Spiegelserver wechseln?"
Jaaaa! (danke weiterhin für den Mirror, #Init7 ♥️ ) -
I recently acquired a new Turris Omnia NG router from @turris to take advantage of my new 10 Gbit/s internet speed from my provider Init7. Now I was really curious about my actual speed ...
This led me to LibreSpeed (https://github.com/librespeed), an Open Source speed test tool which is working by default with PHP. Unfortunately the router isn't powerful to provide reasonable measurements because the chunk files to test the download speed are generated by PHP and openssl. This appeared to be a bottleneck.
So I was tinkering a little bit and created a NGINX backend for LibreSpeed which doesn't rely on PHP.
Now I have put together this in a GitHub comment: https://github.com/librespeed/speedtest/issues/375#issuecomment-3769211254
(I still rely on PHP to get the IP address and to store the measurements though, but this is lightweight enough for the router.)
Try it out yourself: https://speedtest.momou.ch
#speedtest #Internet #OpenSource #LibreSpeed #PHP #measure #tinkering #nginx #turris #omnia #Init7
-
I recently acquired a new Turris Omnia NG router from @turris to take advantage of my new 10 Gbit/s internet speed from my provider Init7. Now I was really curious about my actual speed ...
This led me to LibreSpeed (https://github.com/librespeed), an Open Source speed test tool which is working by default with PHP. Unfortunately the router isn't powerful to provide reasonable measurements because the chunk files to test the download speed are generated by PHP and openssl. This appeared to be a bottleneck.
So I was tinkering a little bit and created a NGINX backend for LibreSpeed which doesn't rely on PHP.
Now I have put together this in a GitHub comment: https://github.com/librespeed/speedtest/issues/375#issuecomment-3769211254
(I still rely on PHP to get the IP address and to store the measurements though, but this is lightweight enough for the router.)
Try it out yourself: https://speedtest.momou.ch
#speedtest #Internet #OpenSource #LibreSpeed #PHP #measure #tinkering #nginx #turris #omnia #Init7
-
I recently acquired a new Turris Omnia NG router from @turris to take advantage of my new 10 Gbit/s internet speed from my provider Init7. Now I was really curious about my actual speed ...
This led me to LibreSpeed (https://github.com/librespeed), an Open Source speed test tool which is working by default with PHP. Unfortunately the router isn't powerful to provide reasonable measurements because the chunk files to test the download speed are generated by PHP and openssl. This appeared to be a bottleneck.
So I was tinkering a little bit and created a NGINX backend for LibreSpeed which doesn't rely on PHP.
Now I have put together this in a GitHub comment: https://github.com/librespeed/speedtest/issues/375#issuecomment-3769211254
(I still rely on PHP to get the IP address and to store the measurements though, but this is lightweight enough for the router.)
Try it out yourself: https://speedtest.momou.ch
#speedtest #Internet #OpenSource #LibreSpeed #PHP #measure #tinkering #nginx #turris #omnia #Init7
-
@martinsteiger #init7 is wirklich toll! Auch die 10gbit funktioniert wie erwartet wenn man die HW dazu hat! Zu empfehlen!
-
@martinsteiger #init7 is wirklich toll! Auch die 10gbit funktioniert wie erwartet wenn man die HW dazu hat! Zu empfehlen!
-
@martinsteiger #init7 is wirklich toll! Auch die 10gbit funktioniert wie erwartet wenn man die HW dazu hat! Zu empfehlen!
-
@martinsteiger #init7 is wirklich toll! Auch die 10gbit funktioniert wie erwartet wenn man die HW dazu hat! Zu empfehlen!
