Netgear R6250 (Dual ARM, 256MB Ram, 128MB Flash)

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4, 5  Next
View previous topic :: View next topic  
Author Message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Thu Jun 12, 2014 19:17    Post subject: Reply with quote
This is pinging the 2.4ghz, ch 1, 20 mhz.


^C
C:\Users\Joe-Laptop>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=82ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=96ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=60ms TTL=64
Reply from 192.168.1.1: bytes=32 time=156ms TTL=64
Reply from 192.168.1.1: bytes=32 time=129ms TTL=64
Reply from 192.168.1.1: bytes=32 time=166ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=173ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=170ms TTL=64
Reply from 192.168.1.1: bytes=32 time=137ms TTL=64
Reply from 192.168.1.1: bytes=32 time=166ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=196ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=170ms TTL=64
Reply from 192.168.1.1: bytes=32 time=138ms TTL=64
Reply from 192.168.1.1: bytes=32 time=150ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 21, Received = 21, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 196ms, Average = 96ms
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
Sponsor
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Thu Jun 12, 2014 20:09    Post subject: Reply with quote
I'll try the new bin next.
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany
PostPosted: Thu Jun 12, 2014 20:09    Post subject: Reply with quote
Malachi wrote:
This is pinging the 2.4ghz, ch 1, 20 mhz.


^C
C:\Users\Joe-Laptop>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=82ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=96ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=60ms TTL=64
Reply from 192.168.1.1: bytes=32 time=156ms TTL=64
Reply from 192.168.1.1: bytes=32 time=129ms TTL=64
Reply from 192.168.1.1: bytes=32 time=166ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=173ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=170ms TTL=64
Reply from 192.168.1.1: bytes=32 time=137ms TTL=64
Reply from 192.168.1.1: bytes=32 time=166ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=196ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=170ms TTL=64
Reply from 192.168.1.1: bytes=32 time=138ms TTL=64
Reply from 192.168.1.1: bytes=32 time=150ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 21, Received = 21, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 196ms, Average = 96ms


That's not normal, see mine:


C:\WINDOWS\system32>ping -t 192.168.0.1

Ping wird ausgeführt für 192.168.0.1 mit 32 Bytes Daten:
Antwort von 192.168.0.1: Bytes=32 Zeit=2ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=2ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Thu Jun 12, 2014 20:33    Post subject: Reply with quote
I know it's not normal. Lol. Any idea why?
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Thu Jun 12, 2014 23:41    Post subject: Reply with quote
Using newd bin made no difference.
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
lepa71
DD-WRT User


Joined: 02 Feb 2012
Posts: 84
PostPosted: Fri Jun 13, 2014 0:23    Post subject: Reply with quote
Malachi

Are you using Intel 7260 AC card, by a chance?
Here is mine from above card
Started as

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=30ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=27ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=42ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64

after couple minutes running
Reply from 192.168.1.1: bytes=32 time=128ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=149ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=138ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=166ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=153ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=124ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=168ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=155ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=178ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=149ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=136ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=144ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=142ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=150ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=142ms TTL=64
Reply from 192.168.1.1: bytes=32 time=26ms TTL=64
Reply from 192.168.1.1: bytes=32 time=121ms TTL=64

This is on Stock netgear fw

My old dell 1490 abg card's ping in perfect
all after running for 5 minutes is less 1 ms
Back to top View user's profile Send private message
lepa71
DD-WRT User


Joined: 02 Feb 2012
Posts: 84
PostPosted: Fri Jun 13, 2014 0:37    Post subject: Reply with quote
Here my nvram show | grep pci

@kong
Could you look it? I'm on the latest netgear R6250 fw.

# wl ver
6.30 RC163.13
wl0: Jun 20 2013 17:40:57 version 6.30.163.2002 (r382208)

BusyBox v1.7.2 (2014-01-17 17:20:52 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

# nvram show | grep pci
pci/2/1/rxgains5ghtrisoa0=15
pci/2/1/rxgains5ghtrisoa1=15
pci/2/1/rxgains5ghtrisoa2=15
pci/1/1/pa2gw1a0=0x1870
pci/1/1/pa2gw1a1=0x1870
pci/2/1/mcslr5gmpo=0
pci/2/1/txchain=7
pci/2/1/phycal_tempdelta=255
pci/2/1/pdgain5g=10
pci/1/1/ledbh12=11
pci/2/1/subband5gver=0x4
pci/2/1/ccode=Q2
pci/2/1/boardflags=0x10001000
pci/2/1/tworangetssi5g=0
pci/2/1/rxgains5gtrisoa0=6
pci/2/1/sb20in40hrpo=0
pci/2/1/rxgains5gtrisoa1=6
pci/2/1/rxgains5gtrisoa2=6
pci/2/1/tempoffset=255
pci/2/1/mcsbw205gmpo=0xEC200000
pci/2/1/noiselvl5ga0=31,31,31,31
pci/2/1/noiselvl5ga1=31,31,31,31
pci/1/1/ag0=2
pci/2/1/noiselvl5ga2=31,31,31,31
pci/1/1/ag1=2
pci/1/1/ag2=255
pci/2/1/xtalfreq=65535
pci/2/1/tempsense_option=0x3
pci/2/1/devid=0x43a2
pci/2/1/femctrl=6
pci/2/1/aa5g=7
pci/2/1/pdoffset80ma0=256
pci/2/1/pdoffset80ma1=256
pci/2/1/cckbw20ul2gpo=0
pci/2/1/pdoffset80ma2=256
pci/2/1/papdcap5g=0
pci/1/1/rxchain=3
pci/2/1/tssiposslope5g=1
pci/2/1/tempcorrx=0x3f
pci/1/1/bw402gpo=
pci/1/1/pa2gw0a0=0xff15
pci/1/1/pa2gw0a1=0xff15
pci/2/1/mcslr5glpo=0
pci/2/1/mcsbw402gpo=2571386880
pci/2/1/sar5g=15
pci/1/1/boardflags=0x80001200
pci/2/1/macaddr=28:C6:8E:6F:F0:88
pci/2/1/pa5ga0=0xff7a,0x16a9,0xfd4b,0xff6e,0x1691,0xfd47,0xff7e,0x17b8,0xfd37,0xff82,0x17fb,0xfd3a
pci/2/1/pa5ga1=0xff66,0x1519,0xfd65,0xff72,0x15ff,0xfd56,0xff7f,0x16ee,0xfd4b,0xffad,0x174b,0xfd81
pci/2/1/rxgains5gmelnagaina0=7
pci/2/1/pa5ga2=0xff76,0x168e,0xfd50,0xff75,0x16d0,0xfd4b,0xff86,0x17fe,0xfd39,0xff7e,0x1810,0xfd31
pci/2/1/rxgains5gmelnagaina1=7
pci/1/1/tempoffset=0
pci/2/1/rxgains5gmelnagaina2=7
pci/1/1/ofdm5gpo=0
pci/2/1/mcslr5ghpo=0
pci/2/1/rxgainerr5ga0=63,63,63,63
pci/2/1/mcsbw202gpo=2571386880
pci/2/1/rxgainerr5ga1=31,31,31,31
pci/2/1/rxgainerr5ga2=31,31,31,31
pci/2/1/pcieingress_war=15
pci/2/1/pdoffset40ma0=12834
pci/2/1/pdoffset40ma1=12834
pci/2/1/pdoffset40ma2=12834
pci/1/1/boardvendor=0x14e4
pci/2/1/sb40and80lr5gmpo=0
pci/2/1/rxgains5gelnagaina0=3
pci/2/1/rxgains5gelnagaina1=3
pci/2/1/rxgains5gelnagaina2=3
pci/2/1/mcsbw205glpo=0xEC200000
pci/1/1/triso2g=4
pci/2/1/measpower1=0x7f
pci/1/1/sromrev=8
pci/2/1/sb20in80and160lr5gmpo=0
pci/2/1/measpower2=0x7f
pci/1/1/extpagain2g=3
pci/2/1/temps_period=15
pci/1/1/venid=0x14e4
pci/2/1/mcsbw805gmpo=0xEC500000
pci/2/1/dot11agduplrpo=0
pci/2/1/mcsbw205ghpo=0xFC652000
wl0_pcie_mrrs=128
pci/2/1/measpower=0x7f
pci/2/1/rxgains5ghelnagaina0=7
pci/2/1/ofdmlrbw202gpo=0
pci/2/1/rxgains5ghelnagaina1=7
pci/2/1/rxgains5ghelnagaina2=7
pci/1/1/maxp2ga0=0x66
pci/1/1/maxp2ga1=0x66
pci/2/1/gainctrlsph=0
pci/2/1/sb40and80hr5gmpo=0
pci/1/1/boardtype=0x62b
pci/2/1/sb20in80and160hr5gmpo=0
pci/2/1/mcsbw1605gmpo=0
pci/1/1/boardflags2= 0x9800
pci/1/1/tssipos2g=1
pci/2/1/epagain5g=0
pci/2/1/mcsbw405gmpo=0xEC300000
pci/1/1/ofdm2gpo=0xA8640000
pci/1/1/ledbh0=255
pci/1/1/ledbh1=255
pci/1/1/ledbh2=255
pci/1/1/ledbh3=131
pci/2/1/cckbw202gpo=0
pci/2/1/rxchain=7
pci/1/1/mcs2gpo0=0x4000
pci/1/1/mcs2gpo1=0xCA86
pci/1/1/mcs2gpo2=0x4000
pci/1/1/mcs2gpo3=0xCA86
pci/1/1/mcs2gpo4=0x7422
pci/1/1/antswctl2g=0
pci/2/1/sb40and80lr5glpo=0
pci/1/1/mcs2gpo5=0xEDB9
pci/1/1/mcs2gpo6=0x7422
pci/2/1/maxp5ga0=72,72,94,94
pci/1/1/mcs2gpo7=0xEDB9
pci/1/1/stbc2gpo=
pci/2/1/maxp5ga1=72,72,94,94
pci/2/1/maxp5ga2=72,72,94,94
pci/1/1/txchain=3
pci/1/1/elna2g=2
pci/2/1/sb20in80and160lr5glpo=0
pci/1/1/ofdm5glpo=0
pci/2/1/sb40and80lr5ghpo=0
pci/1/1/antswitch=0
pci/1/1/aa2g=3
pci/2/1/venid=0x14e4
pci/2/1/mcsbw805glpo=0xEC500000
pci/1/1/ccd2gpo=
pci/2/1/boardvendor=0x14e4
pci/2/1/sb20in80and160lr5ghpo=0
pci/2/1/tempsense_slope=0xff
pci/1/1/ofdm5ghpo=0
pci/2/1/ofdm5glpo=0
pci/2/1/mcsbw805ghpo=0xFC986300
pci/2/1/antswitch=0
pci/2/1/aga0=71
pci/2/1/aga1=133
pci/2/1/rawtempsense=0x1ff
pci/2/1/aga2=133
pci/1/1/leddc=65535
pci/2/1/tempthresh=255
pci/1/1/pa2gw2a0=0xfad3
pci/1/1/pa2gw2a1=0xfad3
pci/2/1/dot11agduphrpo=0
pci/2/1/ofdm5ghpo=0x52000000
pci/2/1/sb40and80hr5glpo=0
pci/2/1/sromrev=11
wl_pcie_mrrs=128
pci/2/1/sb20in40lrpo=0
pci/2/1/sb20in80and160hr5glpo=0
pci/2/1/mcsbw1605glpo=0
pci/2/1/sb40and80hr5ghpo=0
wl1_pcie_mrrs=128
pci/1/1/opo=68
pci/2/1/mcsbw405glpo=0xEC300000
pci/2/1/dot11agofdmhrbw202gpo=17408
pci/2/1/rxgains5gmtrisoa0=15
pci/2/1/sb20in80and160hr5ghpo=0
pci/2/1/mcsbw1605ghpo=0
pci/1/1/ccode=Q2
pci/2/1/rxgains5gmtrisoa1=15
pci/2/1/rxgains5gmtrisoa2=15
pci/2/1/rxgains5gmtrelnabypa0=1
pci/2/1/rxgains5gmtrelnabypa1=1
pci/2/1/rxgains5gmtrelnabypa2=1
pci/2/1/mcsbw405ghpo=0xFC764100
size: 32779 bytes (32757 left)
pci/2/1/boardflags2=0x2
pci/2/1/boardflags3=0x0
pci/1/1/pdetrange2g=3
pci/1/1/regrev=42
pci/2/1/rxgains5ghtrelnabypa0=1
pci/2/1/rxgains5ghtrelnabypa1=1
pci/2/1/rxgains5ghtrelnabypa2=1
pci/2/1/regrev=42
pci/1/1/devid=0x43a9
pci/1/1/tempthresh=120
pci/1/1/macaddr=28:C6:8E:6F:F0:89
pci/2/1/temps_hysteresis=15
pci/1/1/cck2gpo=0
pcie_force_gen1=on
pci/2/1/rxgains5gtrelnabypa0=1
pci/2/1/rxgains5gtrelnabypa1=1
pci/2/1/rxgains5gtrelnabypa2=1
#
#
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Fri Jun 13, 2014 0:59    Post subject: Reply with quote
I don't remember exactly what it is. It's a Broadcom 43xx something. I've had it for years.
Tomorrow I'll try with my other laptop, it has an intel 5100.
My pings were from Kong's builds.
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Fri Jun 13, 2014 1:31    Post subject: Reply with quote
These are the pings from a laptop with an intel 5100.
The router is running 24200M, 2.4ghz.

C:\Users\Dell>ping 192.168.1.1 -t

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=85ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=18ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=15ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=14ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=11ms TTL=64
Reply from 192.168.1.1: bytes=32 time=12ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=16ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=43ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=74ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 132, Received = 125, Lost = 7
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 85ms, Average = 6ms


Note the sudden spikes then the 6 timouts.
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany
PostPosted: Fri Jun 13, 2014 10:09    Post subject: Reply with quote
I have done a long term ping test now, on one client (intel) I managed to have one lost package, but pings are pretty normal. The best pings are with a realtek client, they are constant between 1 and 2ms.

If you have good pings with stock, it probably rules out problems with nearby bluetooth devices/wireless routers but I would play with wireless interference settings.

Also I have done pings between two routers over wireless there I get pretty much constant 1ms. Thus the driver looks ok, may have some issues with certain clients, but for you it doesn't seem to make a difference.
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Fri Jun 13, 2014 10:18    Post subject: Reply with quote
What do you mean by wireless interference settings?
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany
PostPosted: Fri Jun 13, 2014 11:19    Post subject: Reply with quote
Malachi wrote:
What do you mean by wireless interference settings?


root@xxx:~# wl -i eth1 interference

Non-wireless LAN Interference mitigation is enabled. (mode 1)


Possible modes are:

0 = none
1 = non wlan
2 = wlan manual
3 = wlan automatic
4 = wlan automatic with noise reduction
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Back to top View user's profile Send private message
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio
PostPosted: Fri Jun 13, 2014 12:35    Post subject: Reply with quote
Forgive me I'm new at this. Not sure what I do with that.
_________________
I am far from a guru, I'm barely a novice.
Back to top View user's profile Send private message
lepa71
DD-WRT User


Joined: 02 Feb 2012
Posts: 84
PostPosted: Fri Jun 13, 2014 13:41    Post subject: Reply with quote
Kong

Is this only for dd-wrt fw or I can do this on stock as well?
How do I set it to a different mode?

Thanks

<Kong> wrote:
Malachi wrote:
What do you mean by wireless interference settings?


root@xxx:~# wl -i eth1 interference

Non-wireless LAN Interference mitigation is enabled. (mode 1)


Possible modes are:

0 = none
1 = non wlan
2 = wlan manual
3 = wlan automatic
4 = wlan automatic with noise reduction
Back to top View user's profile Send private message
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany
PostPosted: Fri Jun 13, 2014 16:14    Post subject: Reply with quote
Malachi wrote:
Forgive me I'm new at this. Not sure what I do with that.


Logon via ssh and run the command:

wl -i eth1 interference 0

To switch off mitigation, or

wl -i eth1 interference 4

...
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Back to top View user's profile Send private message
Goto page Previous  1, 2, 3, 4, 5  Next Display posts from previous:    Page 4 of 5
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum