NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
PR460X crash
My PR460X on firmware 2.7.0.111 (current latest available) sometimes crashes. Stack trace from the crash logs below. This appears to be a firmware/driver bug. 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.476240] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1559 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.476262] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/3 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.483736] CPU: 3 PID: 0 Comm: swapper/3 Tainted: P 5.4.164 #0 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.491544] Hardware name: Generic DT based system 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.499016] [<4210fa8c>] (unwind_backtrace) from [<4210b870>] (show_stack+0x10/0x14) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.503608] [<4210b870>] (show_stack) from [<42738500>] (dump_stack+0x88/0xa8) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.511506] [<42738500>] (dump_stack) from [<4213e278>] (___might_sleep+0x13c/0x17c) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.518538] [<4213e278>] (___might_sleep) from [<42751ebc>] (down_write+0x18/0x70) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.526438] [<42751ebc>] (down_write) from [<42355ffc>] (debugfs_remove+0x24/0x60) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.533823] [<42355ffc>] (debugfs_remove) from [<3f7a8888>] (eip_ctx_final+0x38/0x68 [qca_nss_eip]) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.541396] [<3f7a8888>] (eip_ctx_final [qca_nss_eip]) from [<3f7ac310>] (eip_tr_inval_done+0x44/0x90 [qca_nss_eip]) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.550317] [<3f7ac310>] (eip_tr_inval_done [qca_nss_eip]) from [<3f7a8e88>] (eip_dma_napi_rx_poll+0x230/0x29c [qca_nss_ei p]) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.561080] [<3f7a8e88>] (eip_dma_napi_rx_poll [qca_nss_eip]) from [<425ffef8>] (__napi_poll+0x28/0xb8) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.572272] [<425ffef8>] (__napi_poll) from [<4260012c>] (net_rx_action+0xf0/0x280) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.581472] [<4260012c>] (net_rx_action) from [<42102148>] (__do_softirq+0xd0/0x280) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.589114] [<42102148>] (__do_softirq) from [<42120f20>] (irq_exit+0x74/0xd4) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.597097] [<42120f20>] (irq_exit) from [<42165810>] (__handle_domain_irq+0x90/0xb4) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.604129] [<42165810>] (__handle_domain_irq) from [<423ddc40>] (gic_handle_irq+0x58/0x90) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.612027] [<423ddc40>] (gic_handle_irq) from [<42101a78>] (__irq_svc+0x58/0x8c) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.620184] Exception stack(0xbe4c3f60 to 0xbe4c3fa8) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.627822] 3f60: 00000000 00014fd8 bedb2a34 42118140 00000000 ffffc000 00000000 42b06e48 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.632859] 3f80: 00000008 42b06ea8 42a41470 00000000 42b91730 be4c3fb0 42108b38 42108b3c 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.641017] 3fa0: 60000013 ffffffff 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.649177] [<42101a78>] (__irq_svc) from [<42108b3c>] (arch_cpu_idle+0x2c/0x38) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.652479] [<42108b3c>] (arch_cpu_idle) from [<42145038>] (do_idle+0xf8/0x274) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.660116] [<42145038>] (do_idle) from [<4214545c>] (cpu_startup_entry+0x18/0x1c) 2026-03-13T13:34:28+00:00 router.lan kernel: [ 40.667147] [<4214545c>] (cpu_startup_entry) from [<42102390>] (__enable_mmu+0x0/0x30)PR60X - Domain-Based Filtering in Firewall Traffic Rules
Dear Netgear Team, currently, the Traffic Rules feature only allows filtering based on IP addresses, ports, and services. While this works for many use cases, it is not sufficient for scenarios where modern services rely on dynamically changing IP addresses (e.g., CDNs or cloud-based endpoints). It would be highly beneficial to have the ability to define firewall rules based on domain names (FQDN). Ideally, this feature could include: support for FQDN in Traffic Rules automatic DNS resolution and IP updates in the background optional wildcard support (e.g., *.example.com) This enhancement would greatly improve real-world usability, especially in environments with IoT devices and cloud services. Thank you for considering this request. Best regards, Alex
VPNG01L licence key activation
could anyone help me in resetting my licence key for activation? Although deinstalled on old laptop I can't activate licence on new one. I have no access to the old system as hard disc is wiped. After countless and friutless hours running in circles at Netgear Support pages you are my last hope... regards BrunoFVS318v3 slow speeds as Router fast as Hub what settings can I change (internally on netgear)
My FVS 318 v3 is only 7 & 8 Mbps as a Router but it speeds up to (94 & 67 Mbps when modem cable is moved from WAN to a LAN port. what inside the Netgear is slowing down speed. No Port Fwrd, no Rules, no VPN, just basic AUTO setup.