xDSL.at

von **jutta** » Mo 31 Jul, 2006 13:09

ein "nettes" beispiel, welche effekte man mit amule/emule erzeugen kann:

Code: Alles auswählen: jutta@compaq:~$ ping -c 100 ping.inode.at PING ping.inode.at (195.58.160.103) 56(84) bytes of data. 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=1 ttl=61 time=2560 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=4 ttl=61 time=2486 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=5 ttl=61 time=2371 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=7 ttl=61 time=2880 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=8 ttl=61 time=2789 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=9 ttl=61 time=2548 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=10 ttl=61 time=2270 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=11 ttl=61 time=2173 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=12 ttl=61 time=2309 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=13 ttl=61 time=2414 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=16 ttl=61 time=2371 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=17 ttl=61 time=2226 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=19 ttl=61 time=2455 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=20 ttl=61 time=2215 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=22 ttl=61 time=2444 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=23 ttl=61 time=2388 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=25 ttl=61 time=2013 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=26 ttl=61 time=2049 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=27 ttl=61 time=2470 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=30 ttl=61 time=2808 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=31 ttl=61 time=2655 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=33 ttl=61 time=1966 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=34 ttl=61 time=1939 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=35 ttl=61 time=2364 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=37 ttl=61 time=2622 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=39 ttl=61 time=2484 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=40 ttl=61 time=2389 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=41 ttl=61 time=2239 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=42 ttl=61 time=2402 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=43 ttl=61 time=2383 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=44 ttl=61 time=2464 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=45 ttl=61 time=2066 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=46 ttl=61 time=2008 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=47 ttl=61 time=1991 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=48 ttl=61 time=2630 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=53 ttl=61 time=2211 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=54 ttl=61 time=2200 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=55 ttl=61 time=2047 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=56 ttl=61 time=2349 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=57 ttl=61 time=2483 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=58 ttl=61 time=2569 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=59 ttl=61 time=1876 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=60 ttl=61 time=2051 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=61 ttl=61 time=2567 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=62 ttl=61 time=2606 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=63 ttl=61 time=2680 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=64 ttl=61 time=2313 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=65 ttl=61 time=2217 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=66 ttl=61 time=2058 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=67 ttl=61 time=2489 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=68 ttl=61 time=2760 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=69 ttl=61 time=2790 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=70 ttl=61 time=2025 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=71 ttl=61 time=1826 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=72 ttl=61 time=1682 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=73 ttl=61 time=2637 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=74 ttl=61 time=2798 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=76 ttl=61 time=2480 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=77 ttl=61 time=2375 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=78 ttl=61 time=2453 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=79 ttl=61 time=2398 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=81 ttl=61 time=2462 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=82 ttl=61 time=2160 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=83 ttl=61 time=2149 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=84 ttl=61 time=2378 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=85 ttl=61 time=2914 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=86 ttl=61 time=2934 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=87 ttl=61 time=2772 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=88 ttl=61 time=2290 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=89 ttl=61 time=2288 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=90 ttl=61 time=2587 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=91 ttl=61 time=2354 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=92 ttl=61 time=2435 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=93 ttl=61 time=2053 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=94 ttl=61 time=2625 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=96 ttl=61 time=2836 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=97 ttl=61 time=2169 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=98 ttl=61 time=1973 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=99 ttl=61 time=2107 ms 64 bytes from ping.inode.at (195.58.160.103): icmp_seq=100 ttl=61 time=2406 ms --- ping.inode.at ping statistics --- 100 packets transmitted, 80 received, 20% packet loss, time 303350ms rtt min/avg/max/mdev = 1682.325/2371.373/2934.442/273.812 ms, pipe 3 jutta@compaq:~$

die pakete sind ein weniges laenger unterwegs als sonst, aber die meisten kommen doch noch an. die pppoe-session haelt unerschuetterlich (seit der einwahl gestern 13 uhr)

hw: compaq presario 2821 notebook. wlan karte: netgear wg511; os: linux (debian), einwahl mit pppoe.
modem: zyxel prestige 662hw. (vpn-mehrplatz config mit pppoe-bridge)

die ssh-session fuehlt sich wie ziemlich dickes erdaepfelpueree an

aber sie haelt.

stats:

Code: Alles auswählen: jutta@compaq:~$ vnstat -i ppp0 Database updated: Mon Jul 31 14:05:01 2006 ppp0 received: 2306 MB (34.1%) transmitted: 4450 MB (65.9%) total: 6756 MB rx | tx | total -----------------------+------------+----------- yesterday 570.70 MB | 1212 MB | 1783 MB today 1590 MB | 3178 MB | 4769 MB -----------------------+------------+----------- estimated 2706 MB | 5409 MB | 8115 MB jutta@compaq:~$

Code: Alles auswählen: jutta@compaq:~$ vnstat -i ppp0 -h ppp0 14:05 ^ t | t t t t t t t t t t t t t t t t t t | t t t t t t t t t t t t t t t t t t t | t t t t t t t t t t t t t t rt t t t t | t t t t t t t t t t t t t t rt rt t t rt | t t t t t t rt t rt t t t t t rt rt rt t rt | t t rt rt t rt rt rt t rt rt t rt rt rt rt rt rt rt rt | t rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt rt -+---------------------------------------------------------------------------> | 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 h rx (kB) tx (kB) h rx (kB) tx (kB) h rx (kB) tx (kB) 15 235 67 23 116025 231190 07 107761 230633 16 1445 223 00 95076 230230 08 110490 231397 17 251 67 01 136353 230428 09 167243 231748 18 57935 112960 02 89038 230232 10 146224 231785 19 75289 205987 03 121081 231230 11 117845 232904 20 95575 229419 04 111177 230023 12 97888 232228 21 100234 229543 05 77640 230526 13 150360 231767 22 85532 230821 06 93843 230559 14 6559 19332 jutta@compaq:~$

//edited ps: ergaenzung, weil es fragen gegeben hat:

die einstellungen habe ich bewusst "brutal" gewaehlt, weil ich testen wollte, ob modem und pppoe-session durchhalten. "normales" surfen ist bei einer rtt ueber 2000ms nicht mehr moeglich, da man meistens timeout-errors bekommt, detto gab es timeout bei whois-abfragen und aehnlichem. aus dem chat bin ich auch immer wieder rausgeflogen:

Code: Alles auswählen: [10:25] *** ju-c (jutta@=UW93-068-043-173.dynamic.xdsl-line.inode.at) has left IRC (Ping Timeout) [10:26] *** ju-c (jutta@=6n97-492-217-634.dynamic.xdsl-line.inode.at) has joined #gay [10:26] *** markus sets mode: +o ju-c [10:50] *** ju-c (jutta@=6n97-492-217-634.dynamic.xdsl-line.inode.at) has left IRC (Ping Timeout) [11:12] *** ju-c (jutta@=GF37-772-906-613.dynamic.xdsl-line.inode.at) has joined #gay [11:12] *** markus sets mode: +o ju-c [13:27] *** ju-c (jutta@=GF37-772-906-613.dynamic.xdsl-line.inode.at) has left IRC (Ping Timeout) [13:28] *** ju-c (jutta@=e796-426-288-861.dynamic.xdsl-line.inode.at) has joined #gay [13:28] *** markus sets mode: +o ju-c [15:42] *** ju-c (jutta@=e796-426-288-861.dynamic.xdsl-line.inode.at) has left IRC (Excess flood) [15:43] *** ju-c (jutta@=CH64-023-198-920.dynamic.xdsl-line.inode.at) has joined #gay [15:43] *** markus sets mode: +o ju-c [17:41] *** ju-c (jutta@=CH64-023-198-920.dynamic.xdsl-line.inode.at) has left IRC (Excess flood) [17:42] *** ju-c (jutta@=FR20-359-084-581.dynamic.xdsl-line.inode.at) has joined #gay [17:42] *** markus sets mode: +o ju-c

von **max_payne** » Mo 31 Jul, 2006 14:03

Und damit man den Erfolg des Programmes sieht, wäre es nett wenn du jetzt noch Cfosspeed testen würdest!

von **jutta** » Mo 31 Jul, 2006 14:15

gibts das als debian-paket?

btw: das modem kann bandwidth-management. bei der derzeitigen config ist das allerdings nicht sehr sinnvoll. ausserdem ging es mir darum, zunaechst rauszufinden, ob pppoe ueber wlan stabil funktioniert. (--> bug des p660hw)

von **max_payne** » Mo 31 Jul, 2006 14:23

gibts das als debian-paket?

nope, nur für win...

das modem kann bandwidth-management.

funktionierts auch?

von **jutta** » Mo 31 Jul, 2006 14:26

frag mich das in 3-4 wochen. es ist erst seit gestern in betrieb und bei der vpn-config kann ich mich nicht vorstellen, wie bandwidth-management funktionieren sollte.

xDSL.at

amule + ping

amule + ping

Wer ist online?