OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

IvanRaide wrote:
doxidad wrote:

I have syslog working with the stock system (no extra logging sw)
....
Hope this helps abit.


Thanks; it does in that it tells me it can work and something on my side is not working.  I am writing to a NAS4Free server which is a variant of FreeBSD so not sure why it doesn't work.  Ironically my old DLink DIR615 router could write to a syslog server and it wrote to the NAS no problem, so not sure whats wrong with OpenWRT.  I have the settings the same as yours, (and every variant I could try).  I confirmed via `sockstat -4 -l` that the NAS has 514 open.  Did you have to make a firewall exception to let the router talked to the NAS for UDP 514 (I wont believe so) but I cant figure out why it doesn't work?  What build are you running?

I had to make an exception in the firewall (ipfw) on the FreeBSD  system to open the port to other IPs on the same net to get it to work. Forgot about that.

kirkgbr wrote:
doxidad wrote:

I have syslog working with the stock system (no extra logging sw)
Setting  System->Logging
External system log server 192.168.200.25
External log server port 514
Output log level debug
cron log level normal


I don't see those options in stock.

If you are talking about the stock linksys software - if it is an option I don't remember( been way too long since I used it). I was talking about openwrt CC - currently running a trunk release from about a week ago, but it has been available in all the CC releases I have tried.

bmork wrote:

Does this mean that tftp is disabled in the WRT1900AC uboot?  I haven't tried... Only assumed it would be there.

There's the TFTP client, but using that requires access to the serial console. What I meant was a TFTP server that you can trigger using a button or whatnot, similar to a lot of Broadcom-based routers. The goal would be to have a recovery mechanism that doesn't require hooking up the console.

hi@all,
can somebody explain this error?

/usr/lib/lua/luci/dispatcher.lua:433: Failed to execute cbi dispatcher target for entry '/admin/system/fstab/mount/cfg044d78'.
The called action terminated with an exception:
/usr/lib/lua/luci/util.lua:33: bad argument #3 to 'format' (no value)
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

i see this, when make luci mount-points edit

thanks :-)
p.

(Last edited by piphone on 16 Apr 2015, 16:25)

doxidad wrote:
kirkgbr wrote:
doxidad wrote:

I have syslog working with the stock system (no extra logging sw)
Setting  System->Logging
External system log server 192.168.200.25
External log server port 514
Output log level debug
cron log level normal


I don't see those options in stock.

If you are talking about the stock linksys software - if it is an option I don't remember( been way too long since I used it). I was talking about openwrt CC - currently running a trunk release from about a week ago, but it has been available in all the CC releases I have tried.

@doxidad

Sorry, I must have misinterpreted when you wrote "stock system".

leitec wrote:
jklap wrote:
leitec wrote:

Right now OpenWrt isn't doing anything with the actual "auto recovery" process, by which I mean it doesn't update the other variables that I think are necessary for that to work properly. I believe the factory firmware updates badcount, boot_part_ready and probably more variables that the "auto_recovery" process then uses to determine if it should boot from the other partition instead. As far as I know Linksys never released the WRT1900AC's u-boot source, so I can't tell what it actually is doing.

Anyone got a contact with LinkSys that can put some pressure on them to release the u-boot source? It would be nice if we could back-port some of the more recent changes to support flashing from a usb drive (for example).

Kaloz said a while back he was trying to get them to release the source.

If I'm not mistaking it with another device you can already boot from USB. I don't recall the exact steps but you can use the 'usb' command to start it and the various fat/ext2 commands to load whatever file you want to boot from.

Edit: I forgot to add before that the Linksys EA4500 does have published u-boot source, including both Linksys and Marvell's changes. Linksys also uses the dual firmware thing there so you might get some mileage out of reading that source code.

That said, last time I talked to Kaloz about this (months ago) he wasn't too keen on spending time trying to work in a system that isn't all that great at preventing bricking. Getting actual source for u-boot would mean we'd have the ability to chainload a custom u-boot, where you could add real recovery and do away with the dual firmware thing altogether. Such is done on some other targets (kirkwood, for example).

Other boards with u-boot have real recovery mechanisms, like a TFTP or web server you can connect to and upload a working image, rather than banking on the possibility that the second image is working.

I'd have to review my notes on what I was trying to do but was hampered as the WRT's u-boot version was quite a bit behind. Vague recollection I was attempting two things-- boot from an image on usb and flashing a new image from usb automatically if detected-- which would give us an additional safety against bricking. I gave up.

But I'm also curious about what they've added for the fail over stuff.

piphone wrote:

hi@all,
can somebody explain this error?

/usr/lib/lua/luci/dispatcher.lua:433: Failed to execute cbi dispatcher target for entry '/admin/system/fstab/mount/cfg044d78'.
The called action terminated with an exception:
/usr/lib/lua/luci/util.lua:33: bad argument #3 to 'format' (no value)
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

i see this, when make luci mount-points edit

thanks :-)
p.

I get the same error with both add/edit..

@kaloz
https://forum.openwrt.org/viewtopic.php … 70#p272770
FYI http://www.gypsy-designs.com/991.jpg

Thu Apr 16 12:37:39 2015 daemon.info hostapd: wlan0: STA 20:aa:4b:3e:5e:39 WPA: group key handshake completed (RSN)
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]: /usr/lib/lua/luci/dispatcher.lua:433: Failed to execute cbi dispatcher target for entry '/admin/system/fstab/mount/cfg044d78'.
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]: The called action terminated with an exception:
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]: /usr/lib/lua/luci/util.lua:33: bad argument #3 to 'format' (no value)
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]: stack traceback:
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]:     [C]: in function 'assert'
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]:     /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch'
Thu Apr 16 12:39:20 2015 daemon.err uhttpd[1337]:     /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

(Last edited by gufus on 16 Apr 2015, 23:30)

piphone wrote:

hi@all,
can somebody explain this error?

/usr/lib/lua/luci/dispatcher.lua:433: Failed to execute cbi dispatcher target for entry '/admin/system/fstab/mount/cfg044d78'.
The called action terminated with an exception:
/usr/lib/lua/luci/util.lua:33: bad argument #3 to 'format' (no value)
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

i see this, when make luci mount-points edit

thanks :-)
p.

same with openvpn !! and still does not start after reboot IGMP proxy 4.0.0-rc7 r45459.do not tell me where it is possible to express thanks to the developers of firmware? thank you

(Last edited by Armik on 16 Apr 2015, 22:02)

I finally switched back to 3.18.11 since 4.0 presented some regression (stability, speeds, lockups, etc). It seems 3.18 has matured quite a bit and overall the router seems to be in a more usable state than where it was just a month ago. @Kaloz @mmilburn and everyone else who have helped this router get to this point, Thank You!

How do I display memory cache in luci?

Armik wrote:
piphone wrote:

hi@all,
can somebody explain this error?

/usr/lib/lua/luci/dispatcher.lua:433: Failed to execute cbi dispatcher target for entry '/admin/system/fstab/mount/cfg044d78'.
The called action terminated with an exception:
/usr/lib/lua/luci/util.lua:33: bad argument #3 to 'format' (no value)
stack traceback:
    [C]: in function 'assert'
    /usr/lib/lua/luci/dispatcher.lua:433: in function 'dispatch'
    /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

i see this, when make luci mount-points edit

thanks :-)
p.

same with openvpn !! and still does not start after reboot IGMP proxy 4.0.0-rc7 r45459.do not tell me where it is possible to express thanks to the developers of firmware? thank you

I think it's a bug in luci.

Just downloaded the latest factory from trunk today and I have no wireless.

OpenWrt Chaos Calmer r45453/ LuCI (git-15.102.66001-622cfc6)

The Wireless Overview pages says "0% Wireless is disabled or not associated." Mode is "unknown." Though I did enable the buttons next to the 2 and 5GHz radios, each now shows disabled.

Any ideas?

@srd, I had this for 5GHz radio and the remedy was to decrease the width from 160 MHz to 80 Mhz.

@lbwjgycd

I have 80 there already, I've changed channels, modes, bw's, etc... to no avail.

my external hdd is ntfs and as somebody pointed out the driver is probably the limiting factor with the write speed.

i hope this isn't a stupid question. if i reformat as ext4 will my windows 7 be able to read/write without a driver ? (i thought the router maybe was taking care of these things)

@jow

thanks :-)
p.

Unfortunately you need a driver for windows 7 to use ext4 (if plugged into your windows box).  http://en.wikipedia.org/wiki/Ext2Fsd
Though you obviously dont need a seperate  windows driver to read the ext4 drive over the network while it is plugged into the router....

its pretty much the reverse situation in that NTFS is native to windows and requires a third party driver for Linux systems.
Whereas EXT4 is a native system for Linux and requires a driver for windows.


I haven't tested the windows driver, though hopefully it works with acceptable performance.
Let me know if you try it smile

BTW, i found it much quicker to use fdisk and mkfs.ext4 to re-partition and re-format the drive while plugged into the router, than attempting to create the ext4 filesystem while plugged into the windows box.


ethereal wrote:

my external hdd is ntfs and as somebody pointed out the driver is probably the limiting factor with the write speed.

i hope this isn't a stupid question. if i reformat as ext4 will my windows 7 be able to read/write without a driver ? (i thought the router maybe was taking care of these things)

(Last edited by drewgarth2 on 17 Apr 2015, 12:31)

hi @all,
1. thanks an all for your work
2. sorry for my bad english, i am a stupid german from berlin :-)

a hint for all, who will see somthing led-playing,
here my config
config led
        option default '0'
        option name 'wan-transmit'
        option sysfs 'mamba:white:wan'
        option trigger 'netdev'
        option dev 'eth1'
        option mode 'tx'

config led
        option default '0'
        option name 'wan-receive'
        option sysfs 'mamba:amber:wan'
        option trigger 'netdev'
        option dev 'eth1'
        option mode 'rx'

config led
        option default '0'
        option name 'lan-transmit'
        option sysfs 'mamba:white:wps'
        option trigger 'netdev'
        option dev 'br-lan'
        option mode 'tx'

config led
        option default '0'
        option name 'lan-receive'
        option sysfs 'mamba:amber:wps'
        option trigger 'netdev'
        option dev 'br-lan'
        option mode 'rx'

config led
        option default '0'
        option name 'usb31'
        option sysfs 'mamba:white:usb3_1'
        option trigger 'usbdev'
        option dev '3-2'

config led
        option default '0'
        option name 'usb32'
        option sysfs 'mamba:white:usb3_2'
        option trigger 'usbdev'
        option dev '3-2'

# and here i let me show activity on wlan0 2,4, i have no usb2-device
config led
        option default '0'
        option name 'wlan0-transmit'
        option sysfs 'mamba:white:usb2'
        option trigger 'netdev'
        option dev 'wlan0'
        option mode 'tx'

for all who are interest: since more than 2 weeks i am running squid on my wrt1900ac, all whirout problems
some times i make 3 to 5 installations debian, opensuse ubuntu at the same time and all work's fine :-)
if you like, i can post my squid.conf from /etc/squid ...

bye
p.

@piphone thanks for the LED config.

I would like to see the squid config. Are you also running a content filter with the proxy?

@chadster766
why you not work on your image??
:-)
here my squid.comf
acl localnet src 192.168.1.0/24
acl ssl_ports port 443
acl safe_ports port 80
acl safe_ports port 21
acl safe_ports port 443
acl safe_ports port 70
acl safe_ports port 210
acl safe_ports port 1025-65535
acl safe_ports port 280
acl safe_ports port 488
acl safe_ports port 591
acl safe_ports port 777
acl connect method connect

http_access deny !safe_ports
http_access deny connect !ssl_ports
http_access allow localhost manager
http_access deny manager
http_access deny to_localhost
http_access allow localnet
http_access allow localhost
http_access deny all

access_log /mnt/usb3/squid/access.log
cache_log /mnt/usb3/squid/cache.log
cache_store_log /mnt/usb3/squid/store.log
netdb_filename none
logfile_rotate 9
logfile_daemon /dev/null

maximum_object_size 5000 MB

http_port 3128 intercept
cache_dir ufs /mnt/usb3/squid/cache 100000 16 256
cache_mem 128 MB

# caching of system updates/large binaries
acl binaries url_regex [-i] ^[.]*\.(iso|tar|gz|tgz|bz2|rpm|deb|udeb|cab|exe|ms[iufp]|dat|zip|rar])$
# ONLY cache binaries
cache allow binaries
# cache deny All

#
# Add any of your own refresh_pattern entries above these.
#
refresh_pattern ^ftp:           1440    20%     10080
refresh_pattern ^gopher:        1440    0%      1440
refresh_pattern -i (/cgi-bin/|\?) 0     0%      0
refresh_pattern .               0       20%     4320


some timees i have problems with files larger than 2 GB (like a knoppic-dvd), then the load is going over 25 and
the router is not responding for a short time, if i stop the download all works fine :-)
normaly my config-directive max_object_size is 2 gb

have fun
p.

piphone wrote:

@chadster766
why you not work on your image??
:-)

IMO OpenWRT and the Linux Kernel has changed too much to bring an AA Image and it's related packages up to date. It requires way to much time that I'm is short supply of :-)

@ chadster

  "IMO OpenWRT and the Linux Kernel has changed too much to bring an AA Image and it's related packages up to date. It requires
   way to much time that I'm is short supply of :-)"

i anderstand; it was only a funny remark :-)
p.

(Last edited by piphone on 17 Apr 2015, 18:22)

Sorry, posts 4526 to 4525 are missing from our archive.