problem se shaperem

David Rohleder davro na ics.muni.cz
Úterý Leden 12 12:32:29 CET 1999


trcka na poda.cz (David Trcka) writes:

> Zdravim,
> 
> mam nasledujici problem se shaperem:
> 
> Mam stroj A se shaperem na 33600 spojeny ethernetem na stroj B.
> Konfigurace sitovych rozhrani i shaperu je bezna, vsechny hodnoty (krome IP
> adres pochopitelne) jsou vychozi (MTU apod.).
> 
> Na stroji A dam ping B -s 4000  --> jede OK:
> PING 194.228.42.126 (194.228.42.126): 4000 data bytes
> 4008 bytes from 194.228.42.126: icmp_seq=0 ttl=64 time=608.8 ms
> 4008 bytes from 194.228.42.126: icmp_seq=1 ttl=64 time=617.9 ms
> 4008 bytes from 194.228.42.126: icmp_seq=2 ttl=64 time=617.7 ms
> 4008 bytes from 194.228.42.126: icmp_seq=3 ttl=64 time=617.9 ms
> 4008 bytes from 194.228.42.126: icmp_seq=4 ttl=64 time=617.7 ms
> 4008 bytes from 194.228.42.126: icmp_seq=5 ttl=64 time=617.7 ms
> 4008 bytes from 194.228.42.126: icmp_seq=6 ttl=64 time=617.7 ms
> 4008 bytes from 194.228.42.126: icmp_seq=7 ttl=64 time=617.7 ms
> 4008 bytes from 194.228.42.126: icmp_seq=8 ttl=64 time=617.9 ms
> 4008 bytes from 194.228.42.126: icmp_seq=9 ttl=64 time=617.7 ms
> ..atd
> 
> Na stroji A dam ping B -s 5000  --> dela toto:
> PING 194.228.42.126 (194.228.42.126): 5000 data bytes
> 5008 bytes from 194.228.42.126: icmp_seq=0 ttl=64 time=862.1 ms
> 5008 bytes from 194.228.42.126: icmp_seq=1 ttl=64 time=1089.2 ms
> 5008 bytes from 194.228.42.126: icmp_seq=2 ttl=64 time=1309.2 ms
> 5008 bytes from 194.228.42.126: icmp_seq=3 ttl=64 time=1529.1 ms
> 5008 bytes from 194.228.42.126: icmp_seq=4 ttl=64 time=1749.0 ms
> 5008 bytes from 194.228.42.126: icmp_seq=5 ttl=64 time=1969.5 ms
> 5008 bytes from 194.228.42.126: icmp_seq=6 ttl=64 time=2189.1 ms
> 5008 bytes from 194.228.42.126: icmp_seq=7 ttl=64 time=2409.0 ms
> 5008 bytes from 194.228.42.126: icmp_seq=8 ttl=64 time=2629.0 ms
> 5008 bytes from 194.228.42.126: icmp_seq=13 ttl=64 time=3229.3 ms
> 5008 bytes from 194.228.42.126: icmp_seq=14 ttl=64 time=3449.0 ms
> ..konec, dalsi pingy v tomto pripade neprojdou. Navic uvazne jakakoliv
> dalsi komunikace ke stroji B, ktera krome toho do te doby jela, dokud
> neprerusim ping.
> 
> Totez dela i opacne pri pingu z B na A.
> Dela to na ruznych verzich shaperu i jadra pocinaje 2.0.34 konce 2.0.36.
> Zhruba tusim, ze to souvisi s tim, ze na nastavene rychlosti jaksi neni
> mozne v rozumne dobe odeslat treba petikilovy paket. Jenomze co s tim,
> takove pakety museji projit!
> 
> Mate nekdo nejaky napad?

Muzete nejak bliz vysvetlit smysl vaseho pocinani? Kdyz neco
shapujete, tak se nemuzete divit, ze ICMP nema flow-control a ze bude
ostatni pakety brzdit, dokonce tak, ze mohou dochazet timeouty, nebo
pretecou buffery pro pakety, a pak se budou prichozi pakety zahazovat
a bude se zpet posilat ICMP source quench (treba na tu zaplnenou
linku)..

Otazka: proc musi prochazet petikilovy ping?


> 
> S pozdravem
> 
> David Trcka, PODA s.r.o., Havirov
> network administrator/spravce site
>           ICQ#: 24079192

-------------------------------------------------------------------------
David Rohleder						davro na ics.muni.cz
Institute of Computer Science, Masaryk University
Brno, Czech Republic
-------------------------------------------------------------------------


Další informace o konferenci Linux