Well the marvel driver still needs some work until I consider it usable. There are several things that don't work right now and some are buggy e.g.: 5G <-> USB sucks.
But you can see the driver improves I have been running the unit in client mode (2G) for the last 2 days, with one pc attached to ethernet and one to 5G. Throughput is not too bad.
And since the driver builds out of tree, updating the driver just takes a few minutes.
I'm not quite understand how 5G <-> and USB/SAMBA issue related but I do know the USB share (FTP, NFS or SAMBA) over wifi performance is really bad.
802.11 is at OSI layer 1 and 2. SAMBA is probably at layer 5/6/7 at least. So, maybe Kong can share more knowledge to us. Maybe it's at the hardware driver level? But isn't those are handled by OS?
Great to see a nice web interface on the WRT1900AC! Seems very functional as well.
Some things:
1. 5GHz. wireless only works (for me) with 20MHz. channel width, the other channel widths don't work. By "don't work", I mean no 5GHz. radio signal.
2. Does the 20dBm tx power provide the hardware default tx power? Should tx power be set to "0" for that? Or can it be higher than 20dBm? Just curious if there's any control there? The reason that I ask is that the signal seems to be not quite as strong on 5GHz. as the stock firmware. 2.4GHz. signal is fine, though.
3. Does the "reset" button work? I didn't try it yet, haven't needed it, but I'm curious.
Other than these questions, I'm really happy to see DD-WRT on the WRT1900AC. Great start, looks like there's some work to go, but I'm so happy to see this.
And the nandboot and altnandboot boot partitions worked really well, stock firmware is in nandboot partition, and DD-WRT is in altnandboot partion. I like that, very helpful.
Great to see a nice web interface on the WRT1900AC! Seems very functional as well.
Some things:
1. 5GHz. wireless only works (for me) with 20MHz. channel width, the other channel widths don't work. By "don't work", I mean no 5GHz. radio signal.
Not all combinations work, try:
AC/N-Mixed
HT40
157
Upper
That's what I currently use.
Quote:
2. Does the 20dBm tx power provide the hardware default tx power? Should tx power be set to "0" for that? Or can it be higher than 20dBm? Just curious if there's any control there? The reason that I ask is that the signal seems to be not quite as strong on 5GHz. as the stock firmware. 2.4GHz. signal is fine, though.
Yes you can raise it, the 20dBm is just dd-wrts default.
The driver has an internal power table and will limit it even if you set it too high for a certain channel/region combo etc.
Quote:
3. Does the "reset" button work? I didn't try it yet, haven't needed it, but I'm curious.
Great to see a nice web interface on the WRT1900AC! Seems very functional as well.
Some things:
1. 5GHz. wireless only works (for me) with 20MHz. channel width, the other channel widths don't work. By "don't work", I mean no 5GHz. radio signal.
Not all combinations work, try:
AC/N-Mixed
HT40
157
Upper
That's what I currently use.
Quote:
2. Does the 20dBm tx power provide the hardware default tx power? Should tx power be set to "0" for that? Or can it be higher than 20dBm? Just curious if there's any control there? The reason that I ask is that the signal seems to be not quite as strong on 5GHz. as the stock firmware. 2.4GHz. signal is fine, though.
Yes you can raise it, the 20dBm is just dd-wrts default.
The driver has an internal power table and will limit it even if you set it too high for a certain channel/region combo etc.
Quote:
3. Does the "reset" button work? I didn't try it yet, haven't needed it, but I'm curious.
Yes works.
Thanks for this. I do usually just leave the default "Mixed" set as the mode, I'll try what you suggest and see if I can get a little more bandwidth *smile*.
For the tx power question, what I was trying to get at is the question of whether there's a tx power setting that sets the hardware default tx power? Like the way the DD-WRT default tx power value sets "Auto" for the R7000? That would be ideal, if that exists. I like to fiddle with the tx power, just have the value set that is the hardware default maximum for my locale, etc.
Thanks a BUNCH for your info and advices, Kong !
Gross gemacht - MUCH appreciated !
I doubt we, users, could ever really estimate what you're
through to make users' dream come true
I'm strongly considering making donations to DD-WRT,
cause I do not see any other (remotely) possible way of "thanking"
you and the staff for the enormous efforts,
work and dedication put in this project. Everlasting RESPECT.
I know I have or would deviate a bit of this subject's
primary focus, but as the last topic is concerned :
1. Wireless bridging DOES work in openwrt, the problem
is it's so damn tricky to accomplish
2. I've succeeded to make WRT1900AC a "wi-fi bridge" with
both Kaloz's and the main-truck (CC) images (?!)
3. My observations are really "mixed-bag", though. Why ?
Because with one of the builds (Kaloz), you can
wirelessly bridge this router to a DD-WRT-one
(EA6700 in mycase), without even needing relaying,
static routes, or interface bridging. HOW this works
is beyond me, really. Generally, following rules had
to be kept in my case :
a) LAN-interface of WRT1900AC must always be a
static address OUTSIDE of the main router/AP's range
b) DHCP on that LAN must always be DISABLED
c) with Kaloz's image, I had to un-bridge the 5 GHz
from the LAN, otherwise it wouldn't work (5 GHz band
used for bridging in general). This build has been the
onliest one allowing me to bridge WRT1900AC to my main
router, using a channel grater than 48 (128 tested and
working, but VERY flacky and disconnecting at random).
d) any other openwrt-build would NOT connect to main
router, if the latter has a channel set higher than 48.
What's the point of AC (1,3 Gbit) then ?!
e) any tested build would show transmit/receive rates
in client WRT-1900AC as "Bitrate: 6 Mbit/s" (?!)
f)any other build (except Kaloz's) - "CC" (trunk),
requires setting up a relay (relayd-daemon), in order
for the traffic to be routed betwen the bridged
WLAN-iface (5 GHz) and the LAN. Why 5 GHz and LAN
do NOT work when bridged - is again beyond me.
Why would normal bridging between
this router's WLAN (connecting you to your main router)
and its LAN not work,
and second - why for All Gods' sake there
is no option to go beyond channel 48 when bridging ?!
Marvell-driver, again ? The driver devs actually
announced the driver does support 1,3 Gbit
Well, folks, just to shed some light as to what
other guys have implemented and what horizons development
for this router has currently reached.
Everything is, and will always be much APPRECIATED !
Please, do point out any errors you might notice in my
tech-setup, because I'm far from Networking-Guru yet !
Thanks all in advance !
[quote="Unixworld"]Thanks a BUNCH for your info and advices, Kong !
Gross gemacht - MUCH appreciated !
Thanks all in advance !
Cheers[/quote]
Your post is most appreciated by me because I wish to purchase a second wrt1900ac and replace the r6250 currently in DD-WRT-client-bridge mode.
The current wrt-1900AC is also in Linksys's "Bridge mode",
and is hardwired to the gateway.
But this new router will probably use Linksys's
"wireless Bridge mode."
So Just to clarify,
In other words, both identical routers (according to the instructions at Linksys) will be using the LAN to connect to each other. The current one's setup will stay in the same situation,
but the new one will (according to Linksys) will use
"wireless bridge mode".
The details I am sure you already know, but it will be a first for me, until the DDWRT firmware is out.
The primary reason for me wanting DDWRT at all in this particular situation is the signal strength meter, which is an enormous help setting up the two routers.
At this time I know I could use either 149 or channel 36.
It took me a half hour to type this just figuring it out in my head,
but yeah, gateway-to-bridge-to-wireless.bridge
If I can't edit this, please ignore the typos.
If I'm way wrong I hope someone points it out.
Thanks in advance.
The issue I've described was my fault, actually
I've managed to bridge via Wi-Fi the WRT-1900AC,
I suppose some more time and patience have been needed.
So you should be fine, especially with two identical routers, I think.
But, have in mind - if you'd like to use the highest
possible 5 GHz-frequency, I'm afraid that's only possible
with DD-WRT now (at least on my side, but then this channel is set
on a different router - my main is EA6700).
I'm fairly familiar with OpenWRT, and as far as I've learned so far,
the channels choice if very limited in the web-interface
(should be possible to set via command line, though). _________________ R7500 Nighthawk X4 (main router)
Current build : 1.0.0.82/23.12.14
WRT1900AC (WiFi-bridge)
Current build : Chaos Calmer r45250 (testing OpenWRT)
Posted: Tue Mar 31, 2015 12:19 Post subject: Marvell submitted more fixes
<Kong> wrote:
Well the marvel driver still needs some work until I consider it usable. There are several things that don't work right now and some are buggy e.g.: 5G <-> USB sucks.
Posted: Wed Apr 01, 2015 15:14 Post subject: Re: Marvell submitted more fixes
Gazooo wrote:
<Kong> wrote:
Well the marvel driver still needs some work until I consider it usable. There are several things that don't work right now and some are buggy e.g.: 5G <-> USB sucks.
I know I added a workaround a few days ago before they came up with the changes, I merged their fixes now and it is working really good so far, AP/Client/Client Bridge Routed including VAP works fine.
Posted: Wed Apr 01, 2015 18:01 Post subject: Re: Marvell submitted more fixes
<Kong> wrote:
Gazooo wrote:
<Kong> wrote:
Well the marvel driver still needs some work until I consider it usable. There are several things that don't work right now and some are buggy e.g.: 5G <-> USB sucks.
I know I added a workaround a few days ago before they came up with the changes, I merged their fixes now and it is working really good so far, AP/Client/Client Bridge Routed including VAP works fine.
I am fairly new to dd-wrt, but I have used it on a couple of my routers. I just want to say Thanks to @<Kong> for his work on the WRT1900ac, I look forward to see what comes of it. And to be able to use it. Thanks again.
Posted: Wed Apr 01, 2015 18:50 Post subject: Re: Marvell submitted more fixes
<Kong> wrote:
I know I added a workaround a few days ago before they came up with the changes, I merged their fixes now and it is working really good so far, AP/Client/Client Bridge Routed including VAP works fine.
This is GREAT news, Kong !
I am so glad you make this giant progress,
and am so eager for the day to come, when your builds
will be out !
THANK you ! _________________ R7500 Nighthawk X4 (main router)
Current build : 1.0.0.82/23.12.14
WRT1900AC (WiFi-bridge)
Current build : Chaos Calmer r45250 (testing OpenWRT)
Posted: Wed Apr 01, 2015 21:51 Post subject: Re: Marvell submitted more fixes
<Kong> wrote:
I know I added a workaround a few days ago before they came up with the changes, I merged their fixes now and it is working really good so far, AP/Client/Client Bridge Routed including VAP works fine.
Kong, I'm curious what sort of wireless speeds you see in the status section of the web admin interface with the 24500M build from yesterday?
