Joined: 11 Feb 2016 Posts: 198 Location: South London
Posted: Tue Feb 13, 2018 20:20 Post subject:
aairon wrote:
Full_Speedz wrote:
Eyerex wrote:
Installed on my WRT1900 everything working ok just a shame about DLNA but stuck a Raspberry Pi in between router and drive to get DLNA back just runs a bit slower but ok for streaming
Yeah, the broken DNLA is the only thing stopping me from installing the latest beta. Hopefully it'll get fixed soon.
I'm confused there were improvements with this latest beta that have nothing to do with DLNA yes indeed.
But because it still doesn't have DLNA you are going to continue to run inferior firm/software anyway?
You do know that this is all volunteer stuff nobody here including Brain Slayer owe anybody anything!
By this I mean that just because some relatively obscure function isn't working there will be no rush to fix it because you won't download the current builds, really nobody cares.
I'm not saying this to put you down but it's the truth.
Think me and Full_Speedz replies and views were perfectly ok we didn't moan and i just said it's a shame it's not working _________________ | Netgear Nighthawk X4S R7800 | Linksys WRT1900ACS V1 | Huawei Echolife HG612 3B |
Installed on my WRT1900 everything working ok just a shame about DLNA but stuck a Raspberry Pi in between router and drive to get DLNA back just runs a bit slower but ok for streaming
Yeah, the broken DNLA is the only thing stopping me from installing the latest beta. Hopefully it'll get fixed soon.
I'm confused there were improvements with this latest beta that have nothing to do with DLNA yes indeed.
But because it still doesn't have DLNA you are going to continue to run inferior firm/software anyway?
You do know that this is all volunteer stuff nobody here including Brain Slayer owe anybody anything!
By this I mean that just because some relatively obscure function isn't working there will be no rush to fix it because you won't download the current builds, really nobody cares.
I'm not saying this to put you down but it's the truth.
You should probably mind your own business, I use DLNA on ddwrt that's why I wont update to the newest version until it gets fixed. I'm not telling anyone to fix it immediately
Aside from jnobody... everyone seems to be having positive results.
I think i will wait for one or two more builds to upgrade.
Over on the driver development front or lack of development front. The marvell dude has no idea why android devices are having issues (glad i use ios)... so i am not sure what he does while waiting for people to submit crash logs... i wish he would work on mu-mimo in the mean time. _________________ WRT3200ACM V1 r39267 std (03/22/19) OpenVPN client
Possibly found a bug in this firmware on a WRT1200AC v2. For anyone using a VPN to encrypt their internet connection, try disabling your VPN and see if your kill switch still works if you have it setup.
I only found this because I was doing some speed testing between different VPN endpoints, and after I had changed my endpoint and then refreshed speedtest.net before the tunnel reestablished, I momentarily saw my real WAN IP displayed.
I tested this again using some what is my ip type sites and they all displayed my real WAN IP rather than not loading at all when the tunnel was down.
I have rolled back to 34311 and the kill switch is working as expected now.
I did a little more troubleshooting with this, thinking that maybe something changed with the $(nvram get wan_iface) variable in the newer builds.
SSHing into the router and then running an echo $(nvram get wan_iface) on both 34311 and 34929 returns the expected eth0.
I also tried removing $(nvram get wan_iface) and replacing it with eth0 in the firewall commands and it made no difference.
So it would appear there is something wrong with iptables itself.
That's interesting. IPTables is a function of the Linux kernel, and I was under the impression that the kernel version had not changed from previous builds. Output of uname -a on my 1200ACV2:
Linux 4.9.81-rc1
Can anybody confirm if that's the same kernel version as the prior builds?
Did you buy chance mod your iptables rule and replace your $nvram variable with eth0 just for purposes of testing?
That's interesting. IPTables is a function of the Linux kernel, and I was under the impression that the kernel version had not changed from previous builds. Output of uname -a on my 1200ACV2:
Linux 4.9.81-rc1
Can anybody confirm if that's the same kernel version as the prior builds?
Did you buy chance mod your iptables rule and replace your $nvram variable with eth0 just for purposes of testing?
the $nvram variable is what I have always had it set to. I just did some experimenting with removing the variable and actually specifying eth0 to see if something might have changed with the variable in the new build.
It does look like the kernel has changed between 34311 and 34929. This is what 34311 which I am having no trouble with returns.
root@RouterAP:~# uname -a
Linux RouterAP 4.9.72 #91 SMP Thu Dec 28 04:11:35 CET 2017 armv7l DD-WRT
I've not poked around in the guts of dd-wrt too much...but I'd guess either something got left out of the new kernel config, the helper modules aren't config'd, or something in whatever the dd-wrt equivalent of sysctl.conf changed. I definitely think it warrants a bug report..not killing vpn'd traffic like that is a security issue.
Is there a problem with the server I can get to the page where the files are displayed, but then get
"This site can’t be reached
download1.dd-wrt.com refused to connect......"
works fine for me with WRT1900ACS V2. No more NTP red marks on the Syslog, works fine with USB and NAS connected, static IPs for CCTVs, and DHCP for wireless & LAN clients.
MyPage (custom script page) though isn't working since Jan 2018 build, the last time it worked was 12/29/2017 build.
Posted: Thu Feb 15, 2018 14:38 Post subject: Everything Working
Everything working for my WRT3200ACM, but I use a relatively simple setup. I did observe my android device dropping once in a while from 5GHz but it immediately reconnected.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Thu Feb 15, 2018 16:10 Post subject:
Adamcarter wrote:
Aside from jnobody... everyone seems to be having positive results.
I think i will wait for one or two more builds to upgrade.
Over on the driver development front or lack of development front. The marvell dude has no idea why android devices are having issues (glad i use ios)... so i am not sure what he does while waiting for people to submit crash logs... i wish he would work on mu-mimo in the mean time.
I doubt that he is just sitting around with his feet up on the desk waiting for logs. I will bet he is working the the driver and he knows some features need work or in the case of mu-mimo needs to be started. Part of the problem seems to be he is the only one. Never saw a development team taking on something like a driver to be one person. _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
Joined: 18 Aug 2009 Posts: 597 Location: Antigua/Seattle
Posted: Thu Feb 15, 2018 16:51 Post subject:
The Honorable David Lin AKA yuhhaurlin has at least one partner who speaks up now and then.
The driver will be needing work for awhile so I'm loading whatever works best and not 'waiting' for anything, why wait when it takes seconds to load?
It's funny I see a lot of posts by folks who are bothered that these builds have problems, and statements that imply that they will not partake in testing new software until it's sorted out. As if anyone on this planet beside them really cares about their particular issue.
yuhhaurlin or Brain Slayer won't drop everything just because you're not happy lol. _________________ WRT3200ACM