How to find Internet problems and who is to blame part 2 - homework

Before contacting a provider, you need to figure out if everything is fine in the house. Without this check, there is a risk of turning into a boy who constantly shouted "I have packet loss" "wolves".






Currently, users have an increasing need for fast interactive traffic - when the Internet is not only thick, but also pings go very fast. The author works for GFN.RU. Both indicators are very important to our users, which allowed them to accumulate a certain store of knowledge and experience, which I share in my articles.





The author will make every effort to ensure that the articles remain objective and do not turn into an advertisement for GFN.RU.





Obsolescence of diagnostic tools

In the modern world, diagnostics, alas, is not very indicative. First, because it is based on 40-year-old protocols (RFC 792 - from 1981) and turns into a magnifying glass in the era of electron microscopes. And secondly, these protocols have big security problems. If a router fully meets RFC 792, then it can be simply attacked using a DDoS attack (which hackers indulged in in the 2000s). Therefore, even these protocols do not work well due to the tightened nuts.





A direct consequence of these limitations is the typical scenario for solving network problems:





, . : , .





, – , . 





, .





- , .





, , . , « – , » . , – - - .





, . : BGP IP. . BGP - , IP - . , :





  1. BGP TTTLDR.





  2. , AnyCast, IP 11.22.33.44 , + : AnyCast , IP - . IP , .





  3. MPLS . , .





  4. "" "" .





  5. "" . ECMP OS , tracert, , .





. traceroute.





windows /cmd tracert. WinMTR. , , .





cmd , windows-style:





/ cmd /k tracert -d -











  1. , . 





  2. – , , , , .





,

« 1000 ». : 





  1. , .





  2. . .





ping . , 20 1000 , - .





~1000 .  : 





200 , , , , . 5-6 . – .





PING

, IP . : cmd /k tracert -d ya.ru







Tracing route to ya.ru [87.250.250.242] over a maximum of 30 hops:







1 1 ms 1 ms <1 ms 192.168.88.1







IP tracert IP- .





, Mikrotik.





, , 64 , – . 





– .  - .





, .





, , wi-fi.









WIFI . -, (, ). -, .





- - .





, , . , .





, https://www.speedtest.net/ ping.





" ping" - ping -t . ping Control+C





, , .





– , . . - windows «Best battery life» 





, .





, , . 200 . 









  1. .





  2. .





. – :





, , , .





, Wi-Fi . «», «», , , . 





, Smart TV , – «». . , , . .





, Wi-Fi

beacons, , 80 – . .





: «2.4» – 5 . 5.





– , « ». . , . . 5- «», 159-.





WiFiInfoView : https://www.nirsoft.net/utils/wifiinformationview.html





: https://en.wikipedia.org/wiki/ListofWLAN_channels





, - Sigal Quality , .





. . , , , :





:





.





, 40-50 .  .. – / – , . – . 40 .





– Wi-Fi , .





:





  1. Find the IP address of your home router.





  2. Run a long ping to the router. Measure losses and speed.





  3. Run a speed test and a long ping in parallel.





  4. Compare results. If there is no deterioration in ping rates, then you have a connection to the router - faster than an Internet channel, and in general, everything is fine at home.





Wifi:





  1. Select a frequency and an unoccupied channel.





  2. If possible, remove the point from the walls.





  3. Orient the antennas correctly. By the way, by running a long "ping" and twisting the antennas, you can find the best option, but do not forget that the figures are reliable only when you DO NOT TOUCH the antennas.





  4. Select the minimum transmitter power that gives the maximum speed in the local network.





How to find internet problems and who is to blame part 1 - inception












All Articles