Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Sun Aug 16, 2020 20:33 Post subject:
aventus wrote:
Linksys wrt 1200ac
Some problems with Wireguard in allowed ip I added few dns servers they got ignored it used the dns servers from setup page and if I disable endpoint to check if killswitch works it’s still connected to endpoint even after restart
With build 44112 everything works
there is no change in wireguard since 44112. not in the gui, not in the code. sounds bogus to me. _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Last edited by BrainSlayer on Sun Aug 16, 2020 20:38; edited 1 time in total
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Sun Aug 16, 2020 20:37 Post subject:
aventus wrote:
Linksys wrt 1200ac
Some problems with Wireguard in allowed ip I added few dns servers they got ignored it used the dns servers from setup page and if I disable endpoint to check if killswitch works it’s still connected to endpoint even after restart
With build 44112 everything works
wireguard never uses dns entries from the setup page. it only uses servers you defined and nothing else.
and do not forget to press apply. otherwise no setting will be taken _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
regarding the nat redirection. consider that the nat redirection is not compatible if QOS is enabled since it uses connection marks _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
regarding the nat redirection. consider that the nat redirection is not compatible if QOS is enabled since it uses connection marks
didn't know such
well hell .... that is some new bullshit but it works on r44191 if I disable QOS
guess I'll have to decide if I still want new builds or QOS
---
EDIT:just a note...and I'll get outta this Marvelly forum
r44213 is now very good for me.
NAT loopback worky good and also QOS.
thanky very much, BS
Last edited by mrjcd on Mon Aug 17, 2020 23:12; edited 1 time in total
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Aug 17, 2020 2:52 Post subject:
Upgraded all routers to r44191 IE11 reset 1900's 3200's no reset.
Upgrades went well without problem.
Still having Reboot/Disconnect problems on 1900V1 WDS Station out in the barn. Continuing to diagnose and monitor.
At about 4.5 hours monitoring all routers with IE11 they suddenly became unresponsive (no GUI). I could close IE11 and restart, signin name/password but no GUI. All 5 routers were doing this. I could telnet into the routers and tried using "restart httpd" but although the router accepted and executed the command GUI was still not available.
All router functions and connections were active and functioning correctly except GUI access. I did try MS EDGE (BETA) but it wouldn't even display the signin.
I next rebooted my desktop and upon restarting I was able to access all routers without any problem. MS EDGE also worked.
Conclusion is that obviously leaving the system monitoring the routers causes some kind of hang up within WIN10. Obviously not a DD-WRT problem, but interesting anyway. I was worried that the GUI loss that occurred in previous builds was back.
I will be continuing to monitor for the 1900 reboot problem tomorrow and shut down (sleep) this desktop overnight. Currently over 5 hours without problem. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Router: Linksys WRT1900ACSv2
Firmware: DD-WRT v3.0-r44191 std (08/15/20) prev. r44187
Kernel: Linux 4.9.232 #2023 SMP Sat Aug 15 07:22:31 +03 2020 armv7l
Browser: Opera Stable 70.0 (Windows 10 64-bit)
Reset: No
Mode: Time: 13:02:25 up 1:34, load average: 0.00, 0.00, 0.00
Ignore WAN DNS, DHCP Server, DHCP-Authoritative, Forced DNS Redirection.
Dnsmasq: Cache DNSSEC data, Validate DNS Replies (DNSSEC), Check unsigned DNS replies, No DNS Rebind.
DNSCrypt2 (2.0.39 Entware)
addn-hosts=Mr. SurprisedItWorks code
5 GHz: AP AC/N-Mixed, Channel 161+Lower, Wide HT40, Allow Channel Overlapping, Short Preamble, Short GI, Single User Beamforming.
2.4 GHz: AP NG-Mixed, Channel 5, Full 20 MHz, TurboQAM (QAM256) support, Short Preamble, Short GI.
Security: WPA2 Personal CCMP-128 (AES)
NAS via USB:
/dev/sda - Block device, size 931.5GiB, Partition: 1-Ext4, 2-Ext4 , 3-swap.
Samba shared: Protocol Version SMB 2.10\SMB 3.11
NFS Server shared: Shared the same partitions as in Samba.
Transmission Daemon - Enable.
Errors:
The log is swollen from the messages (showing the first and last):
Code:
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.108413] ------------[ cut here ]------------
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.113156] WARNING: CPU: 0 PID: 4 at /home/seg/DEV/mvebu/src/router/smbd-next/smbd/buffer_pool.c:364 ksmbd_free_work_struct+0x40/0xa4 [ksmbd]
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.126013] Modules linked in: ksmbd ext4 jbd2 mbcache crc32_generic ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sr_mod cdrom sd_mod xhci_pla
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.183653] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.232 #2023
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.190120] Hardware name: Marvell Armada 380/385 (Device Tree)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.196076] Workqueue: ksmbd-io __smb2_oplock_break_noti [ksmbd]
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.202127] [<c011356c>] (unwind_backtrace) from [<c010ee54>] (show_stack+0x10/0x14)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.209907] [<c010ee54>] (show_stack) from [<c03145b0>] (dump_stack+0x90/0xa4)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.217162] [<c03145b0>] (dump_stack) from [<c01b63b0>] (__warn+0xe4/0x100)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.224154] [<c01b63b0>] (__warn) from [<c0129cf0>] (warn_slowpath_null+0x20/0x28)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.231764] [<c0129cf0>] (warn_slowpath_null) from [<bfa9a140>] (ksmbd_free_work_struct+0x40/0xa4 [ksmbd])
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.241488] [<bfa9a140>] (ksmbd_free_work_struct [ksmbd]) from [<bfa90a5c>] (__smb2_oplock_break_noti+0x298/0x2c0 [ksmbd])
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.252588] [<bfa90a5c>] (__smb2_oplock_break_noti [ksmbd]) from [<c01430f4>] (process_one_work+0x284/0x408)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.262458] [<c01430f4>] (process_one_work) from [<c0143630>] (worker_thread+0x3b8/0x5cc)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.270672] [<c0143630>] (worker_thread) from [<c0148550>] (kthread+0x150/0x158)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.278100] [<c0148550>] (kthread) from [<c010ba80>] (ret_from_fork+0x14/0x34)
Aug 17 09:04:16 LinkSYS kern.warn kernel: [ 2179.285418] ---[ end trace a91bfa55adc900e8 ]---
++++++++++++++++++++++++++++++++
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.902868] ------------[ cut here ]------------
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.907521] WARNING: CPU: 1 PID: 1024 at /home/seg/DEV/mvebu/src/router/smbd-next/smbd/buffer_pool.c:364 ksmbd_free_work_struct+0x40/0xa4 [ksmbd]
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.920626] Modules linked in: ksmbd ext4 jbd2 mbcache crc32_generic ledtrig_usbport pwrseq_simple pwrseq_emmc ahci_mvebu ahci_platform ahci libahci_platform libahci ehci_orion sata_mv usb_storage sr_mod cdrom sd_mod xhci_pla
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.978102] CPU: 1 PID: 1024 Comm: kworker/1:3 Tainted: G W 4.9.232 #2023
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.986050] Hardware name: Marvell Armada 380/385 (Device Tree)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.992003] Workqueue: ksmbd-io handle_ksmbd_work [ksmbd]
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4837.997441] [<c011356c>] (unwind_backtrace) from [<c010ee54>] (show_stack+0x10/0x14)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.005220] [<c010ee54>] (show_stack) from [<c03145b0>] (dump_stack+0x90/0xa4)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.012474] [<c03145b0>] (dump_stack) from [<c01b63b0>] (__warn+0xe4/0x100)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.019466] [<c01b63b0>] (__warn) from [<c0129cf0>] (warn_slowpath_null+0x20/0x28)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.027077] [<c0129cf0>] (warn_slowpath_null) from [<bfa9a140>] (ksmbd_free_work_struct+0x40/0xa4 [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.036785] [<bfa9a140>] (ksmbd_free_work_struct [ksmbd]) from [<bfa90a5c>] (__smb2_oplock_break_noti+0x298/0x2c0 [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.047888] [<bfa90a5c>] (__smb2_oplock_break_noti [ksmbd]) from [<bfa9128c>] (__smb2_lease_break_noti+0x620/0x828 [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.059078] [<bfa9128c>] (__smb2_lease_break_noti [ksmbd]) from [<bfa929f8>] (smb_break_all_levII_oplock+0x1a8/0x2ac [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.070441] [<bfa929f8>] (smb_break_all_levII_oplock [ksmbd]) from [<bfaa6b48>] (smb2_lock+0xde8/0x1110 [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.080671] [<bfaa6b48>] (smb2_lock [ksmbd]) from [<bfa98598>] (handle_ksmbd_work+0x2c0/0x474 [ksmbd])
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.090026] [<bfa98598>] (handle_ksmbd_work [ksmbd]) from [<c01430f4>] (process_one_work+0x284/0x408)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.099286] [<c01430f4>] (process_one_work) from [<c0143630>] (worker_thread+0x3b8/0x5cc)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.107497] [<c0143630>] (worker_thread) from [<c0148550>] (kthread+0x150/0x158)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.114926] [<c0148550>] (kthread) from [<c010ba80>] (ret_from_fork+0x14/0x34)
Aug 17 09:48:35 LinkSYS kern.warn kernel: [ 4838.122233] ---[ end trace a91bfa55adc90183 ]---
Upgraded WRT1200AC v1's from r44187 to r44191 using Brave Version 1.10.97 (64-bit) running on Linux Mint 20 OS.
Successful update and reboot. No reset, nothing disabled prior to update, uptime aproximatly 30 hrs, wireless connected, vpn up immediately (Expressvpn). I do not use NAS. SFE is always disabled. OpenVPN client/DNSMasq, QoS with PIE always enabled.
Kernel VersionLinux 4.9.232 #2023 SMP Sat Aug 15 07:22:31 +03 2020 armv7l
No load average problems. No GUI problems. Today passing thru two wired Corp VPN's (work from home), all other wired/wireless thru router VPN, last night wireless streaming great with no drops/buffering.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Aug 17, 2020 16:02 Post subject:
Overnight Update;
All routers continue to function correctly except the 1900V1 WDS Station in my barn. This is a specific ongoing problem not related to just r44191 and therefore will continue to post actions as results elsewhere.
All routers continue to function correctly except the 1900V1 WDS Station in my barn. This is a specific ongoing problem not related to just r44191 and therefore will continue to post actions as results elsewhere.
One suggestion I will offer is to check your power-line supply to the barn. If it's air or grounded the possibility of small power surges/drops could be affecting your 1900's stability. Daily temp increases/decreases can affect voltage as well depending on wiring age/length. Random storms will also add to any unsteady voltage issues.
Putting a cheap battery backup in front of the router might be all that is needed??? I mention it as I had a similar stability problem several years ago that was voltage related and eliminated by a battery backup. The rural house was built in 1896 with the electrical surges/drops being so tiny that the only detection was the battery backup randomly kicking on/off for a split second with no other visible changes in power supply noticed. The battery backup eliminated my problem so I will pass it on.
The only known solution for Marvell 2.4 GHz authenticated deauthenticated loops (aside from playing around with different builds) is to disable WMM Support and/or select G-Only or BG-Mixed, Full 20 MHz Channel Width and simplify Wireless Security i.e. WPA2 Personal, CCMP-128 (AES) only, the defaults. Legacy data rates are key to work around this wifi driver and/or binary blob issue.
Last edited by blkt on Fri Aug 21, 2020 20:56; edited 4 times in total
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Aug 17, 2020 17:59 Post subject:
Monza wrote:
WENED wrote:
All routers continue to function correctly except the 1900V1 WDS Station in my barn. This is a specific ongoing problem not related to just r44191 and therefore will continue to post actions as results elsewhere.
One suggestion I will offer is to check your power-line supply to the barn. If it's air or grounded the possibility of small power surges/drops could be affecting your 1900's stability. Daily temp increases/decreases can affect voltage as well depending on wiring age/length. Random storms will also add to any unsteady voltage issues.
Putting a cheap battery backup in front of the router might be all that is needed??? I mention it as I had a similar stability problem several years ago that was voltage related and eliminated by a battery backup. The rural house was built in 1896 with the electrical surges/drops being so tiny that the only detection was the battery backup randomly kicking on/off for a split second with no other visible changes in power supply noticed. The battery backup eliminated my problem so I will pass it on.
I appreciate your advise but over the past couple of years I already have done as you suggested. Not only have I installed a small UPS on the router but have replaced the power pack and upgraded same to sustain a stable supply. The problem I have is that if I run build r31924 the router runs flawlessly even with variations in hydro power (voltage and frequency). I have swapped the router with another 1900V1 and have the same results. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
can someone tell me if upnp works in this build, I had destiny 2 all of a sudden not work till i forwarded ports..... Could be just me but i figured id ask someone to check
please check if its enabled of course and if you see entries on the gui for upnp but its still not working, post iptables -Lvn output (from telnet or ssh console)
so i can check if everything is correct
NOTE I AM ON THE NEXT BUILD NOW BS!!!! i am slammed at IT hell aka work.
QOS off, Upnp ON
I also added the log of some red errors in the next build thread PEace for now.
root@ArkhamAsylum:~# iptables -vnL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
2428 342K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
0 0 DROP udp -- eth1 * 0.0.0.0/0 0.0.0.0/0 udp dpt:520
0 0 DROP udp -- br0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:520
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:520
0 0 ACCEPT tcp -- * * 0.0.0.0/0 192.168.1.1 tcp dpt:443
3 108 DROP icmp -- eth1 * 0.0.0.0/0 0.0.0.0/0
10 280 DROP 2 -- * * 0.0.0.0/0 0.0.0.0/0
5 312 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 state NEW
1773 299K ACCEPT all -- br0 * 0.0.0.0/0 0.0.0.0/0 state NEW
308 17245 DROP all -- * * 0.0.0.0/0 0.0.0.0/0
Joined: 09 May 2019 Posts: 2 Location: Netherlands
Posted: Thu Aug 20, 2020 7:05 Post subject:
Hi
1900ACSV2 wifi disconnects frequently or just having no internet.
Reboot helps only temporary. This was the case also with previous version.
Finally, I gave up and installed some randomly choosen older firmware (turned out to be DD-WRT v3.0-r43055 std (05/05/20) ).
So far, everything works second day already without rebooting.
I can't be more specific at the moment as to check which version was the first to introduce issues, because I need stable internet in my home office.