Just upgraded the mt300a after the notification on Facebook. Unfortunately the update broke DHCP completely for IPv4 (IPv6 was fine :s), no addresses or DNS were given, had to revert to the old firmware to get it working again. For now I’ve forced clients to use Google DNS.
Note to self, don’t install updates without testing on a backup device first. Also, get another backup >.<
Can you provide an updated version for lede-gl-ar300md-3.03.tar which already uses LEDE <span style=“color: #404040; font-family: ‘Helvetica Neue’, Helvetica, Arial, sans-serif; font-size: 13px;”>17.01.4, released today, which already has the patches for dnsmasq and WPA2 ?</span>
At this way we can use the standard repositories as well.
<p class=“p1”><span class=“s1”>fw_setenv bootcount 3</span></p>
<p class=“p1”>I can force to boot from the NOR, but I want to make sure that this is the case at any time the device reboots, so I assumed that I can put that at the rc.local, before the exit 0.</p>
<p class=“p1”>However it doesn’t work. What I’m missing?</p>
Testing on AR300M (upgraded with “keep settings”)
If “force all clients to use” is checked under custom DNS, then there is zero bandwidth, Unchecking it and all seems fine.
@evilbob333 Did you have a chance to try what @Glitch suggested? I haven’t yet, but I plan to. I cannot remember if I had “Force all clients to use” enabled or not, but it wasn’t enabled when I reverted (keeping settings) so I assume I didn’t.
Nice to know I’m not the only one who had this problem though!
@mpmc I do not have “Force all clients to use” checked on my router, though I am using custom DNS. On my mobile devices, I was not getting an IP address, and on my laptop, I had to give it a static IP address in order to get in to web interface to get the 2.261 back on.
It looks like DHCP is working with the new firmware. And ditto to Glitch’s sentiments. You guys are awesome. I’m looking forward to the GL-AR750 coming out.