I'm not sure what I could do to fix this. I'd be happy to try reinstall 388.6 if there is anything anyone can suggest for me to get it working or just to have a second look at logs.
After downgrade to 388.5 DLNA works again.
I had a similar problem during the beta, and again this morning when I tried to upgrade from 3004.388.5 to .6 - nothing seemed to be working, and (the clue was) nothing seemed to be able to resolve DNS addresses. Once I realized that hint, I went to the system log and found that DNSMASQ startup was failing with a bad line in the /etc/dnsmasq.conf file.
For me, the bad line was
dns-forward-max=500
which I had added via /jffs/configs/dnsmasq.conf.add
. It turns out that this latest release has added the dns-forward-max=1500
directive - dnsmasq won't accept duplicate entries (you have to edit these with /jffs/scripts/dnsmasq.postconf
if you want to change an existing directive). Once I commented out my (newly duplicated) entry, I was able to upgrade to 3004.388.6 without problem.Important note - it is surprising how many things in the router code depend on DNS running properly. Some are obvious: anything that needs to resolve an external name to work, e.g., DDNS, VPN connections, etc. Some less obvious - for example, ALL of my AIMesh nodes failed to reconnect when dnsmasq wasn't running properly. Also, I was unable to SSH into the router while DNSMASQ wasn't running (I had to downgrade to .5 so that I could comment out the offending entry in
/jffs/configs/dnsmasq.conf
)So...check your system logs for a failed dnsmasq startup (or any other errors that aren't there when you boot up the 3004.388.5 release).
Last edited: