Joined: 08 May 2018 Posts: 7962 Location: Texas, USA
Posted: Fri Oct 30, 2020 17:23 Post subject: New Build 44700 - 10-30-2020-r44700
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and specific device recovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Notes:
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle. 6920, 6928, 6931, 6932 (WIP 7040)
• In-kernel Samba has been implemented this year and default min/max versions have changed 6954, 6957, with WSD support.
• VAP issue is fixed! For any Wireless Mode, create a VAP and both ath0/ath1 should now function properly.
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
• WireGuard 1.0.20200908 & Tools: PBR, Kill Switch, Inbound Firewall, Naming of Peers, Status, Key, Guides. Thanks BS & egc!
Issues:
• There may be remaining issues for Samba (for example NTFS), with frequent updates.
Important:
• If reporting issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, serial output, strace, tcpdump etc.
• For firewall NAT or WAN issues provide 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and the /tmp/.ipt file.
• Search existing SVN tickets before opening a new one. Before reporting, reset and manually setup (no nvram backup).
• Be sure to include operating and wireless modes (Gateway, AP, CB, etc.) along with relevant configuration information.
Joined: 16 Nov 2015 Posts: 4166 Location: UK, London, just across the river..
Posted: Fri Oct 30, 2020 21:52 Post subject:
Router Model TP-Link WR1043ND V2
Firmware Version DD-WRT v3.0-r44700 std (10/30/20)
Kernel Version Linux 3.18.140-d5 #95178 Fri Oct 30 01:35:26 GMT 2020 mips
update: CLI 46627 > 44700
reset: NO
status: Operational 1h+
errors: Nothing new
sweet just flashed it via SSh and got lost in space... TP-link 1043v2 44700
no more SSh(cli) control over the unit...cannot execute reboot and various other commands...
cannot get to the GUI, as CLI does not execute commands and my gui is locked, how sweet...cannot attend physical reboot too, as im far away of the unit, but unit still operational...touch wood...
p.s. just logged me off SSh, no more SSh...its get funky now...
p.s. 2 managed to power down the room where the router is it did the trick, unit is operational...back to normal, SSh works ok, VPN works ok, everything's fine..!!
10x BS
_________________ Atheros
TP-Link WR740Nv1 -----DD-WRT 45711 BS AP,NAT
TP-Link WR740Nv4 -----DD-WRT 44251 BS WAP/Switch
TP-Link WR1043NDv2 ---DD-WRT 45820 BS AP,NAT,AP Isolation,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---DD-WRT 45711 BS AP,NAT,AD/Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Qualcomm/IPQ8065
Netgear R7800 -----DD-WRT 45735 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Broadcom
Netgear R7000 -----DD-WRT 45735 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,VLAN's,DoT,VPN
-----------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Fri Oct 30, 2020 23:37; edited 1 time in total
Updated my R7800 via ssh, no troubles but for some reason my DNS IP changed from my Pi-Hole RPi to 8.8.8.8 I don't know if it's changed after the reboot or it was already changed but I'm sure I was using 192.168.1.4 (my RPi).
Add the below line in to Additional Dnsmasq Options
dhcp-option=6,192.168.1.4 #pihole ip
giuliomagnifico wrote:
Updated my R7800 via ssh, no troubles but for some reason my DNS IP changed from my Pi-Hole RPi to 8.8.8.8 I don't know if it's changed after the reboot or it was already changed but I'm sure I was using 192.168.1.4 (my RPi).