Spoj INRI <-------> Barbucha

Zdar, Semi na node INRI hlasil potize se spojenim mezi node INRI a zbytkem site. Na INRI pingne bez problemu, dal ma veliky packetloss a ukrutny response time: [code:1]root@barbucha:~# ping 10.92.16.75 PING 10.92.16.75 (10.92.16.75) 56(84) bytes of data. 64 bytes from 10.92.16.75: icmp_seq=1 ttl=64 time=1975 ms 64 bytes from 10.92.16.75: icmp_seq=2 ttl=64 time=1829 ms 64 bytes from 10.92.16.75: icmp_seq=3 ttl=64 time=1993 ms 64 bytes from 10.92.16.75: icmp_seq=4 ttl=64 time=2170 ms 64 bytes from 10.92.16.75: icmp_seq=5 ttl=64 time=2720 ms 64 bytes from 10.92.16.75: icmp_seq=6 ttl=64 time=2721 ms 64 bytes from 10.92.16.75: icmp_seq=7 ttl=64 time=2535 ms 64 bytes from 10.92.16.75: icmp_seq=8 ttl=64 time=2780 ms --- 10.92.16.75 ping statistics --- 11 packets transmitted, 8 received, 27% packet loss, time 10072ms rtt min/avg/max/mdev = 1829.820/2340.911/2780.171/364.834 ms, pipe 3 [/code:1] INRI visi jako klient na AirCA na Barbuse. Spolu s ni tam visi i klient AirCA na druidovy. Tenhle spoj jede bez problemu: [code:1] root@barbucha:~# ping 10.92.0.5 PING 10.92.0.5 (10.92.0.5) 56(84) bytes of data. 64 bytes from 10.92.0.5: icmp_seq=1 ttl=63 time=2.19 ms 64 bytes from 10.92.0.5: icmp_seq=2 ttl=63 time=1.77 ms 64 bytes from 10.92.0.5: icmp_seq=3 ttl=63 time=1.79 ms 64 bytes from 10.92.0.5: icmp_seq=4 ttl=63 time=1.80 ms 64 bytes from 10.92.0.5: icmp_seq=5 ttl=63 time=1.79 ms 64 bytes from 10.92.0.5: icmp_seq=6 ttl=63 time=1.78 ms 64 bytes from 10.92.0.5: icmp_seq=7 ttl=63 time=1.79 ms --- 10.92.0.5 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6053ms rtt min/avg/max/mdev = 1.770/1.848/2.199/0.154 ms [/code:1] Zkusil jsem presto AirCA AP rebootnout. Klient Druid se nakonektil bez problemu s urovni cca -50 dBm: [code:1]root@D2B-ap:~# iwconfig ath0 ath0 IEEE 802.11a ESSID:"CZFree.Net.b-di" Mode:Managed Frequency:5.22 GHz Access Point: 00:0B:6B:3F:27:BA Bit Rate:54 Mb/s Tx-Power:17 dBm Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=45/94 Signal level=-50 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 [/code:1] INRI se ale uz nechytnul, prestoze spravne AP naskenoval i s dobrou urovni -55 dBm, ale bez SSID [code:1]Cell 01 - bssid: 00:0B:6B:3F:27:BA ssid "" mode: 802.11a (5.22GHz) signal level: -55dbm [/code:1] Po cca 20minutach se preci jen chytil, vykonost linky je opravdu impresivni, avg response time skoro 4 vteriny :-( [code:1]root@barbucha:~# ping 10.92.16.75 PING 10.92.16.75 (10.92.16.75) 56(84) bytes of data. 64 bytes from 10.92.16.75: icmp_seq=1 ttl=64 time=4492 ms 64 bytes from 10.92.16.75: icmp_seq=2 ttl=64 time=4803 ms 64 bytes from 10.92.16.75: icmp_seq=3 ttl=64 time=5190 ms 64 bytes from 10.92.16.75: icmp_seq=4 ttl=64 time=4601 ms 64 bytes from 10.92.16.75: icmp_seq=5 ttl=64 time=4550 ms 64 bytes from 10.92.16.75: icmp_seq=6 ttl=64 time=3781 ms 64 bytes from 10.92.16.75: icmp_seq=7 ttl=64 time=3251 ms 64 bytes from 10.92.16.75: icmp_seq=8 ttl=64 time=3056 ms 64 bytes from 10.92.16.75: icmp_seq=9 ttl=64 time=3195 ms 64 bytes from 10.92.16.75: icmp_seq=10 ttl=64 time=2860 ms 64 bytes from 10.92.16.75: icmp_seq=11 ttl=64 time=3199 ms 64 bytes from 10.92.16.75: icmp_seq=12 ttl=64 time=3431 ms 64 bytes from 10.92.16.75: icmp_seq=13 ttl=64 time=3372 ms 64 bytes from 10.92.16.75: icmp_seq=14 ttl=64 time=3130 ms --- 10.92.16.75 ping statistics --- 17 packets transmitted, 14 received, 17% packet loss, time 16099ms rtt min/avg/max/mdev = 2860.682/3779.755/5190.111/748.736 ms, pipe 6 [/code:1] upravil jsem tedy routing tak aby spoj mezi INRI a Barbucha nebyl preferovan a traffic sel pres Faraona (uprava ospf cost mezi barbucha a INRI, druid AirCA z 200 na 750). Nez prijdeme na to cim to je (vitam napady) tak to tak zustane. Pak routing vratim tak jak ma byt. Tenis