i've been lurking dd-wrt for some months now and tried different builds on my e4200; i guess i have some feedbacks to report.
where can i post them? couldn't we make a new thread where we speak about latest and greatest builds and what we shall issue/resolve...?
thanks.
EDIT
i am going to summarize what i found out till now.
i used to test builds in this configuration:
wl0 @ 2.4ghz g-only repeater with a virtual interface
wl1 @ 5ghz n-only ap
usb support on, samba client on.
i tested these builds so far:
dd-wrt.v24-16994_NEWD-2_K2.6_big-nv60k = ugly (lots of tx/rx errors everywhere, bad performance; didn't check well anything else)
dd-wrt.v24-17201_NEWD-2_K2.6_big-nv60k = repeater mode didn't work, clients in 2.4ghz band couldn't join the network created by virtual interface; if i recall correctly, usb support worked (/opt was mounting correctly); tx/rx errors here and there
dd-wrt.v24-17949_NEWD-2_K2.6_mega-nv60k = /opt was being mounted twice, making it unusable; tx/rx errors here and there; bad wl0 performance (didn't enable interface mitigation, yet)
r17940-usb-ftp-samba3-dlna-nv60k-broadcom kong mod = every partition mounts just fine, repeater mode works, small-to-none tx/rx error; moreover, after having turned interference mitigation on, i moved wl0 from a jerky 1/5.5/11mbps to a stable 48/54mbps rate - yeah. edit: got 400+ errors in wl0 and 50+ in wl1..
one sad thing is samba performance: with tomato i was getting some crazy speeds, as opposed to whichever dd-wrt build which gives me (much) worse performance.
i upgraded to samba 3.5.12.1 during my tests with build 17201 with no luck (stuck to the same, exact performance).
well, that's all.
any chance to see better samba performance ?
Last edited by m@rco on Wed Dec 07, 2011 8:30; edited 5 times in total
when i set the interference setting, i do it without a loop in the startup script and as long as i don't change any settings afterwards then it sticks just fine. 24hrs uptime and i can log into ssh server to confirm it is still set.
ErMeglio wrote:
What you speaking about here? The bluetooth coexistence mode setting on the web ui? Or is this simply the common name of the "wl interference 2" command ?
e4200 is has a 2.4ghz radio and a 5ghz radio. if i'm not mistaken, wl -i eth2 sets the 5ghz and thats what he's talking about. saying you can just use wl -i eth1 and set the 2.4ghz
are you guys judging connection purely based on transfer speed or are you looking at SNR status as well? i'm running my e4200 in client bridge mode and with 17201 i was dropping connections on my ps3 intermittently. 17949 with interference setting seems to be much improved but obviously thats a subjective statement. the SNR is still about 31-35 (i'm a fair distance from my main router) and SNR was about the same when i was on 17201. _________________ Linksys E4200 (17967)
i've been lurking dd-wrt for some months now and tried different builds on my e4200; i guess i have some feedbacks to report.
where can i post them? couldn't we make a new thread where we speak about latest and greatest builds and what we shall issue/resolve...?
thanks.
yeah your welcome to post them here, this thread is getting alot of exposure and informing the community is a good thing, and I am always open to ideas and feedback..
i've been lurking dd-wrt for some months now and tried different builds on my e4200; i guess i have some feedbacks to report.
where can i post them? couldn't we make a new thread where we speak about latest and greatest builds and what we shall issue/resolve...?
thanks.
yeah your welcome to post them here, this thread is getting alot of exposure and informing the community is a good thing, and I am always open to ideas and feedback..
-Fractal
thanks for your reply, i've edited my original message.
Intel 5100 AGN. As I was saying (don't remember if in this 3d or not, sorry) it's the same nic an user reported to be able to use @ 300Mbps (its max!) at 5Ghz with wl1. I tried all his settings, both on the client that on the router, with no luck at all. Even the interference didn't make any even slight difference.
I had all manner of issues with a 5100 way back on another laptop, which I upgraded to a 5300. Not saying this is the same for you, just pointing out my experience.
ErMeglio wrote:
I've tried N only 5Ghz, NA mixed, mixed in all the combinations with channels+width auto+auto, upper 161 and down+40mhz, auto+40mhz, and others, always the same results (sometimes worse).
Between all these (many) different tries two times I got the card "locked" at 300Mbps sending packets but receiving absolutely nothing, with counter at 0 and bandwith usage at 0%. I had to disable and re enable it. Oh, btw the card has many Intel settings after the driver upgrade, also something like "lock on a mac", so I could surely decide the wl1 mac, lock on 5ghz, "Cisco radio detection" and so on. I tried many with always the same bad results.
Are you using just the drivers are have you also installed the Intel supporting software? That was nothing but trouble at work and we had to whole-sale remove it from all our laptops.
ErMeglio wrote:
What you speaking about here? The bluetooth coexistence mode setting on the web ui? Or is this simply the common name of the "wl interference 2" command ?
I asked about the BT coexistence setting in the GUI, but it's another setting. On my E4200 on a reboot the 2.4GHz setting is disabled i.e. returns blank, but the 2.4/5Ghz setting is "Non-wireless LAN Interference mitigation is enabled.". Here's the exact output from the two commands:
Code:
root@monty:~# wl -i eth1 interference
root@monty:~# wl -i eth2 interference
Non-wireless LAN Interference mitigation is enabled.
root@monty:~#
Then after my additional startup script lines:
Code:
root@monty:~# wl -i eth1 interference
Wireless LAN Interference mitigation is enabled.
root@monty:~# wl -i eth2 interference
Non-wireless LAN Interference mitigation is enabled.
root@monty:~#
Oddly today the speed is fluctuating wildly between 300 and 450, no idea why. Hopefully the message from Fractal about the kernel and drivers will produce a stabilising fix soon.
I have emailed brainslayer asking him if there is a new toolchain he is using as I was able to test his std_usb_nas build and confirm that nslookup is working without segfault.. I can also confirm that wiviz is still broken, however if that is the only thing broken and the wireless is more stable I will take that any day... I will follow up when I know more
@Taomyn
Thanks for all your hints.
I've used the 5100 with no software at all and without updated drivers too, and the results were almost the same.
Now I've upgraded drivers and I thought to have denied the installation of the Intel's connection tool. For sure I asked it not to use Intel to connect to the wireless, but Windows. Instead it installed a pair of applications, the main one is PROset/Wireless that can't make connections but has three sub-apps that are for statistical data of the wireless, diagnostics, a tool to import "profiles" and a sort event registry of wireless statuses. They anyway never appear by themselves, are not even in the tray at the clock.
I see, instead, I could ask, into connection's properties, to use the Intel's subdriver(?) to set some additional settings about the WiFi connection. That's what I was talking about when I spoke about mac address, locked frequency to 2,4 or 5, "Cisco detection" ecc. I tried activating all of these, disactivating the entire subdriver, but no change at all.
The commands you propose with -i eth1 and -i eth2 are exactly the ones I tried without success.
Will check out soon the new BS' build, it would be great if we come to know what's knew, toolchain, uclibc ecc, will look forward for your hot news Fractal
Was reading in the NAT Loopback thread and saw something which made me curious as well; maybe Fractal or other folks in this thread would know?
Mangix wrote:
sorry for bringing this thread from the dead but does svn version 17911 fix nat loopback? many changes were made relating to the nvram variable block_loopback
Can someone do "wl ver" and se which wifi driver is using ? build 17967
Oh... sorry K2.6
These are the drivers on my version kong 17940 root @ DD-WRT: ~ # wl ver
5.60 RC127.4
wl0: Jul 18 05:47:50 2011 Version 5,100,127 _________________ Buffalo WZR-HP-AG300H DD-WRT v24-sp2 (03/19/12) std - build 18777 + modem Digicom combo cx + Nas Synology DS-209 da 2 T + LG DP1W+ APC Back-UPS RS-Power Saving Back-UPS Pro 550 + switch Zyxel Gs105B + http://forum.emulesecurity.net/topic.asp?TOPIC_ID=3441
I have emailed brainslayer asking him if there is a new toolchain he is using as I was able to test his std_usb_nas build and confirm that nslookup is working without segfault.. I can also confirm that wiviz is still broken, however if that is the only thing broken and the wireless is more stable I will take that any day... I will follow up when I know more
-Fractal
It's a bit annoying that it's been reported that SSH has suddenly broken in this release, is it all builds? Unfortunately the workaround isn't enough for me as the changing certificate I think will mess up some scripts I have on my server