The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,180 other subscribers

Archive for the ‘fiber’ Category

« Previous Entries

Reggefiber NTU: convert blind cap to become pure fiber, so no ethernet media converter is needed

Posted by jpluimers on 2021/09/20

Some links:

Edit 20210922: added the below Twitter thread, added searches for the now unavailable videos

[Archive.is] Joel Haasnoot on Twitter: “Freedom laat je alles zelf doen zonder monteur, maar risico als het stuk gaat is 2000-6000 euro om nieuwe splice te doen. Maar er zijn dus ook geen filmpjes oid :)… “

Joel Haasnoot‏ @webguy· Sep 20

Ik moest mij hier een paar maanden gelden hier induiken, maar enigszins bizar hoe weinig documentatie of Google-baar spul is. Er wordt vanuit gegaan dat sysadmins dit maar leren…
Jeroen Wiert Pluimers‏ @jpluimers· Sep 20

Inderdaad. Helaas is het youtube filmpje inmiddels private. Wat heb jij uiteindelijk gedaan?
Joel Haasnoot‏ @webguy· Sep 21

Paar problemen, deels omdat ik een van de eerste 128 oid was bij Freedom en er geen verhuisproces was. Had eerst een patchcover nodig voor nieuwe TK-01 (https://www.kpnwebshop.com/modems-routers/producten/patchcover-kit-ftu-tk01/2 …) en daar zat geen patchkabel bij (geen NTU nodig bij Freedom), want dat was opeens een SC ipv LC eind.
Joel Haasnoot‏ @webguy· Sep 21

Uiteindelijk had KPNNetwerkNL 4 weken nodig om licht op de lijn te krijgen… Ik heb nu nog een patchkabel + optics liggen voor Mikrotik router, maar vooor nu nog maar even via router.
Replying to @webguy @jpluimers
Freedom laat je alles zelf doen zonder monteur, maar risico als het stuk gaat is 2000-6000 euro om nieuwe splice te doen. Maar er zijn dus ook geen filmpjes oid :)

Videos:

–jeroen

Read the rest of this entry »

Posted in fiber, Internet, Power User | Leave a Comment »

Stratix BreedbandAtlas | Bekijk de consumentenbreedband dekking op uw locatie

Posted by jpluimers on 2018/11/09

[WayBack] BreedbandAtlas | Bekijk de consumentenbreedband dekking op uw locatie:

De BreedbandAtlas toont u actuele informatie over de dekking van consumentenbreedband in Nederland – zowel het type verbinding als de snelheid.

This is for consumer broadband connections, but for many businesses that is good enough (especially since players like xs4all and HeldenVanNu offer business plans like subnets, PIN-payment-over-IP).

Via: [WayBack] ‘Aanleg glasvezel groeit weer door lokale projecten en aanleg in buitengebieden’ – IT Pro – Nieuws – Tweakers

The site is by Stratix which also has published this fiber penetration chart over time:

Read the rest of this entry »

Posted in ADSL, fiber, Internet, Power User | Leave a Comment »

Wieso eigentlich PPPoE, Deutschland? Ganz früher, als Ihr noch ein Joghurt im Regal war…

Posted by jpluimers on 2018/11/05

An historic view on PPPoE usage: [WayBack] Wieso eigentlich PPPoE, Deutschland? Ganz früher, als Ihr noch ein Joghurt im Regal wart und die Telekom von ISDN mit Kanalbündelung (128kBit/s) auf DSL… – Kristian Köhntopp – Google+

Note that in The Netherlands:

Actually, xs4all DSL and Fiber use PPPoE too, in large part because it makes it easer for them to do IPv6. From https://www.xs4all.nl/service/diensten/internet/installeren/modem-instellen/hoe-kan-ik-een-ander-modem-dan-fritzbox-instellen.htm

<<<
ADSL
• PPPoA (vpi/vci 8/48, vc-mux). Via de PPPoA verbinding loopt zowel IPv4 als IPv6 verkeer.
• PPP authenticatie: PAP
• PPP credentials moeten ingevuld zijn (de waarden zijn niet belangrijk, maar er moet er wel iets ingevuld zijn)

VDSL en FTTH
• PPPoE via VLAN6 (802.1Q). Via de PPPoE verbinding loopt zowel IPv4 als IPv6 verkeer.
• PPP authenticatie: PAP
• PPP credentials moeten ingevuld zijn (de waarden zijn niet belangrijk, maar er moet er wel iets ingevuld zijn)
• RFC4638 wordt ondersteund op ons netwerk. Dit betekent dat u als klant een MTU van 1500 kunt gebruiken als uw router RFC4638 ondersteunt.
>>>

–jeroen

Posted in ADSL, fiber, Internet, Power User | Leave a Comment »

Bye, bye ADSL…

Posted by jpluimers on 2016/12/27

As I got rid of some final hard coded IPv4 stuff, earlier this month I said good-bye to Ziggo cable internet.

Today, the xs4all ADSL line finally got disconnected as well:

My old trusty Fritz!Box 7340 showing ADSL got disconnected for good on 20161217

My old trusty Fritz!Box 7340 showing ADSL got disconnected for good on 20161217

Which means that the years of running an xs4all DSL connection over mxStream, KPN FAST ADSL and xs4all ONLY are over. Oh the days:

I’m still connected: fiber by xs4all and fiber by helden van nu and when all else fails KPN LTE or xs4all onderweg.

Oh and I had a visit to xs4all unixbeheer and their data center a short while ago as they helped me a lot in the almost 20 years I’ve been a customer with them:

Read the rest of this entry »

Posted in ADSL, fiber, History, Internet, KPN, Power User, xs4all, Ziggo/UPC/A2000 | Leave a Comment »

difference between ADSLfiber and fiberfiber when both are @xs4all.

Posted by jpluimers on 2016/03/28

20150412 ping statistics from WiFi -> ADSL -> VPN -> fiber (where ADSL and fiber both are Fritz!Box machines having LAN-LAN VPN to each other):

PING 192.168.71.1 (192.168.71.1): 56 data bytes
64 bytes from 192.168.71.1: icmp_seq=0 ttl=63 time=19.190 ms
...64 bytes from 192.168.71.1: icmp_seq=1 ttl=63 time=18.905 ms
64 bytes from 192.168.71.1: icmp_seq=2 ttl=63 time=19.261 ms
64 bytes from 192.168.71.1: icmp_seq=3 ttl=63 time=19.982 ms
64 bytes from 192.168.71.1: icmp_seq=4 ttl=63 time=19.332 ms
64 bytes from 192.168.71.1: icmp_seq=5 ttl=63 time=26.800 ms
64 bytes from 192.168.71.1: icmp_seq=6 ttl=63 time=20.139 ms
64 bytes from 192.168.71.1: icmp_seq=7 ttl=63 time=19.498 ms
64 bytes from 192.168.71.1: icmp_seq=8 ttl=63 time=18.915 ms
64 bytes from 192.168.71.1: icmp_seq=9 ttl=63 time=19.200 ms
64 bytes from 192.168.71.1: icmp_seq=10 ttl=63 time=18.948 ms
64 bytes from 192.168.71.1: icmp_seq=11 ttl=63 time=19.524 ms
64 bytes from 192.168.71.1: icmp_seq=12 ttl=63 time=19.511 ms
64 bytes from 192.168.71.1: icmp_seq=13 ttl=63 time=20.417 ms
64 bytes from 192.168.71.1: icmp_seq=14 ttl=63 time=19.350 ms
64 bytes from 192.168.71.1: icmp_seq=15 ttl=63 time=18.690 ms
64 bytes from 192.168.71.1: icmp_seq=16 ttl=63 time=18.632 ms
64 bytes from 192.168.71.1: icmp_seq=17 ttl=63 time=18.912 ms
64 bytes from 192.168.71.1: icmp_seq=18 ttl=63 time=19.397 ms
64 bytes from 192.168.71.1: icmp_seq=19 ttl=63 time=19.257 ms
64 bytes from 192.168.71.1: icmp_seq=20 ttl=63 time=18.147 ms
64 bytes from 192.168.71.1: icmp_seq=21 ttl=63 time=18.601 ms
^C
--- 192.168.71.1 ping statistics ---
22 packets transmitted, 22 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.147/19.573/26.800/1.657 ms

same but LAN –> fiber -> VPN -> ADSL

Pinging 192.168.24.1 with 32 bytes of data:
Reply from 192.168.24.1: bytes=32 time=19ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=18ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63
Reply from 192.168.24.1: bytes=32 time=17ms TTL=63

Ping statistics for 192.168.24.1:
    Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 19ms, Average = 17ms

–jeroen

Posted in ADSL, fiber, Fritz!, Fritz!Box, Internet, Network-and-equipment, Power User, routers, VPN | Leave a Comment »

« Previous Entries
 
%d bloggers like this: