David, for the reason I do not know, my DDNS wget with your r3063 have problem on Wget+DDNS

I have DDNS with both eNom and Dynv6. the eNom DDNS receive error while the Dynv6 does not. The Wget return error 4, OpenSSL error

Previous r2695 does not have Wget pre-installed, and I can have both DDNS work with no Wget install, by install Curl and libustream-openssl. Installed Wget and then remove it will result in the same error above.

I further install the 17.01-SNAPSHOT r3024-6b68635 with Wget installed, then the problem solved.

My issue has been raised out here

forum.lede-project.org/t/wget-error-in-ddns-update/865

Do you think it is possible to fix this? Thanks

(Last edited by enri1357 on 26 Jan 2017, 02:29)

There are a couple of ssl packages I left out of the build on r3063 that were required for opkg to talk https. Those packages will be added back in the next build, and I wonder if that was the problem.

Has anyone here ever tried applying VLAN tagging with this build to the WAN interface with the help of the switch configuration in LuCI or the config files? I'll soon have to put up with an FTTH ISP, and the connection needs VLAN ID 100 for internet.

Here's my idea - it's a Shelby device so I think I have to tag ports 4 and 5:

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option ports '0 1 2 3 6'
    option vid '1'

config switch_vlan
    option device 'switch0'
    option vlan '2'
    option ports '4t 5t'
    option vid '100'

(Last edited by floydburgermcdahm on 26 Jan 2017, 22:41)

@davidc502
I just installed your latest, r3063, on my wrt1900acs. I got the ssl security issue.  I then edited the /etc/config/httpd file for the 443 ports. 
config uhttpd 'main'
    list listen_http '0.0.0.0:80'
    list listen_http '[::]:80'
    #list listen_https '0.0.0.0:443'
    #list listen_https '[::]:443'
    option redirect_https '1'
    option home '/www'
    option rfc1918_filter '1'
    option max_requests '3'
    option max_connections '100'
    option cert '/etc/uhttpd.crt'
    option key '/etc/uhttpd.key'
    option cgi_prefix '/cgi-bin'
    option script_timeout '60'
    option network_timeout '30'
    option http_keepalive '20'
    option tcp_keepalive '1'
    option ubus_prefix '/ubus'

Commenting out the two references to port 443 and a reboot allows me to login without a cert issue.

--bill

@davidc502
Been updating as usual, and want to thank you again for your builds.

Yesterday I updated to your latest, r3063. Kept settings, and everything started fine. Came back home today, and router had rebooted. I decided to see if l could replicate this, and see if the router was overheating. Rebooted router again, opened an ssh terminal and speedtest tab. I issued the sensors command, and ran the speedtest. The speeds were around 35mbps, which was lower than my regular 100mbps. The sensors showed temps of ~77 for the CPU, and the router then crashed.

Rolled back to r2695. I have no idea what the issue is, as 77 degrees seems pretty low compared to what the temperature triggers are for the fan. I wonder what the issue was for people that had issues with the test build.

If there's any tests or commands that you would want me to run to learn more, let me know.

--ThePatrikos

Is the shell script commented out in cron? 

root@lede:~# crontab -l
#*/5 * * * * /sbin/fan_ctrl.sh

No, it is not.
*/5 * * * * /sbin/fan_ctrl.sh

If you want, change the thresholds for the CPU. That's what I did when I owned a v1.

The below is the default
CPU_LOW=85
CPU_HIGH=95

This is what you could change it to.
CPU_LOW=80
CPU_HIGH=85

**EDIT**

Really, there's no reason for the router to crash.  They may have rolled already, but try to capture the system and kernel logs.

(Last edited by davidc502 on 27 Jan 2017, 01:44)

Thanks, will flash and change the settings. Will let you know what happens.

EDIT: I can set up a log server for the router to dump the logs right? (Never mind, found the option)

(Last edited by thepatrikos on 27 Jan 2017, 01:48)

You can also mount a USB sick, and log to it. Probably wouldn't be a bad idea to log all Firewall Drops to USB as well.

@davidc502
Thanks for your help!

The temps are stable now (~67), increasing a bit only when the router is handling lots of traffic. Log files show that all is normal, and the firewall only shows the regular amount of garbage from who knows where getting dropped.
If anything changes, I'll look through the logs saved on my server.

Thanks again!
--ThePatrikos

(Last edited by thepatrikos on 27 Jan 2017, 03:56)

What I did was to opkg install all the package listed in your site, but that don't help.

now I use Image Generator to generate all the package listed in your site to a standard 17 01 Snapshot, then it works

I think the actual culprit is the line "option redirect_https '1"
This instructs httpd to always use ssl, if available.
Probably this needs to change to "option redirect_https '0'" or simply commented out.

Commenting out the https lines has a similar effect, since no https port is availabe and a redirect is impossible.

@adr
Good catch.
--bill

@davidc502 @bill1228

I just tried changing the "option redirect_https '0'" and it works as expected.
The Luci webinterface just stays on http or https protocol, depending on what you used to connect.

Good deal. Thanks

Hi!
Total scripting disabled noob here asking for help: I just installed lede-mvebu-linksys-wrt1900acs-squashfs-factory.img on my WRT1900CS V2. I can connect all my devices to the internet via WiFi but the LuCi access is denied. Access via LAN is no problem. Does anyone have a tip what could be wrong?

Question to make sure I understand what you are asking.

1. If on Wifi you can not get to LuCi
2. If plugged into a Ethernet Port you can get to LuCi

Have you tried https?

Also,

What network is a wired PC on vs a device on Wifi.

(Last edited by davidc502 on 28 Jan 2017, 18:25)

wget returned 4.

Doing anything with server?

Hi David, thanks for getting back so fast.
1. If on WiFi I can not get to LuCi. A white screen appears with black lettering saying lua configuration interface in the top left. That's it.
2. If plugged into an Ethernet port I can get to LuCi and also see and can access the Buffalo NAS hooked up to another Lan port. On Wifi the NAS doesn't show up.

Sorry, I don't get the question.

Best,
   Daniel

My 1900v1 is suffering the same beahavior that ThePatrikos watched on his. It began rebooting and I couldn't even access them to show the temperatures before rebooting again. Back to previous release...

Regards and thanks David for this great work. Lede is working really fine for em (apart these glitches...).

Thanks for the info. Are you going back to r2695? Seems many V1 owners having success with that particular build.

Seems the device on wifi is getting something, but not all.  Have you done a wifi speed test to see what speeds the device is getting?

For the earlier question. Basically what's needed is the IP, Subnet Mask, and default gateway of a device on the LAN and the same information from a device on Wifi.

Thanks,

Please try again, and let me know if you're still having any issues getting to the server.

Thanks,

Sorry for being late, I was away from home. But yes, I'm on r2695 now. After the "rebooting session" I installed r2695 and has been Ok since then. My son has been home all day and that means a pretty heavy wrk for the router. No problem until now. If there's anything I could investigate, please tell me.

Regards.