The Wiert Corner – irregular stream of stuff

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

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

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

    Join 1,729 other followers

Archive for the ‘ADSL’ Category

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 »

Convert FRITZ!Box 7360 to Managed Switch (or even Access Point) having it’s own IP address: Setting up the FRITZ!Box as an IP client – via AVM International

Posted by jpluimers on 2017/01/23

This was a tad difficult to find as I searched for “Convert Fritz!Box to Switch” instead of “Convert Fritz!Box to Access Point”.

Since I had an old Fritz!Box 7360 lying around (from my ADSL era) and wanted to extend the cabled LAN for my brothers Fritz!Box 7490 with some low-bandwidth devices (max 100 megabit/second) I searched for Switch. My bad.

Oh I had to factory reset it as well as I forgot the management credentials. The AVM help on this is cumbersome: Loading the FRITZ!Box factory settings | FRITZ!Box 7360 | AVM International but the xs4all help includes a web-reset procedure as part of Internet: Reset procedures van mijn FRITZ!Box 7360 which translates to:

  1. Switch off the Fritz!Box (as this procedure needs to be done within 10 minutes of switching it on)
  2. Connect LAN2 to your computer
  3. Switch on the Fritz!Box
  4. Wait for a DHCP IP or (if you know the IP addresses) configure IP manually
  5. Go to the web-interface URL
  6. Indicate you forgot your password:

    Forgot your password?

    Forgot your password?

  7. Indicate you want a factory reset:

    Restore Factory Settings

    Restore Factory Settings

Anyway: with the above steps it becomes a Managed Switch (and if you don’t disable WiFi: Access Point too) that uses the primary internet connection as DHCP server (so it gets an IP address itself as well which means you can manage it).

Read the rest of this entry »

Posted in ADSL, Fritz!, Fritz!Box, 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:

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 | 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!Box, Internet, Network-and-equipment, Power User, Routers, VPN | Leave a Comment »

 
%d bloggers like this: