Hello,
recently I started to have issues with opening one particular page. I tested that page from mobile phone over LTE and works fine. I narrowed issue to Homebox. Looks like error is on TSL handshake and Homebox has something to do with it.
Anybody with similar issue?
Thank you.
Seite 1 / 1
recently I started to have issues with opening one particular page. I tested that page from mobile phone over LTE and works fine. I narrowed issue to Homebox. Looks like error is on TSL handshake and Homebox has something to do with it.
Anybody with similar issue?
Thank you.
Which site? The homebox shouldn't touch the TLS handshake at all.
https://nadmetanja.briefing-nadmetanja.hr/
http://www.briefing.ba/
these two are issue. I narrowed down issue by elimination to homebox. It used to work, checked with guys running these websites and they haven't changed anything in months. However, I noticed new firmware on homebox.
http://www.briefing.ba/
these two are issue. I narrowed down issue by elimination to homebox. It used to work, checked with guys running these websites and they haven't changed anything in months. However, I noticed new firmware on homebox.
Hmm. Working on my side. Not very fast... Maybe that's the problem...
Hello @AKaric ,
sounds... interesiting. What kind of error exactly do you get? Do you also recieve this error if you connect your mobile via WiFi with the Homebox? If I remember I can try to check this from home since I am using the same model of the o2 Homebox.
Regards,
Lars
sounds... interesiting. What kind of error exactly do you get? Do you also recieve this error if you connect your mobile via WiFi with the Homebox? If I remember I can try to check this from home since I am using the same model of the o2 Homebox.
Regards,
Lars
Hello @o2_Lars ,
there is no specific error. Page is just unreachable. Tried different devices with different OS. For example mobile opens over LTE without problems but as soon as it is connected to Homebox, no go. Restarting Homebox helped before but now even restart won't help.
If you are using same Homebox with same firmware, please try to open up these pages and let me know result. Thank you.
there is no specific error. Page is just unreachable. Tried different devices with different OS. For example mobile opens over LTE without problems but as soon as it is connected to Homebox, no go. Restarting Homebox helped before but now even restart won't help.
If you are using same Homebox with same firmware, please try to open up these pages and let me know result. Thank you.
I also use a o2 Homebox 6641 (with the same firmware). I can open these websites without any issues. Maybe the websites or their provider had a temporary problem.
Hello @AKaric ,
if you still encounter the same issues please reset the Homebox to factory default and install it using the PIN that you recieved from us during activation. You also find all necessary data on our online portal under Mein o2.
Please also make sure that there are no additional services activated that transfer data through other networks like for example VPN or a TOR browser since this can interfere with reaching a host.
You may also try to ping this address or carry out a traceroute to see if there is something not right with the route to that host.
Please also try accessing the host with a browser set to private so that no cookie may interfere with this page.
You are using the DNS server that we provide to the homebox via DHCP, don't you?
Regards,
Lars
if you still encounter the same issues please reset the Homebox to factory default and install it using the PIN that you recieved from us during activation. You also find all necessary data on our online portal under Mein o2.
Please also make sure that there are no additional services activated that transfer data through other networks like for example VPN or a TOR browser since this can interfere with reaching a host.
You may also try to ping this address or carry out a traceroute to see if there is something not right with the route to that host.
Please also try accessing the host with a browser set to private so that no cookie may interfere with this page.
You are using the DNS server that we provide to the homebox via DHCP, don't you?
Regards,
Lars
Update: Over Windows 10 same problem. Can´t open the two webpages. Ping is no problem.
How long are customer at O2?All new customer have a real dual stack (IPv4 and IPv6) for over two years
For information:
I can connect to the standard browser via the smartphone (Mate 10 Lite) and to the 7490 via Wi-Fi, with both sides opening.
I use neither VPN nor is IPv6 activated at the Fritzbox.
I can connect to the standard browser via the smartphone (Mate 10 Lite) and to the 7490 via Wi-Fi, with both sides opening.
I use neither VPN nor is IPv6 activated at the Fritzbox.
Hello @AKaric ,
I activated DualStack with IPv6 for your connection. Please reconnect your router and try again if you can reach this addresses now :-)
Thanks to@Joe Doe for testing this :-)
Regards,
Lars
I activated DualStack with IPv6 for your connection. Please reconnect your router and try again if you can reach this addresses now :-)
Thanks to
Regards,
Lars
Interesting ... how do you know that the TE lives in the north?
It worked for me without IPv6.
Ok. It looks now like a routing problem up to the region you live. @blablup What is your region? My is near Hamburg.
code:
Routenverfolgung zu nadmetanja.briefing-nadmetanja.hr [80.80.59.125]
über maximal 30 Hops:
1 5 ms 2 ms 1 ms be.ip 192.168.1.xx]
2 25 ms 64 ms 26 ms loopback1.0004.acln.06.ham.de.net.telefonica.de 62.52.201.xxx]
3 28 ms 27 ms 27 ms bundle-ether11.0002.dbrx.06.ham.de.net.telefonica.de 62.53.7.110]
4 33 ms 34 ms 32 ms ae7-0.0001.corx.06.ham.de.net.telefonica.de 62.53.15.0]
5 32 ms 31 ms 32 ms ae6-0.0002.corx.02.fra.de.net.telefonica.de 62.53.0.49]
6 31 ms 34 ms 34 ms bundle-ether6.0001.dbrx.02.fra.de.net.telefonica.de 62.53.0.127]
7 31 ms 31 ms 31 ms bundle-ether1.0004.prrx.02.fra.de.net.telefonica.de 62.53.8.187]
8 32 ms 31 ms 32 ms 176.52.252.28
9 32 ms 31 ms 31 ms 80.157.131.181
10 51 ms 50 ms 50 ms 217.239.41.54
11 50 ms 50 ms 50 ms 217.239.41.54
12 54 ms 55 ms 54 ms 62.159.61.222
13 54 ms 54 ms 55 ms 85-114-37-2.dialup.optinet.hr 85.114.37.2]
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 60 ms 62 ms 60 ms 80.80.59.2
18 71 ms 67 ms 66 ms www.briefing.ba .80.80.59.125]
Yesterday my IP was 77.6.26.53 and yesterday i have tested the URL with success.
It was just slow (3 seconds to show the page).
https://nadmetanja.briefing-nadmetanja.hr/ i can´t open any more.
(Works at 12:10 with IP 95.116.1XX.XXX Gateway 62.52.201.201
Not working with now IP 77.3.1XX.XXX and Gateway 62.52.200.147)
http://www.briefing.ba/ i can open without any problems.
works with IPv6 at all
code:
C:\Users\XXX>tracert nadmetanja.briefing-nadmetanja.hr
Routenverfolgung zu nadmetanja.briefing-nadmetanja.hr 80.80.59.125]
über maximal 30 Hops:
1 3 ms 1 ms 1 ms fritz.box x192.168.178.X]
2 11 ms 14 ms 7 ms 62.52.200.147
3 9 ms 10 ms 8 ms bundle-ether27.0005.dbrx.01.ham.de.net.telefonica.de e62.53.12.12]
4 23 ms 15 ms 15 ms ae4-0.0001.corx.06.ham.de.net.telefonica.de e62.53.14.230]
5 16 ms 14 ms 14 ms ae6-0.0002.corx.02.fra.de.net.telefonica.de e62.53.0.49]
6 14 ms 14 ms 15 ms bundle-ether2.0002.dbrx.01.off.de.net.telefonica.de e62.53.0.209]
7 15 ms 16 ms 17 ms bundle-ether2.0001.prrx.01.off.de.net.telefonica.de e62.53.28.177]
8 15 ms 14 ms 14 ms 176.52.252.32
9 19 ms 17 ms 17 ms 80.157.131.181
10 33 ms 32 ms 32 ms 217.239.43.254
11 40 ms 38 ms 37 ms 62.159.61.222
12 40 ms 40 ms 39 ms 85-114-37-2.dialup.optinet.hr r85.114.37.2]
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 46 ms 48 ms 46 ms 80.80.59.2
17 46 ms 43 ms 44 ms 80.80.59.125
Ablaufverfolgung beendet.
Report from Hessen-region in the south:
Both URL accessible without problems, if IPv6 is active.
First URL is not loadable with IPv6 OFF !!! No Error-message, only blank screen.
Second URL loads also with IPv4, but slow.
With a Gateway 62.52.200.XXX the first link or both don´t work.
with my 2nd IP i get no answer.
I think i could be a problem from the target.
The DNS will not resolved with an IPv6 DNS.
So IPv6 will have no real influence. There is no different if i turn it on or off.
code:
traceroute to 80.80.59.125, 30 hops max, 36 byte packets
1 (85.183.43.xx) 1 ms 1 ms 1 ms
2 (62.52.201.200) 20 ms 20 ms 20 ms
3 (62.53.2.98) 19 ms (62.53.2.96) 20 ms 20 ms
4 (62.53.14.28) 26 ms 35 ms (62.53.15.0) 29 ms
5 (62.53.0.49) 26 ms (62.53.0.17) 28 ms (62.53.0.1) 27 ms
6 (62.53.0.27) 29 ms (62.53.0.11) 27 ms (62.53.0.29) 28 ms
7 (62.53.9.54) 28 ms 26 ms (62.53.1.34) 45 ms
8 (213.140.51.60) 27 ms 28 ms 27 ms
9 (80.157.131.181) 26 ms 26 ms 26 ms
10 (217.239.55.238) 43 ms 43 ms 42 ms
11 (217.239.55.238) 42 ms (62.159.61.222) 50 ms 50 ms
12 (85.114.37.2) 49 ms 48 ms 48 ms
13 * * *
14 * * *
15 * * *
16 (80.80.59.2) 56 ms 56 ms 56 ms
17 (80.80.59.2) 53 ms * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Try a reconnect to get this Gateway.
I would like to think that is nothing o2 specific.
And even other trace route have a problem...
A trace route from heise.de is working:
And even other trace route have a problem...
code:
guest@dnstools.ch:~> traceroute 80.80.59.125
1 static.1.241.243.136.clients.your-server.de (136.243.241.1) 0.207 ms
2 core24.fsn1.hetzner.com (213.239.229.53) 1.303 ms
3 core4.fra.hetzner.com (213.239.203.149) 4.992 ms
4 100ge7-2.core1.fra1.he.net (80.81.192.172) 4.991 ms
5 100ge11-1.core1.fra2.he.net (72.52.92.86) 5.301 ms
6 100ge5-2.core1.muc1.he.net (184.105.223.110) 11.144 ms
7 100ge14-1.core1.vie1.he.net (184.105.65.109) 16.893 ms
8 100ge10-1.core1.sof1.he.net (184.105.65.134) 33.855 ms
9 optima-telekom.10gigabitethernet14-2.core1.zag1.he.net (216.66.93.62) 23.361 ms
10 85-114-37-2.dialup.optinet.hr (85.114.37.2) 23.127 ms
11 *
12 *
13 *
A trace route from heise.de is working:
code:
Hop IP Hostname Pings [ms] avg [ms]
1 212.19.45.33 - 0,47 / 0,28 / 0,34 0,36
2 212.19.61.10 - 0,35 / 4,06 / 0,41 1,60
3 82.98.102.20 - 0,89 / 0,69 / 0,75 0,78
4 82.98.102.6 te0-0-2-1.c350.f.de.plusline.net 1,01 / 2,00 / 0,97 1,33
5 62.157.251.37 - 0,55 / 0,48 / 0,92 0,65
6 217.239.49.114 - 14,35 / 14,43 / 14,08 14,29
7 217.239.49.114 - 14,12 / 14,05 / 14,20 14,12
8 80.157.206.6 - 22,48 / 22,30 / 22,56 22,45
9 85.114.37.10 85-114-37-10.dialup.optinet.hr 21,73 / 21,74 / 21,67 21,71
10 - - - -
11 - - - -
12 - - - -
13 80.80.59.2 - 32,68 / 28,71 / 28,63 30,01
14 80.80.59.125 - 32,26 / 35,45 / 36,18 34,63
15 80.80.59.125 - 40,26 40,26
Geez,... thanks to you all for this really extensive testing, that was something that I could not have done myself sitting in the office (fully climated btw ).
I addressed this internally to a special departement and they might have a look into this (I can not and will not promise anything) and if they find anything that is not running as it should I am sure they will take any steps necessary to fix this
Regards,
Lars
I addressed this internally to a special departement and they might have a look into this (I can not and will not promise anything) and if they find anything that is not running as it should I am sure they will take any steps necessary to fix this
Regards,
Lars
Deine Antwort
Werde Teil der O₂ Community!
- Melde dich bei Mein O₂ an (oder registriere dich schnell)
- Wähle deinen Nutzernamen für die Community
- Erstelle dein Thema oder deinen Kommentar und lass dir schnell und unkompliziert helfen
Anmelden
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.