Thanks voor julllie reacties!
Yes. Ik schakel zelfs regelmatig over naar mijn telefoon als hotspot, dat gaat echt zóveel sneller en 'snappier' dan de DSL verbinding. Overigens is het zowel bedraad als draadloos het geval, voor de duidelijkheid!
Okay, vanaf een willekeurige computer, aan de kabel en wifi uit.
Bokt is in ieder geval niet te laden... staat nu al een dikke minuut wisselend op connecting-loading-finding-etc. Mijn telefoon laadt dezelfde site, via 4G, gewoon supersnel, dus aan de aanbodkant is niks mis. Op hetzelfde moment heb ik een aantal traceroutes uitgevoerd.
Het valt mij op dat bepaalde onderdelen tijdens het lang laden ook weer apart zichtbaar waren: googlesyndication.com en boktimg.nl, dus die heb ik allebei ook meegenomen.
code:
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
| C:\Users\hurkm>tracert bokt.nl
Tracing route to bokt.nl [82.161.230.90]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.254
2 18 ms 18 ms 18 ms 82-170-155-254.ip.telfort.nl [82.170.155.254]
3 19 ms 19 ms 20 ms ams-ix.sara.xs4all.net [80.249.208.48]
4 19 ms 19 ms 19 ms 0.ae4.xr3.3d12.xs4all.net [194.109.5.5]
5 19 ms 19 ms 19 ms 0.ae11.xrc1.1d12.xs4all.net [194.109.5.102]
6 19 ms 19 ms 19 ms www.bokt.nl [82.161.230.90]
Trace complete.
C:\Users\hurkm>tracert googlesyndication.com
Tracing route to googlesyndication.com [216.58.211.164]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.2.254
2 18 ms 17 ms 37 ms 82-170-155-254.ip.telfort.nl [82.170.155.254]
3 19 ms 19 ms 18 ms ae10.524.ibr1.asd-nh.ip.telfort.nl [195.240.64.3
3]
4 19 ms 18 ms 18 ms 195-240-240-194.ip.telfort.nl [195.240.240.194]
5 19 ms 19 ms 19 ms 209.85.240.111
6 20 ms 19 ms 19 ms 209.85.251.25
7 32 ms 32 ms 42 ms 72.14.233.250
8 32 ms 31 ms 31 ms 209.85.241.139
9 31 ms 32 ms 31 ms dub08s01-in-f4.1e100.net [216.58.211.164]
Trace complete.
C:\Users\hurkm>tracert boktimg.nl
Tracing route to boktimg.nl [82.161.230.91]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.254
2 18 ms 18 ms 18 ms 82-170-155-254.ip.telfort.nl [82.170.155.254]
3 19 ms 19 ms 19 ms ams-ix.sara.xs4all.net [80.249.208.48]
4 19 ms 19 ms 20 ms 0.ae4.xr3.3d12.xs4all.net [194.109.5.5]
5 19 ms 19 ms 20 ms 0.ae10.xrc2.3d12.xs4all.net [194.109.5.118]
6 19 ms 19 ms 20 ms img.bokt.nl [82.161.230.91]
Trace complete.
C:\Users\hurkm>tracert linkedin.com
Tracing route to linkedin.com [108.174.10.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.254
2 18 ms 18 ms 18 ms 82-170-155-254.ip.telfort.nl [82.170.155.254]
3 19 ms 18 ms 18 ms ae10.524.ibr1.asd-nh.ip.telfort.nl [195.240.64.3
3]
4 19 ms 19 ms 19 ms kpn-nso.telecity2.jointtransit.nl [217.170.20.13
0]
5 20 ms 20 ms 19 ms adm-b2-link.telia.net [62.115.145.74]
6 19 ms 19 ms 19 ms adm-bb3-link.telia.net [213.155.137.210]
7 27 ms 27 ms 27 ms ldn-bb3-link.telia.net [213.155.136.98]
8 103 ms 104 ms 104 ms ash-bb3-link.telia.net [80.91.249.101]
9 104 ms 104 ms 104 ms ash-b1-link.telia.net [62.115.113.209]
10 100 ms 101 ms 102 ms linkedin-ic-301441-ash-b1.c.telia.net [213.248.1
03.190]
11 * * * Request timed out.
12 * * * Request timed out.
13 102 ms 102 ms 103 ms 108-174-10-10.fwd.linkedin.com [108.174.10.10]
Trace complete. |
En die pings:
code:
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
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
| C:\Users\hurkm>ping -t bokt.nl
Pinging bokt.nl [82.161.230.90] with 32 bytes of data:
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=20ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Reply from 82.161.230.90: bytes=32 time=19ms TTL=58
Pinging linkedin.com [108.174.10.10] with 32 bytes of data:
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=103ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=103ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=103ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55
Reply from 108.174.10.10: bytes=32 time=102ms TTL=55 |
Beiden gingen door zonder timeouts of pieken...
Check.
DSL komt binnen op een Telfort Experiabox V8, routed. Telfort ondersteunt geen bridgemode (formeel) en daarom staat ie nu weer in routed. (in de routes hierboven: 192.168.2.254). Wireless is uit.
Er hangen twee devices aan: IPTV STB (apart VLAN) en een Dlink DIR868L router (192.168.2.1 aan WAN, 192.168.0.1 aan LAN-zijde). Deze routeert ook. De Dlink staat in de DMZ van de Experiabox. Wel of niet in de DMZ plaatsen maakt overigens geen verschil.
De Dlink is voor het LAN de DHCP server. Eén kabel naar een Asus unmanaged gigabit switch met PC, Mac Mini en Time Capsule. Eén kabel naar een Synology DS412+ NAS. De rest is wireless, voor zover mogelijk op 5GHz N/AC geconfigureerd.