Re: lug-bg: DUP!
- Subject: Re: lug-bg: DUP!
- From: kolp <kolp@xxxxxxxxxxx>
- Date: Sat, 4 Oct 2003 19:08:01 +0300
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 04 October 2003 10:15 pm, YaneV wrote:
> Zdraweite
>
>
> situachiikata e
>
> wireless wireless
> [ras] <------------------>[switch]<------------------>[losh klient]
>
> | | wireless
> |
> | +-<-------------->[klient1]
>
> +-[klient2]
>
>
>
> wireless-a do [losh klient] e na dosta golqmo rastoqnie poradi koeto ima
> mnogo duplicate paketi
>
> # ping 213.169.61.195
> PING 213.169.61.195 (213.169.61.195) from 212.36.13.66 : 56(84) bytes of
> data. 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=25.3 ms
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=26.1 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=33.4 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=37.8 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=45.3 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=49.3 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=50.3 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=55.2 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=57.5 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=59.2 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=62.3 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=63.5 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=1 ttl=63 time=80.5 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=11.2 ms
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=18.9 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=21.2 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=23.3 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=29.2 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=36.0 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=39.6 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=44.0 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=44.9 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=48.7 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=69.6 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=76.1 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=77.1 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=90.9 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=101 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=103 ms (DUP!)
> 64 bytes from 213.169.61.195: icmp_seq=2 ttl=63 time=110 ms (DUP!)
>
> --- 213.169.61.195 ping statistics ---
> 2 packets transmitted, 2 received, +28 duplicates, 0% loss, time 1004ms
> rtt min/avg/max/mdev = 11.234/53.085/110.395/25.945 ms
>
> horata koito sa puskali wirelessa kazwat che po dobre nemozelo za uslowiqta
>
> qwno duplicate paketite (ili znam li kakwo) sa prichinata poradi koqto i
> werelessa do [ras] mashinata se pretowarwa i wsichki klienti ostawat pochti
> bez nikakuw dostup do [ras]
>
> w momenta w koito [losh klient] se izkluchat ot switcha sichko se oprawq i
> [klinet2] zapochwa da transwerwa s mad 1500 Kbit
>
> ima shaper koito e pri [losh klient] koito go orqzwa na 320 kbit (dosta po
> malko ot 1500) no w momenta w koito prawi kakuwto i da e trafik sichko se
> zadrustwa
>
>
> Nqkakwo predlozenie kak da se otturwa ot duplicatite ako te sa problema de
> ... ili kakwo drugo moze da e problema ... probwal sum da smenq [swutc] s
> linuksko routerche no efekta behse sushtiq
>
>
> Nqkakwi idei .....
dup packetite po definicia se poluchavat, kogato se gubi acknowledgement
che polucheni ot otsreshtnata strana i sendera e prinuden da re-transmitva.
variantite mogat da sa kolkoto iskash - losho oborudvane, goliamo
razstoianie, zaglushavane na chestotata (umishleno ili ne) i t.n. syvetyt mi
e da procedirash taka:
ot stranata na `loshia' klient probvai da "ogledash" iz efira kakvo stava -
kef ti airsnort, kef ti kismet, wellenreiter i pr. pyrvo vij obache dali
drivera ti poddyrja monitor rejim, kato tyrsish slednia red s `iwpriv':
monitor (8BE8) : set 2 int & get 0
nakraia mojesh da opitash da slojish oshte edin access point pred loshia
klient i da go narochish za repeater; daje e hubavo da predava na drug
channel.
uspeh,
kp.
- --
Key Server: pgp.ai.mit.edu
Key ID: 0xB304804D
Key Fingerprint: DA0C 2A46 5D50 0932 73C2 BD9E A25A A5BB B304 804D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/fvBlolqlu7MEgE0RAl6VAKDCcfH5S+9N34K8dKLexKVJcouekACbBxUl
3rncvE9MFrnop3GMCCjydJY=
=BghQ
-----END PGP SIGNATURE-----
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
============================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers).
http://www.linux-bulgaria.org - Hosted by Internet Group Ltd. - Stara Zagora
To unsubscribe: http://www.linux-bulgaria.org/public/mail_list.html
============================================================================
|