PDA

Bekijk de volledige versie : WL500g (Oleg 1.9.2.7-7e) + "DC++" = big ping on LAN?



jimmy_cr
22-08-2006, 11:54
Hi, I've found this problem at my WL500g. Router connected to internet through WAN port, LAN ports + WLAN = local stations (at home). When I connect 1 computer to LAN port and run DC++ on that PC - DC++ is working well, but sometimes I need to remotely-operate on this PC and that's the problem. I'm using RemoteAdmin software and sometimes I'm not able to connect to RA neither connect to ASUS web configuration or telnet from WAN side (internet). When the DC++ is shut-down, I can work normally with RA and also with ASUS web configuration. It look strange for me, because DC++ is limited (internal DC++ limiter) to use only 512kbps (64kBps) in both directions (I've set a Virtual Server for DC++ ports because I need to do NAT). So I tried to telnet to my WL500g and I tried to ping to my LAN computer. Look what I saw when DC++ running:



[admin@jimmy_wl500g root]$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: icmp_seq=0 ttl=128 time=1.4 ms
64 bytes from 192.168.1.100: icmp_seq=1 ttl=128 time=28.3 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=128 time=171.5 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=128 time=42.5 ms
64 bytes from 192.168.1.100: icmp_seq=4 ttl=128 time=264.4 ms
64 bytes from 192.168.1.100: icmp_seq=5 ttl=128 time=275.2 ms
64 bytes from 192.168.1.100: icmp_seq=6 ttl=128 time=41.3 ms
64 bytes from 192.168.1.100: icmp_seq=7 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=8 ttl=128 time=39.2 ms
64 bytes from 192.168.1.100: icmp_seq=9 ttl=128 time=43.1 ms
64 bytes from 192.168.1.100: icmp_seq=10 ttl=128 time=1.1 ms
64 bytes from 192.168.1.100: icmp_seq=11 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=12 ttl=128 time=270.7 ms
64 bytes from 192.168.1.100: icmp_seq=13 ttl=128 time=253.6 ms
64 bytes from 192.168.1.100: icmp_seq=14 ttl=128 time=240.8 ms
64 bytes from 192.168.1.100: icmp_seq=15 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=16 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=17 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=18 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=19 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=20 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=21 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=22 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=23 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=24 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=25 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=26 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=27 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=28 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=29 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=30 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=31 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=32 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=33 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=34 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=35 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=36 ttl=128 time=2.4 ms
64 bytes from 192.168.1.100: icmp_seq=37 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=38 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=39 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=40 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=41 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=42 ttl=128 time=543.1 ms
64 bytes from 192.168.1.100: icmp_seq=43 ttl=128 time=94.5 ms
64 bytes from 192.168.1.100: icmp_seq=44 ttl=128 time=842.8 ms
64 bytes from 192.168.1.100: icmp_seq=45 ttl=128 time=384.6 ms
64 bytes from 192.168.1.100: icmp_seq=46 ttl=128 time=261.3 ms
64 bytes from 192.168.1.100: icmp_seq=47 ttl=128 time=245.3 ms
64 bytes from 192.168.1.100: icmp_seq=48 ttl=128 time=227.0 ms
64 bytes from 192.168.1.100: icmp_seq=49 ttl=128 time=102.9 ms
64 bytes from 192.168.1.100: icmp_seq=50 ttl=128 time=1.0 ms
64 bytes from 192.168.1.100: icmp_seq=51 ttl=128 time=71.5 ms


Is it normal? How to track where's problem? Lots of connections at one time? Can anybody advice?

Styno
22-08-2006, 12:30
Is it a 'WL-500g' or 'WL-500g Deluxe'?

jimmy_cr
22-08-2006, 13:38
WL-500g (as I wrote ;) )

I probably know you're pointing at - CPU speed of "NONDeluxe"? It's just 1 wired client (TOP shows cca 6% CPU utilisation) connected!

EDIT: Now with DC++ ping 1ms, but still problem to connect to RemoteAdmin / ASUS Web configuration - shouldn't be problem this:
http://wl500g.info/showpost.php?p=34013&postcount=155
I have same networking card...

But when opening ASUS Web configuration remotely, it's going through WAN only :-/ so it's independent to enviroment connected to LAN