Joined: 08 May 2018 Posts: 7443 Location: Texas, USA
Posted: Sun May 24, 2020 18:04 Post subject:
Ok, I guess I have to repeat: Did you try power cycling the cable modem? Turning it off for a few minutes, turning it back on, *then* powering up your router with it connected?
I don’t know if I understand you correctly.
I turned off my DIR-320 and, after waiting a bit, turned it on. I did it. I do not have access to the equipment of the provider. I am connected to them using DOCSIS technology. I suppose that they have a modem installed on the trunk cable ARRIS, then there is a switch with a firewall DES-1008A, and then the twisted-pair subscribers are connected, which I belong to. I do the same with r36527, the WAN gets IP instantly.
Sorry for my English.
Ok, are you in a dormitory or apartment building served by a common Internet provider through a network or what is your arrangement? The Arris has to be power cycled or you need to figure out why it is rejecting your router. Perhaps if you had reset in the process of upgrading, the system got your original MAC and will only recognize that or some such. FYI, a DES-1008A is not anything other than a dumb (unmanaged) switch. It has no firmware, no firewall, nothing.
Yes, maybe I was wrong with DES-1008A. But why with another firmware r36527 I do not have to do anything. Only set MAC cloning, apply, turn off the power, turn on the power. And he instantly gets an IP. Maybe in the new firmware I need something else to configure or enable?
But I noticed one feature. If after r36527 I do not reset, then DIR-320 continues to receive IP. I tried many different versions, but only r36527 starts after reset.
Hi, in an attempt to get a number of highly supported secure simple wifi repeater bridges, I bought some wrt54g v4s off ebay. As I want them to be secure, I attempted to flash 43217 instead of the iconic 14929 from the peacock thread. My plan, based on peacock thread, was to flash the mini trailed build, and then the mini generic, or std generic. Not to concerned about fixing a bricked router. I am concerned that 43217 should work on a wrt54g v4, and there's nothing in this build such that it wouldn't work as a repeater bridge, and that it will have all current CVE's. i.e. I just want to make sure before I spend all this time, that its not a known bug / issue that wifi doesn't work on these builds or on this router, etc.
Router/Version: Wrt-54g v4
Previous/Reset: Linksys Firmware
Mode/Status: default / bricked -> working ?
- It appears to be working with the first flash from stock firmware trailing mini build. Peacock thread says I should now flash to mini generic, or std generic. Given what I experienced below, should I do that? Or should I flash to 14929 mini trailing build, then 14929 mini generic, then to 43217 mini / std generic ?
- Following the peacock thread, I used the trailing mini build. On the linksys firmware gui, I uploaded the firmware and after a couple of minutes, I got failure.
- I did a hard reset, ping ttl=64, and got the ddwrt screen, but its asking for a username and password instead of the password reset screen I was expecting. I used u:root, and p:admin, did not work.
- I power cycled, did a hard reset again, ping ttl=100, and couldn't load gui.
- I power cycled, did a hard reset again, ping "network unreachable", and couldn't load gui.
- Gave up and left.
- Just turned it on to check something, got ttl=64, loaded the gui, and was prompted to enter username, and change password as expected. However, it says DD-WRT v3.0-r43217 instead of DD-WRT v2.4-r43217 as I would have expected.
- Peacock thread says I should now flash to mini generic, or std generic. Given what I experienced above, should I do that? Or should I flash to 14929 mini trailing build, then 14929 mini generic, then to 43217 mini / std generic ? I'm terrified, now that its working, that I do whatevers needed to clear out anything bad that might be left behind.
Router/Version: Wrt-54g v4
Previous/Reset: Linksys Firmware
Mode/Status: default / bricked (my fault)
- This issue is just an fyi, I assume it is borked, and I assume it is borked because of what I did. I got the router for $10 on ebay, so I'm not worried. Just wanted to mention it since, it seemed to really go downhill when I flashed the generic build on top of the trailed build, but that could have no correlation, and simply be the after effects of my idiocy previously with the mega flash.
- Following the peacock thread, I used the trailing mini build on the linksys firmware gui. Everything went smoothly, following the wiki, and I eventually got to the screen asking me to set username, and password (after all the resets).
- I then had a brain fart, and attempted to flash a mega bin like an idiot.
- Somehow I did not brick it at this stage or at least I do not believe I did, as after a hard reset, it let me login.
- Thinking I had saved myself, and the router simply didn't let me flash, I attempted to flash mini generic. Now I have blinking power button, ping network unreachable, and no gui.
Router/Version: Asus RT-AC68U H/W Version A2
Kernel: Linux 4.4.224 #192 SMP Fri May 22 08:05:47 +04 2020 armv7l
Status: On Firmware: DD-WRT v3.0-r43217 std (05/22/20), router keeps rebooting at random times
Router: (Off Site 2) Netgear R700
-DHCP WAN (Gateway)
-ISP IPv6 - Prefix Delegation for 4xVLANs via Dnsmasq
-2x Static Leases
-6xVLANs + 6xBridges
-DDNS - Custom Script
-Entware DNSCrypt-Proxy V2 - IPv4/v6 4xQuad9 Servers
-YAMon3.4.6 w/Entware's ip-full for IPv6
-SSH -Custom Port & Key
-NTP server left blank
-QoS - Disabled
-TCP Congestion - bbr
-USB w/32GB USB3 Thumb Drive
-Custom Startup,Shutdown,Firewall Scripts
Firmware: DD-WRT v3.0-r43217 std (05/22/20) [from: DD-WRT KONGAC 39855M]
Linux Rel: Linux 4.4.224 #192 SMP Fri May 22 [from: Linux 4.4.xxx]
WiFi Firmware: version 220.127.116.11 (r524987)
Reset: YES, Router swap (from a spare R7000 full reset and manual config)
Status & Uptime: Working over 10 hours, Working
Thank-you BrianSlyer for your Great Work and everyone else who makes DD-WRT Great on the Forum! _________________ Home Network on Telus PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r44483 Std
R7000 - Wired ISP 4K IPTV Gateway - DDWRT r44483 Std
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r44483 Std
WRT610Nv1 - Client Bridge - DDWRT r33679 Mega K2.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r44483 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Firmware: v3.0-r43217 std (05/22/20)
Router/Version: Netgear R7000 Kernel: Linux 4.4.224 #192 SMP Fri May 22 08:05:47 +04 2020 armv7l
Previous: v3.0-r43192 std (05/19/20)
Mode/Status: AP wired and wireless, Up and running for 4 days
Reset: Soft boot before and after upgrade
Temperatures: CPU 60.8 °C / WL0 46.3 °C / WL1 51.4 °C
Issues/Errors: Nothing significant
Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
The minor issue with the zero packet count on wl0 has returned, and "Connected Clients" is stuck at zero. The wl1 counts seem correct.
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 NG-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, VNC, Zabbix, VPN, Radius
- NO: UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware _________________ Netgear R7000: v3.0-r44809 std (11/15/20)
EdgeRouter-X: EdgeOS v2.0.8