Don't pretend to be in Germany when you're in Finland!

I once had WiFi problems with an older version of OpenWRT and this helped:

wireless.radio0.path='platform/soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'

That's something I rarely do LOL, but I have tried everything.

So this is were my ignorance starts to show. How would I change the setting?

Haha...depending on where exactly you are in Finland I guess there is nobody around who cares about your TX power for that matter.

Well you did post contents from your config file here, so you'd just open that file with a text editor and start typing away. I personally use WinSCP or FileZilla depending on which machine I am on and log into the router, navigate to /etc/config/wireless (it's like any file manager), open it, change whatever I want in the text editor (currently I am where I pretend to be ) and then save it.

No promises though, adding platform to path was intended to be a workaround for strange behavior and missing values in LuCI and I thought it had been fixed anyway.

(Alternatively you can use PuTTY or command line and tools like vim, but the former is more intuitive if you're just starting.)

I really don't think the following is going to help, but it did give v1 users problems in the past, so it may be worth checking out.

in the wireless config on both option paths, put  "platform/"  in front of soc and reboot.

They should look like this.

option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'
option path 'platform/soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'

I got carried away with details. Doing a very basic test (unhooking the WAN connection and rebooting the WRT1900) showed that the AVM router used as modem is not responsible for my issue as 198.168.1.1 still couldn't be pinged via WiFi and not accessed through the browser interface. In Luci the configuration interface WiFi is set to Access Point connecting LAN with WAN. The LAN interface bridges the switch eth0 with the wireless network (lan,wan). I wouldn't mind having access to LAN and WAN via WiFi without LAN connected to WAN.
Thanks for any ideas.

(Last edited by jimmy-jazz on 4 Feb 2017, 10:10)

Ok so I did a reset to default settings, that was the only thing I didn't do and that sorted the problem. After the first reset I tried to change the channel of the 5 Ghz to a higher one (its now 36) and that made the radio to shut down. I could not wake it up what ever I changed so I did another reset and now everything works.

Thanks to everyone

Just one more question. I have been using Putty to see the files of my router. I don't have the capacity to work with Putty so the idea of modifying the files with WinSCP or similar would be nice. But if I try to connect to my router with WinSCP or Filezilla I get error "Received unexpected end-of-file from SFTP server". I can get connected with Putty.

So what am I doing wrong?

Make sure it is set to scp and not sftp.

...or install the SFTP server package in LuCI.

LAN should normally bridge eth1 and WiFi. That sounds as if your config is a bit messed up. You can either change that or do a clean re-install.

Thank you. I will finally try to setup up open vpn now when everything is working.

Thanks Floyd!
The default set up was bridging WiFi and eth0. Changing that to eth1 gave me access to LuCi and bridging in eth1 again gives access to the attached NAS.

Good luck with that...I have a working OpenVPN setup to PerfectPrivacy here, so feel free to ask if you need any help...!

I Need those who own the 3200ACM to test a new build - r3293. This could just be my configuration, but am unable to upgrade using sysupgrade -F. After the reboot, nothing has changed, and I want to be sure if others are having the same issue or not.

https://davidc502sis.dynamic-dns.net/sn … u/generic/

thanks,

Looks like I may have stumbled across a symptom of the issue.

root@lede:~# fw_setenv boot_part 2
Read error on /dev/mtd1: No error information
Error: can't write fw_env to flash

Ended up using the USB TTL cable to get me out of trouble. Flashed the same image that was on it r3063, and then from there flashed using sysupgrade -F to r3293 without issue.

Hi David and other members

I just downloaded and installed the latest version of Shelby ( lede-mvebu-linksys-wrt1900acs-squashfs-factory.img dated 2017-02-04 22:58 , size 14M ) on my late 2016 year WRT1900ACS - with the 1.6ghz processors - from your LEDE snapshots section (2017 build with LuCi). This one also comes with all the packages pre installed I believe.

I am trying to connect to the internet via a USB modem stick (ZTE 5008-Z). Can anyone please help me set this up??

Kind Regards
Marius

Is it OK to flash the new build to the wrt3200ACM?

Can anyone please try and help me understand the interface changes in the newer builds?

First of all, eth0 (now LAN) and eth1 (now WAN) got switched around but after some research this seems to have been consistently applied across the WRT1X00 series. The switch config of course had to be changed as well. So, just a name change.

What is new: CPU (eth1) port is now VLAN tagged by default while WAN port isn't. As a result, it seems that the WAN interface had to be configured to bridge the tagged and the non-tagged port. This is admittedly creative, but I wonder why this was done? Also, WAN6 seems to be part of the bridge but actually now shows no physical settings at all. Won't this break functionality of WAN6 - has anyone been able to test this? Thanks!

I did find these instructions, but don't know if they apply completely.

https://wiki.openwrt.org/doc/recipes/3gdongle

It's fine to flash, but I've seen no improvements over the last build... I.E. LED issue, Sysupgrade issue persist.  Wifi is just as bad, but that's expected since there have been no wifi changes since the last build.

Thanks,

OK mate thanks. When it comes to flash a new build will I be able to flash with out USB TTL?

Hi David,

Do you know if the latest version 3293 has been compiled with above option enabled? I have installed NGINX but still get the same error - "the "ssl" parameter requires ngx_http_ssl_module".

Thanks.

This is what I observed.. On the 1900acm, there were no problems. However going from r3063 to r3293, on the 3200ACM, I had to use the usb/ttl cable. As a test, I flashed r3063 using the usb/ttl (same build it was on), and then flashed with no issues to r3293. Unknown reason why I couldn't flash the first time, but after flashing again, it was fine. Seems to have been a one-off problem as no other users have reported issues.

@davic502,

Just to let you know, I just flashed r3293 on my WRT1900ACS v1 and noticed the WAN led is flashing now...
I hope this isn't temporary.