[es] - Multicast i neverovatno veliki ping na OpenWRT ruteru posle pola sata rada

Milan Kragujevic
Software Engineer

Član broj: 231903
Poruke: 2220
*.dynamic.vipmobile.rs.

Sajt: https://milankragujevic.c..

+201 Profil

Multicast i neverovatno veliki ping na OpenWRT ruteru posle pola sata rada

^{28.06.2018. u 18:37 - pre 70 meseci}

Mapa mreže je sledeća:
Ruter je Raspberry Pi 3B sa OpenWRT operativnim sistemom. Uplink je dva USB LTE modema u mwan3, mada to nema veze jer se problem dešava i bez mwan3 i čak i bez oba modema.
Svi uređaji idu na switch koji je spojen sa Pi-jem, onda ima još jedan svič na koji su spojeni prijemnici za tv.
Imam povezan Multicast servis na mrežu ethernetom kao i dva klijenta (Smart TV i set top box uređaj) na mreži isto ethernet-om. Multicast je pušten na oba plejera istovremeno.
Nakon 15 min do 30 min rada mreža se uspori, ping postane ogroman (500 ms za ethernet je apsurdno veliko, barem po meni)

FFmpeg šalje strim na multicast sa satelitskog risivera, i sasvim je sposoban hardver da enkodira video u realtime, osim toga pokazuje speed 1x stoga očigledno da ffmpeg nije problem.

Risiver nije problem isto jer restart risivera ne pomaže.

Interesantno je da se ping ka internetu (preko LTE modema) ne poveća kada se "zakuca" mreža što mi je čudno, jer da je problem do protoka na mreži ili do opterećenja procesora rutera, trebalo bi sav saobraćaj da "crkne", ne samo multicast.
Jedino rešenje je restart rutera odnosno Pi-ja, kada se automatski restartuje strimer (FFmpeg) i risiver (jer primeti da je mreža pukla pa ima while true loop koji proverava dok ne bude reachable command server nakon čega startuje multicast risiver softver odnosno middleware).

Svi kablovi su Cat 5, nisu oštećeni.

Osim navedenog, na mreži ima 4 Netis rutera, koji su postavljeni u bridge/AP mod i služe samo da naprave hotspot.

Code:

C:\Users\Milan>ping -n 10000 192.168.1.135

Pinging 192.168.1.135 with 32 bytes of data:
Reply from 192.168.1.135: bytes=32 time=224ms TTL=64
Reply from 192.168.1.135: bytes=32 time=169ms TTL=64
Reply from 192.168.1.135: bytes=32 time=670ms TTL=64
Reply from 192.168.1.135: bytes=32 time=693ms TTL=64
Reply from 192.168.1.135: bytes=32 time=711ms TTL=64
Reply from 192.168.1.135: bytes=32 time=736ms TTL=64
Reply from 192.168.1.135: bytes=32 time=740ms TTL=64
Reply from 192.168.1.135: bytes=32 time=783ms TTL=64
Reply from 192.168.1.135: bytes=32 time=845ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time=28ms TTL=64
Reply from 192.168.1.135: bytes=32 time=47ms TTL=64
Reply from 192.168.1.135: bytes=32 time=76ms TTL=64
Reply from 192.168.1.135: bytes=32 time=113ms TTL=64
Reply from 192.168.1.135: bytes=32 time=130ms TTL=64
Reply from 192.168.1.135: bytes=32 time=178ms TTL=64
Reply from 192.168.1.135: bytes=32 time=245ms TTL=64
Reply from 192.168.1.135: bytes=32 time=308ms TTL=64
Reply from 192.168.1.135: bytes=32 time=322ms TTL=64
Reply from 192.168.1.135: bytes=32 time=366ms TTL=64

Ping statistics for 192.168.1.135:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 845ms, Average = 321ms
Control-C
^C
C:\Users\Milan>

Edit: Zaboravih da napomenem, multicast počne da secka dok na kraju se ne zakuca skroz. Tada ponekad dobijem poruku Host unreachable.

Odgovor na temu

Milan Kragujevic
Software Engineer

Član broj: 231903
Poruke: 2220
*.dynamic.vipmobile.rs.

Sajt: https://milankragujevic.c..

+201 Profil

Re: Multicast i neverovatno veliki ping na OpenWRT ruteru posle pola sata rada

^{30.06.2018. u 12:38 - pre 70 meseci}

Manje ili jedan 1ms.

Code:

C:\Users\Milan>ping -n 10000 192.168.1.135

Pinging 192.168.1.135 with 32 bytes of data:
Reply from 192.168.1.135: bytes=32 time=1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64
Reply from 192.168.1.135: bytes=32 time=1ms TTL=64
Reply from 192.168.1.135: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.135:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Control-C
^C
C:\Users\Milan>

Odgovor na temu