Posted: Wed Feb 18, 2015 1:39 Post subject: WR841N new firmware, new issues
Hi,
I have a TP-Link WR-841N v7.1 that has been upgraded to the following build:
Code:
Router Model
TP-Link TL-WR841ND v7
Firmware Version
DD-WRT v24-sp2 (01/20/15) std - build 25974
Kernel Version
Linux 3.5.7.33 #18903 Tue Jan 20 06:09:12 CET 2015 mips
Now there are a few features that is not working.
1. DHCP is not working, although all settings are normal:
Code:
DHCP Type: DHCP Server
DHCP Server: Enable
Start IP Address: 192.168.10.100
Maximum DHCP Users: 50
Use DNSMasq for DHCP: Yes
Use DNSMasq for DNS: Yes
DHCP-Authoritative: Yes
Forced DNS Redirection: Yes
Both DHCP and DHCP reservation does not working. Setting the IP manually on the client works well, though.
2. NTP doesn't update time automatically. I have enabled the NTP client, used my local NTP server here in my country (which is verified working because I can update time from my computer), and have set the current time zone.
3. I cannot access another computer via LAN, but able to access it via WiFi.
For example, PC A (192.168.10.10, Static) is connected through Ethernet port 1 on the router and PC B (192.168.10.20, Static) is connected through Ethernet port 2 on the router. Both PCs can browse the Web but cannot ping each other.
If I disconnected the LAN cable on PC B and connected it using USB WiFi Adapter, PC B can ping PC A and PC A can access Samba shares on PC B.
4. After working for ~1 hour, Internet connection will cease to work through WiFi (although SSID still appears and new clients can still connect). LAN connections are fine, however.
Are these issues caused by the new firmware? I previously used an ancient build of DD-WRT from 2012, then just updated the router a few weeks ago. (I have done a factory reset, and these issues are still there.)
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 18, 2015 3:27 Post subject:
those arent default settings, forced dns redirection is not enabled by default, restore factory defaults or "erase nvram" "reboot" & check again, &/or disable forced dns redirection if the static dns fields are empty (0.0.0.0) _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
DHCP is broken in wr841n since build r25697, I've tested in two units (wr841n and wr841nd, v8 and v7) and there's no DHCP even doing a 30/30/30 after flashing, the same situation occurs with the latest beta r26490. Assigning IPs manually is the only way to make them work.
This is again the WR841ND v7/v8 DHCP problem... Someone should open a ticket already ! _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
DDWRT in latest builds have broken DHCP, i also issued DHCP problems, random internet drops via WIFI etc.. So i migrated to Gargoyle firmware. I looks and its compatible for TL841ND, buti suppose that will work also in 841N because its the same hardver inside.
Any news about the last build (r26866)? Just asking before trying once again... If DHCP is still broken I'm going to report the issue in the Mantis bug tracking system as I didn't find it reported.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun May 17, 2015 5:54 Post subject:
if someone with one of these small flash tplinks or any other affected router (seems to be only 4mb flash ones, not surprised) can find the EXACT last public build (no guessing) with working dnsmasq it would probably help..the bug is already reported on trac but is lacking info severely..
forget mantis, thats old & never looked at _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
if someone with one of these small flash tplinks or any other affected router (seems to be only 4mb flash ones, not surprised) can find the EXACT last public build (no guessing) with working dnsmasq it would probably help..the bug is already reported on trac but is lacking info severely..
The last build that is working correctly with DHCP is 25544 for v7. For v8 is r25648.
if someone with one of these small flash tplinks or any other affected router (seems to be only 4mb flash ones, not surprised) can find the EXACT last public build (no guessing) with working dnsmasq it would probably help..the bug is already reported on trac but is lacking info severely..
The last build that is working correctly with DHCP is 25544 for v7. For v8 is r25648.
TP-Link TL-WR841N v9.2. r25697.
DNSMasq working perfectly (LAN,Wi-Fi,guest Wi-Fi)
