Posted: Wed Oct 07, 2015 2:44 Post subject: Another chance...
Hi guys,
Like I did with the EA6900 while ago I did the same with this model, then...
Any news kong about VLAN support ?
Because I did something really "funny", I tried to access http://iprouter:port/Vlan.asp and it loads the VLAN, but any changes in there doesn't affect at all...
I have been trying vconfig add vlanXXX and ifconfig vlanZZZ up and for sure nothing works netiher.
Now I took my image.bin from the EA6900 and pasted in the WRT1900AC and I'm able to see the VLANS, but doesn't work at all.
I hope that we can have a workaround for this fact of the VLANS.
Many thanks and keep in touch.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Wed Oct 07, 2015 3:08 Post subject:
@tbgeo: Thanks a lot for your time and effort. From the numbers, it looks like there is not much of a difference--a slight edge to Kong's build on Blowfish. I use the aes-128-cbc these days on PIA.
Posted: Wed Oct 07, 2015 9:01 Post subject: Re: WRT1900AC
<Kong> wrote:
Giraffe wrote:
The problem is the 802.11N performance of the WRT1900AC, it isn't very good. The laptop i'm currently using has a Intel Ultimate-N 6300 WIFI-adapter. Under Linux peak throughput is about 70Mbps (85mbps running Win10) versus 120mbps with my old Netgear R7000 (running DD-WRT).
That's a driver problem marvel tried to add packet aggregation to the latest driver, but it broke more then it fixed, so we rolled back the driver, this is supposed to be fixed in the next release along wth the driver crash.
Along with the driver crash...? Did you maybe mean that they will have fixed the driver crashes in the next release?
If so, then that is the release to wait for . Any ETA?
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Wed Oct 07, 2015 20:36 Post subject:
I thinks it is OK. The reason I say that is when I had to use mine, I only used ground, rx and tx. So, at least for this router, it should be fine if you are talking about a serial recovery.
Posted: Wed Oct 07, 2015 21:21 Post subject: Re: WRT1200AC latest kong build
Flexcaliber wrote:
I just flashed latest Kong build: ddwrt-mvebu-armada-385-caiman-squashfs-factory on my WRT1200AC which was one stock firmware.
My router boots fine but when I try to acces the mgmt page at 192.168.1.1 it keeps popping up username and password.
I have changed it the first time I logged in, but the browser doesn't accept it...
I can't acces the mgmt page atm...
Is 192.168.1.1 the default access IP for DD-WRT firmwares? Is there a default username and password as well?
(Sorry if this is documented somewhere, but I have not been able to find anything)
Joined: 05 Mar 2014 Posts: 193 Location: Edmonton, AB
Posted: Wed Oct 07, 2015 21:38 Post subject:
Normally, 192.168.1.1 is the default. Also, after a fresh install it prompts you to put a name and password on that page. Now, it could be a little different if you are just upgrading without deleting the settings.
This is topical, I swear (don't beat me)
Kong's TX queue length is set to 1000, which I never would have noticed if not for a speed test that also measures "bufferbloat".
People recommend lowering this amount drastically to reduce bufferbloat, but it had almost no effect.
What DID have an effect was FQ_Codel QOS.
However, the download-speed should be left blank, and (to please the test and get an "A") the upload speed should be slightly less than what it really is (Which makes no sense since it believes you and lowers the upload speed).
I would have fooled more with download/incoming QOS but leaving it blank doesn't affect bufferbloat.
the upload speed should be slightly less than what it really is (Which makes no sense since it believes you and lowers the upload speed).
The reason you deflate the value is simple.
For QoS to be effective it has to kick in BEFORE you saturate the link. Any link at any rate.
Once you hit its max throughput its too late to implement QoS.
So you typically shed anywhere from 5-15% off the max throughput.
Also keep in mind that you want to shed that from the real world values not the subscribed rate.
That is why you run various speed/performance tests before hand; so you know what your real world throughput is as the base. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
A bit off topic but should be of interest to the users of these boxes.
A new version is coming out.
Here is a summary of the big changes.
The major differences distinguishing the WRT1900ACS and its predecessor are the new processor, the added RAM, and the removal of the internal fan. Linksys replaced the 1.2 GHz dual core ARM-based processor with an updated 1.6 GHz version, and the new WRT1900ACS now contains 512 MB of DDR3 RAM.
The router should be available for pre-order now I read. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
. Any ETA?