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.

Hi,

Apologies  for being yet another n00b asking the questions :-p

I just bought the WRT1200AC, I would like to use Openwrt for the following (If its supported)

Act as a fileserver with USB HDD
Act as a VPN
Allow the use of dyn dns
use QOS and bandwitdth control on my network
Do some basic to advanced network monitoring.

My knowledge thus far is that USB drives are not working, what else isn't working. In addition does Open WRT allow for any thing in git hub to be used?

My backround is a bit of Ubuntu server (pulling from a repository wise) haven't done FTP or windows fileshares before, but want too in Open WRT if possible?

Thanks

Also, what firmware image should I be using that still has a gui and these features? if any and a link if possible

Thanks again

(Last edited by samfree91 on 21 Apr 2016, 12:11)

samfree91 wrote:

... WRT1200AC ...

Why is this posted in the WRT1900AC thread?

cmsigler advises you to begin here.

Hi Guys, any of you guys having problems with WRT 1900ACS router PPPoE drops?

Setup: ADSL->DRAYTEK VIGOR 120 (PPPOE pass-through) --> WAN of Linksys WRT1900ACS

On latest stable release? I have noticed is happening ~every hour:

Thu Apr 21 15:21:43 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Apr 21 15:21:43 2016 daemon.notice netifd: Network device 'eth0' link is down
Thu Apr 21 15:21:43 2016 daemon.notice netifd: wan (24882): Command failed: Permission denied
Thu Apr 21 15:21:45 2016 kern.info kernel: [14461.809442] mvneta f1034000.ethernet eth0: link up
Thu Apr 21 15:21:45 2016 kern.info kernel: [14461.814323] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Thu Apr 21 15:21:45 2016 daemon.notice netifd: Network device 'eth0' link is up
Thu Apr 21 15:21:45 2016 daemon.notice netifd: VLAN 'eth0.5' link is up
Thu Apr 21 15:21:45 2016 daemon.notice netifd: Interface 'wan' has link connectivity 
Thu Apr 21 15:21:45 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Apr 21 15:21:45 2016 kern.info kernel: [14461.820977] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.5: link becomes ready
Thu Apr 21 15:21:45 2016 daemon.info pppd[24911]: Plugin rp-pppoe.so loaded.
Thu Apr 21 15:21:45 2016 daemon.info pppd[24911]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Thu Apr 21 15:21:45 2016 daemon.notice pppd[24911]: pppd 2.4.7 started by root, uid 0
Thu Apr 21 15:22:01 2016 daemon.warn pppd[24911]: Timeout waiting for PADO packets
Thu Apr 21 15:22:01 2016 daemon.err pppd[24911]: Unable to complete PPPoE Discovery
Thu Apr 21 15:22:01 2016 daemon.info pppd[24911]: Exit.
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Interface 'wan' is now down
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Interface 'wan' is disabled
Thu Apr 21 15:22:01 2016 kern.info kernel: [14477.067030] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Thu Apr 21 15:22:01 2016 kern.info kernel: [14477.074313] IPv6: ADDRCONF(NETDEV_UP): eth0.5: link is not ready
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Interface 'wan' is enabled
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Interface 'wan' is setting up now
Thu Apr 21 15:22:01 2016 daemon.notice netifd: VLAN 'eth0.5' link is down
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Interface 'wan' has link connectivity loss
Thu Apr 21 15:22:01 2016 daemon.notice netifd: Network device 'eth0' link is down
Thu Apr 21 15:22:01 2016 daemon.notice netifd: wan (24934): Command failed: Permission denied
Max Hopper wrote:
samfree91 wrote:

... WRT1200AC ...

Why is this posted in the WRT1900AC thread?

cmsigler advises you to begin here.

It is perfectly valid here! the WRT1200AC is practically the same as the WRT1900AC, the biggest difference is the fact that it doesn't support 1900AC but 1200AC, though the rest is the same.

A Wrt1900acs with an image built from official git HEAD.

root@OpenWrt:~# hwclock -D
hwclock from util-linux 2.28
Using the /dev interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
select() to /dev/rtc0 to wait for clock tick timed out...synchronization failed
root@OpenWrt:~# dmesg | grep rtc
[    1.191097] hctosys: unable to open rtc device (rtc0)
[   13.282058] armada38x-rtc f10a3800.rtc: rtc core: registered f10a3800.rtc as rtc0
root@OpenWrt:~# cat /proc/interrupts | grep rtc
 39:          0          0       GIC  53 Level     f10a3800.rtc

Zero interrupts? Has anyone got the clock working?

Max Hopper wrote:
samfree91 wrote:

... WRT1200AC ...

Why is this posted in the WRT1900AC thread?

cmsigler advises you to begin here.

because the 1200 and the 1900 are so closely related.

@mrfrezee

Hello

I try to install the cups, but not available.
and on p910nd not work. ls0 not found.
Tie it going? you could put cups? or how do I put myself?

Have you tried a build that has packet buffering patch (mvneta-hwbm - Linux-next) for the outside interface?

I wouldn't like apply something that wasn't tested properly and not confirmed by community or official OpenWRT docs/online notes. Spend good few weeks on OpenWRT hardening and tweaking. Still got few little issues with my Linksys WRT 1900ACs and major one is PPPoE drops..

ADSL Line -> Vigor 120 modem (PPPoE pass-through) with ethernet port to -> Linksys WAN (configured as PPPoE)..

I have seen guys suggesting to change WAN mode from 1G to 100MB, but I cannot find info how I can do that (I don't mind as my DSL link doesn't reach 100MB anyway)..

No issues with wireless N and AC modes or LAN ports under heavy loads- all works as expected, only WAN frequently drops (as per previously posted "logread" output).

I am willing post my complete setup (which includes VLANs, IGMP_SNOOPING, Complete OS and services hardening, Wireless tuning, OpenVPN and etc.) once all problems resolved

Gents!!
Can anyone explain these kernel logs? I am using David's latest image.
Many THANKS!!

[   17.299380] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 
[   17.306509] ieee80211 phy1: Channel: 128: 0x0 0x0 0xf
[   17.311601] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 
[   17.318729] ieee80211 phy1: Channel: 132: 0x0 0x0 0xf
[   17.323857] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 
[   17.330934] ieee80211 phy1: Channel: 136: 0x0 0x0 0xf
[   17.336063] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 
[   17.343195] ieee80211 phy1: Channel: 140: 0x0 0x0 0xf
[   17.348287] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 
[   17.355416] ieee80211 phy1: Channel: 149: 0x0 0x0 0xf
[   17.360508] ieee80211 phy1: 16 16 16 16 14 14 14 14 15 15 15 15 14 14 14 14 
[   17.367640] ieee80211 phy1: Channel: 153: 0x0 0x0 0xf
[   17.372775] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14 
[   17.379863] ieee80211 phy1: Channel: 157: 0x0 0x0 0xf
[   17.384995] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14 
[   17.392138] ieee80211 phy1: Channel: 161: 0x0 0x0 0xf
[   17.397230] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14 
[   17.404373] ieee80211 phy1: Channel: 165: 0x0 0x0 0xf
[   17.409456] ieee80211 phy1: 16 16 16 16 16 16 16 16 15 15 15 15 14 14 14 14 
[   17.416602] ieee80211 phy0: regdomain: FCC
[   17.420732] ieee80211 phy0: Channel: 1: 0x0 0x0 0xf
[   17.425693] ieee80211 phy0: 17 11 11 11 10 10 10 10 f f f f 0 0 0 0 
[   17.432128] ieee80211 phy0: Channel: 2: 0x0 0x0 0xf
[   17.437046] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.443827] ieee80211 phy0: Channel: 3: 0x0 0x0 0xf
[   17.448745] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.455525] ieee80211 phy0: Channel: 4: 0x0 0x0 0xf
[   17.460443] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.467223] ieee80211 phy0: Channel: 5: 0x0 0x0 0xf
[   17.472183] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.478923] ieee80211 phy0: Channel: 6: 0x0 0x0 0xf
[   17.483884] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.490624] ieee80211 phy0: Channel: 7: 0x0 0x0 0xf
[   17.495581] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.502363] ieee80211 phy0: Channel: 8: 0x0 0x0 0xf
[   17.507281] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.514061] ieee80211 phy0: Channel: 9: 0x0 0x0 0xf
[   17.518978] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.525759] ieee80211 phy0: Channel: 10: 0x0 0x0 0xf
[   17.530763] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0 
[   17.537554] ieee80211 phy0: Channel: 11: 0x0 0x0 0xf
[   17.542600] ieee80211 phy0: 17 11 11 11 11 11 11 11 10 10 10 10 0 0 0 0 
[   17.550882] br-lan: port 1(eth0) entered disabled state
[   17.951173] ieee80211 phy0: change: 0xffffffff
[   18.032204] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   18.040524] device wlan0 entered promiscuous mode
[   18.045439] br-lan: port 2(wlan0) entered forwarding state
[   18.051006] br-lan: port 2(wlan0) entered forwarding state
[   18.058039] ieee80211 phy0: change: 0x100
[   18.067330] ieee80211 phy0: change: 0x40
[   18.241771] ieee80211 phy0: change: 0x40
[   18.321806] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   18.329752] br-lan: port 1(eth0) entered forwarding state
[   18.335308] br-lan: port 1(eth0) entered forwarding state
[   18.411788] ieee80211 phy0: change: 0x40
[   18.428974] ieee80211 phy1: change: 0xffffffff
[   18.522088] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   18.530527] device wlan1 entered promiscuous mode
[   18.535452] br-lan: port 3(wlan1) entered forwarding state
[   18.541032] br-lan: port 3(wlan1) entered forwarding state
[   18.546986] mvneta f1074000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[   18.549546] ieee80211 phy1: change: 0x100
[   18.554684] ieee80211 phy1: change: 0x60
[   18.581788] ieee80211 phy0: change: 0x40
[   18.646868] br-lan: port 2(wlan0) entered disabled state
[   18.652709] br-lan: port 3(wlan1) entered disabled state
[   18.658192] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   18.731752] ieee80211 phy1: change: 0x40
[   18.779614] ieee80211 phy0: change: 0x40
[   18.911873] ieee80211 phy1: change: 0x60
[   18.951794] ieee80211 phy0: change: 0x40
[   18.988030] ieee80211 phy1: change: 0x100
[   19.110941] ieee80211 phy1: change: 0x100
[   19.120132] ieee80211 phy1: change: 0x62
[   19.131768] ieee80211 phy0: change: 0x40
[   19.226347] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   19.232950] br-lan: port 3(wlan1) entered forwarding state
[   19.238539] br-lan: port 3(wlan1) entered forwarding state
[   19.316862] ieee80211 phy0: change: 0x40
[   19.386027] ieee80211 phy1: change: 0x20
[   19.502073] ieee80211 phy0: change: 0x40
[   19.671799] ieee80211 phy0: change: 0x40
[   19.841823] ieee80211 phy0: change: 0x40
[   20.011771] ieee80211 phy0: change: 0x40
[   20.077012] ieee80211 phy0: change: 0x100
[   20.186361] ieee80211 phy0: change: 0x100
[   20.195453] ieee80211 phy0: change: 0x42
[   20.290682] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   20.297378] br-lan: port 2(wlan0) entered forwarding state
[   20.303036] br-lan: port 2(wlan0) entered forwarding state
[   20.331717] br-lan: port 1(eth0) entered forwarding state
[   21.231692] br-lan: port 3(wlan1) entered forwarding state
[   22.301747] br-lan: port 2(wlan0) entered forwarding state
[ 9835.782437] ieee80211 phy0: check ba result error 1
[ 9835.787437] ieee80211 phy0: ampdu start error code: -22
[ 9835.822463] ieee80211 phy0: check ba result error 1
[ 9835.827618] ieee80211 phy0: ampdu start error code: -22
[ 9835.862400] ieee80211 phy0: check ba result error 1
[ 9835.867474] ieee80211 phy0: ampdu start error code: -22
[ 9835.902440] ieee80211 phy0: check ba result error 1
[ 9835.907423] ieee80211 phy0: ampdu start error code: -22
[ 9835.942472] ieee80211 phy0: check ba result error 1
[ 9835.947683] ieee80211 phy0: ampdu start error code: -22
[ 9835.982480] ieee80211 phy0: check ba result error 1
[ 9835.987477] ieee80211 phy0: ampdu start error code: -22
[ 9836.032444] ieee80211 phy0: check ba result error 1
[ 9836.037418] ieee80211 phy0: ampdu start error code: -22
[ 9836.072443] ieee80211 phy0: check ba result error 1
[ 9836.077422] ieee80211 phy0: ampdu start error code: -22
[ 9836.112447] ieee80211 phy0: check ba result error 1
[ 9836.117448] ieee80211 phy0: ampdu start error code: -22
[ 9836.152444] ieee80211 phy0: check ba result error 1
[ 9836.157552] ieee80211 phy0: ampdu start error code: -22
[ 9836.192474] ieee80211 phy0: check ba result error 1
[ 9836.197446] ieee80211 phy0: ampdu start error code: -22
[ 9836.232476] ieee80211 phy0: check ba result error 1
[ 9836.237447] ieee80211 phy0: ampdu start error code: -22
[ 9836.272439] ieee80211 phy0: check ba result error 1
[ 9836.277436] ieee80211 phy0: ampdu start error code: -22
[ 9836.312449] ieee80211 phy0: check ba result error 1
[ 9836.317439] ieee80211 phy0: ampdu start error code: -22
[ 9836.352452] ieee80211 phy0: check ba result error 1
[ 9836.358030] ieee80211 phy0: ampdu start error code: -22
[ 9836.392405] ieee80211 phy0: check ba result error 1
[ 9836.398011] ieee80211 phy0: ampdu start error code: -22
[ 9836.442436] ieee80211 phy0: check ba result error 1
[ 9836.447493] ieee80211 phy0: ampdu start error code: -22
[ 9836.492448] ieee80211 phy0: check ba result error 1
[ 9836.498227] ieee80211 phy0: ampdu start error code: -22
[ 9836.542450] ieee80211 phy0: check ba result error 1
[ 9836.547432] ieee80211 phy0: ampdu start error code: -22
[ 9836.592482] ieee80211 phy0: check ba result error 1
[ 9836.597533] ieee80211 phy0: ampdu start error code: -22
[ 9836.632439] ieee80211 phy0: check ba result error 1
[ 9836.637489] ieee80211 phy0: ampdu start error code: -22
[ 9836.772503] ieee80211 phy0: check ba result error 1
[ 9836.777520] ieee80211 phy0: ampdu start error code: -22
[ 9836.812452] ieee80211 phy0: check ba result error 1
[ 9836.817804] ieee80211 phy0: ampdu start error code: -22
[ 9836.852453] ieee80211 phy0: check ba result error 1
[ 9836.857451] ieee80211 phy0: ampdu start error code: -22
[ 9836.902459] ieee80211 phy0: check ba result error 1
[ 9836.907612] ieee80211 phy0: ampdu start error code: -22
[ 9836.942470] ieee80211 phy0: check ba result error 1
[ 9836.947688] ieee80211 phy0: ampdu start error code: -22
[ 9836.992455] ieee80211 phy0: check ba result error 1
[ 9836.998120] ieee80211 phy0: ampdu start error code: -22
[ 9837.032455] ieee80211 phy0: check ba result error 1
[ 9837.037686] ieee80211 phy0: ampdu start error code: -22
[ 9837.072864] ieee80211 phy0: check ba result error 1
[ 9837.079106] ieee80211 phy0: ampdu start error code: -22
[ 9837.112424] ieee80211 phy0: check ba result error 1
[ 9837.117733] ieee80211 phy0: ampdu start error code: -22
[ 9837.163060] ieee80211 phy0: check ba result error 1
[ 9837.168055] ieee80211 phy0: ampdu start error code: -22
[ 9837.222495] ieee80211 phy0: check ba result error 1
[ 9837.227858] ieee80211 phy0: ampdu start error code: -22
[ 9837.272624] ieee80211 phy0: check ba result error 1
[ 9837.277626] ieee80211 phy0: ampdu start error code: -22
[ 9837.322415] ieee80211 phy0: check ba result error 1
[ 9837.327395] ieee80211 phy0: ampdu start error code: -22
[ 9837.362427] ieee80211 phy0: check ba result error 1
[ 9837.367413] ieee80211 phy0: ampdu start error code: -22
[18725.713089] ieee80211 phy1: check ba result error 1
[18725.718161] ieee80211 phy1: ampdu start error code: -22
[18725.753089] ieee80211 phy1: check ba result error 1
[18725.758073] ieee80211 phy1: ampdu start error code: -22

@Juni0rM1nt

Known driver issue, from what I recall.

Max Hopper wrote:
samfree91 wrote:

... WRT1200AC ...

Why is this posted in the WRT1900AC thread?

cmsigler advises you to begin here.

Okay so after some further reading i know what version ill get (the stock open wrt image for now)

Further question Can i compile soft ether onto this device? as following the instructions in the link below, leaves me puzzled with the references to AR7XXX or AR 9XXX when i beleive we would have to compile a package for mvebu... how can i go about this, whats the differences in the tutorial? is it only the architecture?

http://tocan.de/en/blog/2015/04/06/soft … inrichten/

Thanks again

Has anyone seen any active dhcp lease wonkiness on trunk (k4.4.7, r49207)?

Under Active DHCP Leases, I have every single statically assigned IP listed, with a netmask of /32 and a lease time remaining of 7942d 2h 46m, or 21 years, 9 months lol (/tmp/dhcp.leases is empty, however Active DHCPv6 Leases is accurate)

Is this due to something on my end within a config, or should I file a bug report?

(Last edited by JW0914 on 22 Apr 2016, 01:31)

@Juni0rM1nt

That excerpt is from the boot log. Do you see the same during normal operation?

nitroshift

@tomce

Since you already have a modem, why don't you let it handle the PPPoE connection itself? Also, the buffer manager has been already tested and patches sent to Kaloz but he didn't have time to push them upstream. The changes they bring have been upstreamed in kernel 4.6 anyway.

nitroshift

(Last edited by nitroshift on 22 Apr 2016, 05:14)

@JW0914

When I first set up this device about a month ago I also had issues, like the printer not receiving the hostname and terribly poor dns performance (the ISPs nameserver is slow but this shouldn't break 90% off all queries). As there is no document properly describing odhcpd I simply removed it and use dnsmasq-full instead. All dhcp/dns issues are gone. Whether I sucked at configuration or if there is a bug I can't tell.

nitroshift wrote:

@tomce

Since you already have a modem, why don't you let it handle the PPPoE connection itself? Also, the buffer manager has been already tested and patches sent to Kaloz but he didn't have time to push them upstream. The changes they bring have been upstreamed in kernel 4.6 anyway.

nitroshift

1) Currently is running PPPoE pass-through mode (or in other words modem in bridged mode), so my wan interface acts as modem.
2) I am using stable release, I don't think I can patch this.

hi, WRT1200ac questions:
I tried to jump through the 437 pages of this discussion trying to find an answer on the 5GHz problem (which is not turning on, on chaos calmer), if there is a solution could someone tell me how to get it on? Could anyone give any recommendation on which firmware to use? What settings do you use for the 5GHz radio?

I got linked here from the wiki page, if there is a solution to common problems (like the 5GHz) it is maybe a good idea to put it on the wiki, so people like me don't have to flood this discussion with the same question.

sera wrote:

@JW0914

When I first set up this device about a month ago I also had issues, like the printer not receiving the hostname and terribly poor dns performance (the ISPs nameserver is slow but this shouldn't break 90% off all queries). As there is no document properly describing odhcpd I simply removed it and use dnsmasq-full instead. All dhcp/dns issues are gone. Whether I sucked at configuration or if there is a bug I can't tell.

odhcpd works great and I've used it since first switching to OpenWRT ~18 months ago.   I'm beginning to suspect this might be a config file with an anomally I missed, as I know I didn't have this issue with kernel 4.1.6 and trunk from 02/07.  I'll double check all odhcpd related configs again and file a bug report if I can't find anything.

Your prior issue sounds like it could have been caused by wonkiness in a config file (especially if you edited configs in a notepad on Windows, as Windows terminates lines with CR LF vs LF on *nix), an unterminated value (i.e. missing enclosed single quotes for a value), a network issue with traffic on ports 67 & 68 (or requests to 0.0.0.0/multicast not being routed properly), or a one off bug that was fixed.

(Last edited by JW0914 on 22 Apr 2016, 12:33)

Cracked after 3 months and sent it back to Amazon (wrt1900acs)... Never felt so happy and elated!!!

Good Riddance! wink

@JW0914

I use vim on linux or busybox vi on the device itself to edit files. For me it felt as if odhcpd and dnsmasq don't play nice with each other in the default setup which would be a bug. But as I can't tell I reduced the problem to what I know. Just take it as a hint to narrow down your issue.

dnsmasq and odhcpd work fine together, going hand in hand, in the default config or with a custom one.  When you had this issue, was it a custom built image, or 15.05?  If it wasn't a custom built image, it could have been wonkiness with a flash, especially if you had this issue immediately after flashing, and prior to customizing the configs.  One can usually verify if the issue is the firmware or their environment (i.e. config files) by asking if anyone else had the issue; if none did, it's not an issue with the firmware (unless it's a custom built image). 

I've had too many issues with flashing via the WebGUI or via sysupgrade that I now flash exclusively via TFTP.  I installed an audio jack into the side of the router to make TFTP flashing extremely convenient, which also allows you to verify nothing went wrong upon the next boot by verifying the router goes into promiscuous mode.

(Last edited by JW0914 on 22 Apr 2016, 13:08)

I use "sysupgrade -n" unless I have to use ttl. Custom image without luci, always built from git HEAD.

The issue persisted over many flashes and configs. The many flashes came from having to add missing or crippled utils for debugging one at a time.

dnsmasq and odhcpd work fine together

At this point I really wonder why we have both in tandem. What does odhcpd add on top of dnsmaq? Why should I go back?

PS: Never thought about an audio jack, nice one.

Sorry, posts 10926 to 10925 are missing from our archive.