Article View: alt.pl.wirelesslan
Article #29716cos nie tak z linkiem?
From: michael
Date: Wed, 30 Nov 2005 11:38
Date: Wed, 30 Nov 2005 11:38
35 lines
3023 bytes
3023 bytes
witam, mam problem z sygnalem na linku niecale 7km a mianowicie jest sprzet 2 AP planet 1960, przy jednym parabola interline 23db a przy drugim typu grid 17db (dokladnie taka http://www.allegro.pl/show_item.php?item=72354914). i teraz tak, mierząc sygnał z grida netstumblerem wynosi -65db stabilny i gesty bez zadnych przerw, w druga strone podobnie, a jednak po zestawieniu polaczenia na apekach internet dziala tragicznie a ping napiera duplikatami: 64 bytes from 192.168.1.201: icmp_seq=1 ttl=127 time=10.1 ms 64 bytes from 192.168.1.201: icmp_seq=1 ttl=127 time=11.4 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=1 ttl=127 time=13.3 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=1 ttl=127 time=15.7 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=1 ttl=127 time=17.5 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=2.81 ms 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=3.83 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=5.72 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=8.76 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=12.7 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=18.3 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=27.7 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=29.4 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=30.7 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=2 ttl=127 time=31.7 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=4 ttl=127 time=2.51 ms 64 bytes from 192.168.1.201: icmp_seq=4 ttl=127 time=3.32 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=4 ttl=127 time=5.71 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=4 ttl=127 time=8.65 ms (DUP!) 64 bytes from 192.168.1.201: icmp_seq=4 ttl=127 time=9.56 ms (DUP!) i co z tym poczac, gdzie szukac winy? acha, apeki ustawione w tryb bridza na kanale 1-szym bez kodowania. dodam jeszcze ze warunki niemal idealne, teren wysoko w gorach, widocznosc rewelacyjna, praktycznie brak jakichkolwiek zaklocen. z gory dzieki za sugestie i pomoc, michael
Technical Details
Message-ID:
<dmk30i$ei9$1@atlantis.news.tpi.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!newsfeed.gazeta.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mailShow Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!newsfeed.gazeta.pl!news.nask.pl!news.nask.org.pl!newsfeed.tpinternet.pl!atlantis.news.tpi.pl!news.tpi.pl!not-for-mail From: "michael" <michael@gower.pl> Newsgroups: alt.pl.wirelesslan Subject: cos nie tak z linkiem? Date: Wed, 30 Nov 2005 12:38:45 +0100 Organization: tp.internet - http://www.tpi.pl/ Lines: 37 Message-ID: <dmk30i$ei9$1@atlantis.news.tpi.pl> NNTP-Posting-Host: buj86.internetdsl.tpnet.pl X-Trace: atlantis.news.tpi.pl 1133350739 14921 83.18.165.86 (30 Nov 2005 11:38:59 GMT) X-Complaints-To: usenet@tpi.pl NNTP-Posting-Date: Wed, 30 Nov 2005 11:38:59 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-RFC2646: Format=Flowed; Original MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit