December 2025
M	T	W	T	F	S	S
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31

Archive for the ‘Fritz!Box’ Category

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 »

Fritz!Box 7360 and 7490: static routes over VPN don’t work

Posted by jpluimers on 2016/03/15

I’ve tried the below on a Fritz!Box 7490 configuration and it fails as well.

The case is that I’ve a VPN (see Getting Fritz!Box LAN-LAN VPN to work) between a Fritz!Box 7360 (having internal IP 192.168.24.1) and a Fritz!Box 7490 (having internal IP 192.168.71.1). This is how it looks from the Fritz!Box 7360 side:

Name Address in the Internet local network remote network

80.100.143.119 80.100.143.119 192.168.24.0/24 192.168.171.0/24

Name	Address in the Internet	local network	remote network
80.100.143.119	80.100.143.119	192.168.24.0/24	192.168.171.0/24

On the 192.168.171.0/24 side of things, the internal IP of the 80.100.143.119 router is 192.168.171.1. Inside the 192.168.171.0/24 network is is another router (192.168.171.22) having an internal 192.168.71.0/24 network.

Basically I want to tell the Fritz!Box 7360 (at IP 192.168.24.1) that there is an internal route to 192.168.71.0/24 via 192.168.171.22.

I found and read Accessing multiple IP networks behind a FRITZ!Box over VPN connection between two FRITZ!Boxes | FRITZ!Box 7360 | AVM International.

Based on it, I wanted to add this route on the 192.168.24.1:

Static IPv4 Route

IPv4 network 192.168.71.0

Subnet mask 255.255.255.0

Gateway 192.168.171.22

Enabled X

IPv4 network	192.168.71.0
Subnet mask	255.255.255.0
Gateway	192.168.171.22
Enabled	X

When you do that, you get this error message:

An error occurred.
Error description: The route is illegal.
Please enter your data again. If the error occurs again, please consult AVM Support.

How can I get this route to work?

–jeroen

Posted in Fritz!, Fritz!Box, Internet, Power User | 1 Comment »

Getting Fritz!Box LAN-LAN VPN to work for @xs4all connections despite lack of @AVM_DE support

Posted by jpluimers on 2016/01/22

This is a follow-up of my post Fritz!Box VPN error messages.

I had been failing to get a LAN-LAN connection between two xs4all Fritz!Box internet connections working, despite the description in [WayBack] Adapting a VPN connection from FRITZ!Box to FRITZ!Box (LAN-LAN) | AVM International.

I was keeping the 0x1C error, and eventually contacted the customer support. At first they redirected me again to the documentation, so I replied with detailed PDFs for both Fritz!Box devices containing detailed information about:

both their internet connectivity
both their internal network settings
both their error logs
both their VPN configuration (including LAN-LAN and personal entries)

I got a reply back that – paraphrased – went like “We cannot provide network-administration-support, but VPN support of Fritz!Box in general works fine, so please read these pages”:

Given that they knew both connections were xs4all (which out-of-the-box doesn’t firewall), the PDFs didn’t indicate any firewall configuration and support not asking if the individual VPN connections worked (they do) but just blaming me or the Firewall is blatant, especially since they did not explain what the error codes meant.

Besides I already had read those pages and tried all the suggested solutions (more than a day work, as there are many suggested steps, Fritz!Box devices tend to reboot on many configuration change types and their DSL training is slow at best).

After the email, I went back to the drawing board based in this one twitter conversation that was partially useful (but failed to indicate more error codes and also pointed me to their email helpdesk which failed miserably).

The IKE-error 0x1C can mean that the remote IP doesn’t match the expected IP.

So I tried this:

Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Hardware, Network-and-equipment, Power User | 1 Comment »

[NL] @xs4all – inkomende telefoontjes blokkeren: Fritz!Box of VOIP-selfcare

Posted by jpluimers on 2016/01/18

xs4all biedt twee mogelijkheden om inkomende telefoontjes te blokkeren: via de Fritz!Box of via VOIP-selfcare.

Als je in het VOIP-selfcare een nummer toevoegt onder “Inkomende oproepen blokkeren”, dan krijgt de beller een “bandje” dat het een ongewenst gesprek is. Dat wilde ik niet: net als bij inlog fouten wil je zo weinig mogelijk informatie geven over een oorzaak.

Als je oproepen van een specifiek telefoonnummer via de Fritz!Box blokkeert, dan krijgt de beller meteen xs4all voicemail. Ook niet wat ik wilde, maar het zette me wel op het juiste spoor.

De voicemail komt doordat de Fritz!Box dan een meteen een in-gesprek (line busy) genereert en zo het telefoongesprek afwimpelt. Omdat voicemail bij xs4all standaard aan staat, gaat het gesprek dan meteen naar voicemail.

In dit geval wilde ik toch van de xs4all voicemail af, dus heb ik dat gedaan door in de VOIP-self care alle vinkjes bij “Gesprekken doorschakelen” uit te zetten, zie het plaatje onderaan.

Een “Gesprekken doorschakelen” zonder vinkjes heft alle doorschakelingen op, waardoor de beller precies het antwoord krijgt dat de Fritz!Box voorschotelt.

Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Internet, Power User | Leave a Comment »

Fritz!Box VPN error messages – via: VPN mit der FritzBox :: network lab

Posted by jpluimers on 2015/11/02

VPN mit der FritzBox :: network lab has a nice walk through on how to set up non LAN-LAN VPN connections with Fritz!Box.

But the really cool thing is that they have a table of IKE (Internet Key Exchange) error messages.

Until now, I mainly had these errors, which thanks to the table now have a description:

0x0000 or 0x0: ???
0x001C or ox1C: “invalid id”; translated: wrong remote IP in the VPN config
0x2027: “timeout”
0x202d: “dns: timeout”

Better than

Note: both are within the public IP range, so not in the ranges mentioned here: Identifying the address range of the IPv4 address for the Internet connection | FRITZ!Box 7390 | AVM International.

Maybe I should just use the Windows tools to setup the config: MarkusKirschmann.de – Blog » IKE-Error Ox1c.

–jeroen

via:

Their table:

Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Network-and-equipment, Power User | Leave a Comment »

Fiber to Fiber speed beats Cable to Fiber speed by a factor 2 (all three internet connections are in the same house)

Posted by jpluimers on 2015/10/05

I’ve two fiber connections, one cable connection and one ADSL connection at home.

This is a traceroute from one fiber connection to the other over the outside network:

traceroute to snip.xs4all.nl (80.100.143.119), 64 hops max, 52 byte packets
 1  tomatortn66u (172.23.71.1)  0.951 ms  0.708 ms  0.638 ms
 2  fiber24315337241.heldenvannu.net (37.153.243.241)  1.135 ms  0.988 ms  0.974 ms
 3  rt121bb121-212-183.routit.net (212.121.121.183)  1.973 ms  1.976 ms  1.919 ms
 4  0-7-0-4-core2-a-tc1.routit.net (84.246.25.133)  2.711 ms  2.498 ms  2.517 ms
 5  0-7-0-4-core2-a-tc1.routit.net (84.246.25.133)  2.725 ms  2.674 ms  2.535 ms
 6  0-7-0-7-core4-a-tc2.routit.net (37.0.80.7)  3.048 ms  2.883 ms  2.712 ms
 7  1-2-inet1-tc2.routit.net (84.246.25.46)  2.767 ms  2.633 ms  2.514 ms
 8  ams-ix.tc2.xs4all.net (80.249.208.166)  2.676 ms  4.177 ms  2.775 ms
 9  0.ae5.xr3.3d12.xs4all.net (194.109.5.13)  2.987 ms  3.114 ms  11.387 ms
10  xe-8-1-0.dr11.xs4all.net (194.109.7.14)  6.188 ms
    xe-7-0-1.dr11.d12.xs4all.net (194.109.7.58)  3.320 ms
    xe-8-0-1.dr11.d12.xs4all.net (194.109.7.38)  3.206 ms
11  snip.xs4all.nl (80.100.143.119)  4.079 ms !X  3.960 ms !X  3.946 ms !X

This is the same but from my third connection (that will go away sooner than later): Cable.

traceroute to snip.xs4all.nl (80.100.143.119), 64 hops max, 52 byte packets
 1  www.asusnetwork.net (192.168.171.1)  1.016 ms  0.983 ms  0.938 ms
 2  * * *
 3  212.142.62.69 (212.142.62.69)  11.427 ms  8.361 ms  8.459 ms
 4  84.116.244.97 (84.116.244.97)  8.080 ms  10.405 ms  7.340 ms
 5  nl-ams09b-ri1-xe-10-2-0.aorta.net (84.116.130.22)  7.625 ms
    nl-ams09b-ri1-xe-8-0-0.aorta.net (84.116.130.2)  10.392 ms
    84.116.136.81 (84.116.136.81)  9.534 ms
 6  0.xe-1-2-0.xr1.tc2.xs4all.net (194.109.7.209)  8.315 ms  9.505 ms  9.684 ms
 7  0.ae5.xr3.3d12.xs4all.net (194.109.5.13)  9.508 ms
    0.ae4.xr4.1d12.xs4all.net (194.109.5.9)  9.565 ms
    0.ae5.xr3.3d12.xs4all.net (194.109.5.13)  9.459 ms
 8  xe-7-0-1.dr11.d12.xs4all.net (194.109.7.58)  8.547 ms  13.159 ms  9.893 ms
 9  snip.xs4all.nl (80.100.143.119)  9.710 ms !X  10.079 ms !X  8.121 ms !X

Finally there is ADSL (which will go even sooner):

snap:~ # traceroute snip.xs4all.nl
traceroute to snip.xs4all.nl (80.100.143.119), 30 hops max, 40 byte packets using UDP
 1  192.168.71.1 (192.168.71.1)  1.052 ms   0.554 ms   0.520 ms
 2  lo0.dr13.d12.xs4all.net (194.109.5.212)  17.767 ms   17.368 ms   17.123 ms
 3  1423.ae3.xr4.1d12.xs4all.net (194.109.7.137)  16.901 ms 1418.ae3.xr4.1d12.xs4all.net (194.109.7.17)  16.628 ms 1323.ae3.xr3.3d12.xs4all.net (194.109.7.141)  16.354 ms
 4  xe-8-1-0.dr11.xs4all.net (194.109.7.14)  15.961 ms xe7-0-0.dr11.d12.xs4all.net (194.109.7.170)  15.762 ms xe-8-1-0.dr11.xs4all.net (194.109.7.14)  15.283 ms
 5  snip.xs4all.nl (80.100.143.119)(N!)  15.914 ms (N!)  16.171 ms (N!)  15.710 ms

Cable is about twice as slow than Fiber.

ADSL is about three times as slow than Fiber.

–jeroen

Posted in fiber, Fritz!, Fritz!Box, Internet, Power User, routers, TomatoUSB | Leave a Comment »

http://169.254.1.1 trick for Opening UI of the FRITZ!WLAN Repeater 1750E – via: AVM International

Posted by jpluimers on 2015/08/24

Because http://fritz.box points to my Fritz!BOX router, it cannot be used to get to my Fritz!WLAN Repeater. I just learned about the http://169.254.1.1 trick does.

Which saves me from remembering the repeater IP-address or name.

–jeroen

via: Opening the FRITZ!Box user interface | FRITZ!WLAN Repeater 1750E | AVM International.

Posted in Fritz!, Fritz!Box, Fritz!WLAN, Internet, Power User, routers | Leave a Comment »

Looking for a new Dynamic DNS provider for FritzBox 7340 and ASUS RT N66U

Posted by jpluimers on 2013/08/01

Found out the hard way that DynDNS.org now requires you to perform a web login every 30 days for the free service: Free DNS requires monthly login? – Dyn Community Forum.

Basically I’m looking for a way to either

host my own dynamic DNS compatible service (I already run normal DNS on 2 domains)
use another free dynamic DNS service

The biggest problem: I’m using 2 routers that have a list of supported Dynamic DNS services that only partially overlap: Read the rest of this entry »

Posted in ASUS RT-N66U, Fritz!, Fritz!Box, Network-and-equipment, Power User | Tagged: dynamic dns service, software, technology | 1 Comment »

#@xs4all only over AnnexB with FRITZ!Box 7340 #fail: line sync issues; offline most of the time, max 4 mbit. @xs4all needs to give me some compelling arguments to regain trust in them. @xs4all_HD

Posted by jpluimers on 2012/03/08

xs4all won’t tell you up front, but they changed a couple of things that will bring your 10 mbit down / 1 mbit up to something that hardly connects, and if it does less than half the speed.

This is also a post on how XS4ALL treats long lasting (15 years!) customer relations. Badly.

05.03.12 16:08:01 DSL-Synchronisierung beginnt (Training). 05.03.12 16:06:05 Internetverbindung wurde getrennt. 05.03.12 16:06:05 Internetverbindung IPv6 wurde getrennt, Präfix nicht mehr gültig. 05.03.12 16:06:05 Internetverbindung wurde getrennt. 05.03.12 16:06:05 DSL antwortet nicht (Keine DSL-Synchronisierung). 05.03.12 15:56:30 Internetverbindung IPv6 wurde erfolgreich hergestellt. Präfix: 2001:980:43d9::/48 05.03.12 15:56:30 Internetverbindung IPv6 wurde erfolgreich hergestellt. IP-Adresse: 2001:980:43d9::be05:43ff:fe70:9b53 05.03.12 15:56:26 Internetverbindung wurde erfolgreich hergestellt. IP-Adresse: 82.161.132.169, DNS-Server: 194.109.6.66 und 194.109.9.99, Gateway: 194.109.5.205 05.03.12 15:56:21 DSL ist verfügbar (DSL-Synchronisierung besteht mit 4804/1029 kbit/s). 05.03.12 08:44:20 DSL-Synchronisierung beginnt (Training).

They advertised XS4ALL ONLY (since it on the copper pair you only run DSL, no phone, so you don’t need a splitter) as faster, cheaper and more stable internet and VOIP connection.

It is not. Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Network-and-equipment, Opinions, Power User | Leave a Comment »

xs4all ONLY issues with ADSL sync and Fritz!Box 7340

Posted by jpluimers on 2011/08/26

Recently, I had big problems with my Fritz!Box 7340 losing ADSL sync on my xs4all ONLY connection.

The odd thing is: the problems started after it worked well for quite a while.

I had multiple dozens of these reconnects per day, sometimes as few as once every fre hours, but often as many as half a dozen per hour:

11.07.11 05:14:08 IPv6 Internet connection established successfully. Prefix: 12ab:34cd:56ef::/48
11.07.11 05:14:08 IPv6 Internet connection established successfully. IP address: 12ab:34cd:56ef::fe01dc23:ba45:9867
11.07.11 05:14:07 Internet connection established successfully. IP address: 172.31.120.210, DNS server: 194.109.6.66 and
194.109.9.99, Gateway: 194.109.5.205
11.07.11 05:14:01 DSL is available (DSL synchronization exists with 10007/1029 kbit/s).
11.07.11 05:13:47 DSL synchronization starting (training).
11.07.11 05:13:32 Internet connection cleared.
11.07.11 05:13:32 IPv6 Internet connection was cleared; prefix no longer valid.
11.07.11 05:13:32 Internet connection cleared.
11.07.11 05:13:31 DSL not responding (no DSL synchronization).

The xs4all helpdesk didn’t respond on my emails, and Google searches didn’t reveal much.

This is what I tried:

I tried getting the FRITZ.Box_Fon_WLAN_7340.en-de-es-it-fr.99.05.04-19769.image firmware, mentioned in this thread, but could not download it any more.
I also tried to set the DSL settings to “maximum stability” without any improvement, resetting to factory settings, etc.
The router is already very close to the ISRA point (where DSL enters the house), and I tried both with/without splitter with no improvement whatsoever.
Read the steps in this sat4all thread, but found nothing unusual in my hardware and software config.

I didn’t expect any improvement as nothing on my side has changed, and before xs4all ONLY, I ran DSL for more than 10 years with different modems and no problems whatsoever.

Finally, I downgraded to Firmware-Version 99.04.88 from Firmware-Version 99.04.90.

When downgrading, keep this in mind:

Fritz! does not keep old firmware versions on-line; you must regularly get the Fritz!Box 7340 part of their ftp site and keep an archive yourself
It will reset your router to factory state and not remember any settings
It cannot restore your settings if you saved them with a higher firmware version, not even when you save them with a password as the web-interface seems to suggest

Luckily, one of the things that xs4all did well, is keep an archive of firmware versions for the Fritz!Box 7340, including a Firmware-Version 99.04.88.

Perform these steps when downgrading: Read the rest of this entry »

Posted in Fritz!, Fritz!Box, Network-and-equipment, Power User | 1 Comment »

« Previous Entries

Next Entries »

	Lars Fosdal on Security alarm provider Woonve…
	Thomas Mueller on Question got closed in May 202…
	Thaddy de Koning on Formulier voor bewindvoerders…
	Thaddy de Koning on Formulier voor bewindvoerders…
	Thaddy de Koning on Formulier voor bewindvoerders…

The Wiert Corner – irregular stream of stuff

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

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘Fritz!Box’ Category

difference between ADSLfiber and fiberfiber when both are @xs4all.

Fritz!Box 7360 and 7490: static routes over VPN don’t work

Static IPv4 Route

Getting Fritz!Box LAN-LAN VPN to work for @xs4all connections despite lack of @AVM_DE support

[NL] @xs4all – inkomende telefoontjes blokkeren: Fritz!Box of VOIP-selfcare

Fritz!Box VPN error messages – via: VPN mit der FritzBox :: network lab

Fiber to Fiber speed beats Cable to Fiber speed by a factor 2 (all three internet connections are in the same house)

http://169.254.1.1 trick for Opening UI of the FRITZ!WLAN Repeater 1750E – via: AVM International

Looking for a new Dynamic DNS provider for FritzBox 7340 and ASUS RT N66U

#@xs4all only over AnnexB with FRITZ!Box 7340 #fail: line sync issues; offline most of the time, max 4 mbit. @xs4all needs to give me some compelling arguments to regain trust in them. @xs4all_HD

xs4all ONLY issues with ADSL sync and Fritz!Box 7340

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

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘Fritz!Box’ Category

Rate this:

Share this:

Static IPv4 Route

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this: