Joined: 18 Mar 2014 Posts: 12834 Location: Netherlands
Posted: Sat Jan 16, 2021 11:47 Post subject:
brrfpm wrote:
Upgrade: via web UI, TurboQAM missing on Asus AC3200 and the issue I've detailed below.
Reset: no
-------------------------------------------------
I still have the same issue as mentioned before.
Allowed IP's in VPN still has a limit of 1024 chars.
This restricts me from using the UI to fill my allowed IPs range and instead I have to manually do this on the router.
I'm basically compensating for the lack of a "Blocked IPs" or "Non-Allowed IPs" to allow both PBR and DBR tunnels to work hand in hand.
This is basically so: "For this one machine route all traffic through this VPN bar for this one website" and a separate DBR tunnel is in place for that one website for not only the PBR machine but the whole network.
I have a python script to print CIDR addresses covering the whole range of IPs for the whole internet minus the IPs for the DBR websites and the DBR websites defined DNSs. It comes to a total of 1214 chars which is quite small considering what it is.
Because of the arbitrary limit in the router GUI of 1024 I manually have to set it on the router and in a start-up script which is quite annoying.
Upgrade: via web UI, TurboQAM missing on Asus AC3200 and the issue I've detailed below.
Reset: no
-------------------------------------------------
I still have the same issue as mentioned before.
Allowed IP's in VPN still has a limit of 1024 chars.
This restricts me from using the UI to fill my allowed IPs range and instead I have to manually do this on the router.
I'm basically compensating for the lack of a "Blocked IPs" or "Non-Allowed IPs" to allow both PBR and DBR tunnels to work hand in hand.
This is basically so: "For this one machine route all traffic through this VPN bar for this one website" and a separate DBR tunnel is in place for that one website for not only the PBR machine but the whole network.
I have a python script to print CIDR addresses covering the whole range of IPs for the whole internet minus the IPs for the DBR websites and the DBR websites defined DNSs. It comes to a total of 1214 chars which is quite small considering what it is.
Because of the arbitrary limit in the router GUI of 1024 I manually have to set it on the router and in a start-up script which is quite annoying.
Firmware: v3.0-r45454 std (01/15/21)
Router/Version: Netgear R7000 Kernel: Linux 4.4.251 #1836 SMP Fri Jan 15 00:11:49 +07 2021 armv7l
Previous: v3.0-r45420 std (01/13/21)
Mode/Status: AP wired and wireless, Up and running for 27 hours.
Reset: Soft boot before and after upgrade
Temperatures: CPU 57.5 °C / WL0 45.0 °C / WL1 50.2 °C
Issues/Errors: Nothing significant
Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
There is a mysterious "Sysctl" tab in the Administration tab that seems to allow a lot of fine-tuning. I might be tempted to break things.
There is a minor issue with the packet count on wl0.1 and "Connected Clients" stuck at zero. The wl0 and wl1 counts seem correct.
Upload and Download speeds are to ISP spec. Nothing unexpected in the syslog.
Current basic R7000 setup (subject to change of course):
- Static WAN IP
- SFE - On
- STP - On
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 149, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- No custom scripts
- NO: ttraf, Tor, VNC, Zabbix, VPN, Radius, OpenVPN
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Firmware: v3.0-r45454 mega (01/15/21)
Router/Version: ASUS RT-N66U
Kernel: Linux 4.4.251 #6239 Fri Jan 15 18:16:24 +07 2021 mips
Previous: v3.0-r44340 mega (09/10/20)
Mode/Status: Router wired and wireless, Up and running for 1 hours.
Reset: No
Issues/Errors: None so far
Upgrade was fast & smooth. Speedtest still shows similar numbers from before upgrade which are according to the ISP plan.
It's been quite a while since I upgraded; all good! Great work BS and everyone involved in the project.
Firmware: v3.0-r45454 std (01/15/21)
Router/Version: Netgear R8000
Kernel: Linux 4.4.251 #1841 SMP Fri Jan 15 11:04:07 +07 2021 armv7l
Previous: v3.0-r45229 std
Mode/Status: AP wired and wireless (2.4/5GHz)
Reset: None, Soft boot before and after upgrade
Temperatures: CPU 59.1 °C / WL0 46.8 °C / WL1 44.8 °C / WL2 49.3 °C
Issues/Errors: None detected so far
Note: I didn't see anywhere the option to turn on QAM256 for the 2.4Ghz radio. Is this done behind the scenes or am I missing a switch here?
Firmware: DD-WRT v3.0-r45454 std (01/15/21)
Time: 08:28:15 up 1 day, 5:28, load average: 0.07, 0.03, 0.00
Router/Version: Netgear R6300V2
Kernel: Linux 4.4.251 #1836 SMP Fri Jan 15 00:11:49 +07 2021 armv7l
Previous: Factory
CPU Model: Broadcom BCM4708
Mode/Status: Internet router, wifi disabled, OpenVPN in use
Reset: Soft boot before and after upgrade
Temperatures: CPU 57.5 °C / Not available
Issues/Errors: Nothing significant
Device is used as primary Internet router on a cable line. It also runs OpenVPN client as a permanent LAN2LAN VPN connection back to another network. IPv6 is also enabled and IPv6 is in use from the local LAN. Dynamic DNS is also setup. VoIP phones register through this device back to a PBX on the other network.
Posted: Mon Jan 18, 2021 21:34 Post subject: WRT54GSv1
This build also soft bricks my WRT54GS version 1.
Flashing via WebUI all logs look good reboot looks good to my knowledge. Once reboot occurs passes normal network traffic but WebUI unresponsive, no ping response, and no SSH response either. Must recover VIA tftp recovery. Access via physical com port tried issuing download and upgrade commands with no downloads. Wget has no results listed on the CLi. Attached full serial output from first boot with working build through upgraded and reboot with no access.
Firmware: v3.0-r45454 std (01/15/21)
Router/Version: Netgear R8000
Kernel: Linux 4.4.251 #1841 SMP Fri Jan 15 11:04:07 +07 2021 armv7l
Previous: v3.0-r45229 std
Mode/Status: AP wired and wireless (2.4/5GHz)
Reset: None, Soft boot before and after upgrade
Temperatures: CPU 59.1 °C / WL0 46.8 °C / WL1 44.8 °C / WL2 49.3 °C
Issues/Errors: None detected so far
Note: I didn't see anywhere the option to turn on QAM256 for the 2.4Ghz radio. Is this done behind the scenes or am I missing a switch here?
I have tried the experimental driver, reset to factory defaults and rebuilt the settings from scratch. I have found the following issues:
1. the 5GHz radios (wlan0, wlan2) are inoperative (operated correctly with the proprietary driver)
2. Even though I selected UK as the regulatory domain in the UI, the 2.4 GHz radio (wlan1) advertises the domain to be DE (Germany).
Joined: 08 Apr 2017 Posts: 49 Location: Underground lair
Posted: Tue Jan 19, 2021 22:14 Post subject:
Router/Version: Netgear R8000
File/Kernel: r45454/Linux 4.4.251
Previous/Reset: r44715/yes
Mode/Status: Primary gateway/working
Issues/Errors: VAP will not connect wirelessly. Wireless stops working after any change to wireless settings. Have to power cycle to restart. _________________ Routers: Netgear R8000, Linksys E1200v1, E4200, WRT54Gv3, TL-WDR4300v1.7
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r45454 std (01/15/21) (prev. DD-WRT v3.0-r45036 std (12/18/20))
Kernel: Linux 4.4.251 #1836 SMP Fri Jan 15 00:11:49 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: 1d up, ok.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-45454_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r45454 big (01/15/21) (prev. DD-WRT v3.0-r45036 big (12/18/20))
Kernel: Linux 4.4.251 #6235 Fri Jan 15 18:06:31 +07 2021 mips
Mode: Gateway, Wifi disabled, Wireguard Endpoint for external VPS, connected via DHCP WAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: 1d up, ok.
Joined: 16 Mar 2019 Posts: 353 Location: Szczecin, Poland EU
Posted: Tue Jan 19, 2021 22:56 Post subject: New Build - 01/15/2021 - r45454
Router/Version: Netgear WNR3500L v2
File/Kernel: Linux 4.4.251 #6223 Fri Jan 15 17:39:06 +07 2021 mips
Reset: No
Mode: Internet gateway, WIFI AP, Dnsmasq server
Errors: Described below
Status: Working
Uptime: ~100h
I'm updated device via ssh from previously beta of dd-wrt. Generally router works good. I have many warns and errors in logs.
Code:
Jan 1 01:00:16 Myrouter kern.warn kernel: Found a AMD NAND flash with 2048B pages or 128KB blocks; total size 128MB
Jan 1 01:00:16 Myrouter kern.warn kernel: Primary instruction cache 32kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
Jan 1 01:00:16 Myrouter kern.warn kernel: Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Jan 1 01:00:16 Myrouter kern.warn kernel: PCI: no core
Jan 1 01:00:16 Myrouter kern.warn kernel: PCI: no core
Jan 1 01:00:16 Myrouter kern.warn kernel: PCI: Fixing up bridge
Jan 1 01:00:16 Myrouter kern.warn kernel: PCI: Fixing up bus 0
Jan 1 01:00:16 Myrouter kern.err kernel: pflash: found no supported devices
Jan 1 01:00:16 Myrouter kern.warn kernel: ERROR: Unknown flash, device_id:0x00
Jan 1 01:00:16 Myrouter kern.err kernel: bcmsflash: found no supported devices
Jan 1 01:00:16 Myrouter kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 01:00:16 Myrouter kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x500000
Jan 1 01:00:16 Myrouter kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 01:00:16 Myrouter kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 01:00:16 Myrouter kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 01:00:16 Myrouter kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: et_txq_thresh set to 0xce4
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 01:00:16 Myrouter kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 01:00:16 Myrouter kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 01:01:58 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 15 20:00:20 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 16 11:14:52 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 16 12:20:46 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 16 14:36:24 Myrouter daemon.err process_monitor[2225]: cyclic NTP Update failed (servers 194.146.251.100)
Jan 16 15:04:44 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 16 17:24:08 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 16 20:59:26 Myrouter daemon.err httpd[1559]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 16 21:05:18 Myrouter daemon.err httpd[10392]: httpd : Request Error Code 408: Unexpected connection close in intitial request
Jan 16 22:05:53 Myrouter daemon.err httpd[12381]: httpd : Request Error Code 408: Unexpected connection close in intitial request
Jan 16 22:05:53 Myrouter daemon.err httpd[12381]: httpd : Request Error Code 408: Unexpected connection close in intitial request
Jan 16 22:05:53 Myrouter daemon.err httpd[12381]: httpd : Request Error Code 408: Unexpected connection close in intitial request
Jan 18 10:28:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 10:31:07 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 10:34:10 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 11:28:32 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:11:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:14:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:59:16 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:59:28 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:59:38 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 17:59:52 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:01 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:02 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:16 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:57 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:00:58 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:06 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:14 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:22 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:30 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:38 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:01:56 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:02:04 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:02:12 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:02:24 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:02:32 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:02:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:03:29 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:05:54 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:06:11 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:06:41 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:06:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:08:24 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:10:27 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 18 18:11:01 Myrouter daemon.err httpd[12775]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 18 21:23:43 Myrouter daemon.err httpd[12775]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 19 11:58:27 Myrouter daemon.err httpd[12775]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 19 12:14:03 Myrouter daemon.err httpd[31212]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 19 13:35:44 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 13:38:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:09:44 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:11:41 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:12:15 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:37:16 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:37:17 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:38:13 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:38:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:38:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:39:27 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:42:05 Myrouter daemon.err httpd[32425]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 19 14:42:30 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:44:34 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:47:37 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:50:39 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:53:42 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:56:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:59:48 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 14:59:49 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:15:23 Myrouter daemon.err process_monitor[32415]: cyclic NTP Update failed (servers 194.146.251.100)
Jan 19 15:35:29 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:38:10 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:41:14 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:44:17 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:45:35 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:45:46 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:46:12 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:47:24 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:47:35 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:47:52 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:48:20 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 15:51:22 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:13:05 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:13:50 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:14:47 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:14:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:15:04 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:15:40 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:16:13 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:16:25 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:17:00 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:17:10 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:50:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:51:08 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:51:46 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:53:12 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:55:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 16:58:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:51:38 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:52:33 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:52:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:53:06 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:53:26 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:53:46 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:53:57 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 18:54:19 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 19:33:21 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:22:42 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:22:50 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:23:01 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:23:11 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:23:39 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:23:50 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:07 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:15 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:23 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:31 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:39 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:47 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:24:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:08 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:18 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:26 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:34 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:43 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:51 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:25:59 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:08 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:16 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:24 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:36 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:26:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:27:01 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:30:04 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:33:07 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:36:12 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:39:15 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:42:18 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:45:31 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:45:39 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:45:47 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:45:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:03 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:11 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:19 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:28 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:38 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:46:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:01 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:11 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:19 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:30 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:38 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:47 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:47:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:48:03 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:48:11 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:48:19 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:48:55 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:49:23 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:49:31 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:49:45 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:49:53 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:50:28 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:51:09 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:51:31 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:51:39 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:51:56 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:52:08 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 20:55:10 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 21:35:33 Myrouter kern.warn kernel: br0: received packet on eth1 with own address as source address
Jan 19 23:36:33 Myrouter daemon.err httpd[32425]: httpd : Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Posted: Sun Jan 24, 2021 6:58 Post subject: Re: WRT54GSv1
Veritech wrote:
This build also soft bricks my WRT54GS version 1.
Flashing via WebUI all logs look good reboot looks good to my knowledge. Once reboot occurs passes normal network traffic but WebUI unresponsive, no ping response, and no SSH response either. Must recover VIA tftp recovery. Access via physical com port tried issuing download and upgrade commands with no downloads. Wget has no results listed on the CLi. Attached full serial output from first boot with working build through upgraded and reboot with no access.