Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Wed Nov 06, 2019 2:42 Post subject:
mrjcd wrote:
kernel-panic69 wrote:
Which paper clips do you use, because I know the size of the holes on Linksys and what does and don't fit on most of the connectors.
just a regular standard paperclip (not a big one)
straighten it and clip it off down to a good size, don't need it too long
fits rather loosely in header holes --- that's why I pull all three to the side and tape
I'm thinking I may do the mod so I don't have to have the case open. Stereo 1/8" (3.5mm) phone jack wired to the header and make up the external cable.
Drek wrote:
This is what separates the true geeks, from the wannabes, the selection of paper clips.
You guys are nuts. I love it, but you're all nuts...
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Wed Nov 06, 2019 2:52 Post subject:
dragonC wrote:
kernel-panic69 wrote:
Were the samba configuration variables added to a .conf or nvram? Or are they hard-coded? Hmmm....
I run custom smb.conf to get my own setup. basically copy the generated one, tweak a few parameters and launch it on a startup script. I added max/min protocol there.
I am not 100% sure this release has the v3 protocol, I would have to look. BUT, I thought some of this may have been hard-coded and not in the .conf, so I would have to check into that. As always, it's an ever-evolving thing. And I don't know if it's ALL devices inclusive, either. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Router/Version: Linksys WRT54G
Mode: v4
File: dd-wrt.v24_mini_wrt54g 11-04-2019-r41459.bin and dd-wrt.v24_mini_generic 11-04-2019-r41459.bin tested.
Kernel: Linux 2.4.37 #56878 Mon Nov 4 06:07:33 +04 2019 mips
Status: Radio OFF.
Previous working build used was 05-15-2019-r39800
Needed to have VAP working so went with this build.
VAP does not work when setting the WPA2 auth. Works without AUTH
Installed as far as 01-07-2018-r34411 dd-wrt.v24_mini_wrt54g.bin radio still OFF.
Code:
DD-WRT v3.0-r34411 mini (c) 2018 NewMedia-NET GmbH
Release: 01/08/18
root@DD-WRT:~# dmesg
CPU ProcId is: 0x00029008, options: 0x0000004d
Linux version 2.4.37 (root@linux) (gcc version 3.4.6 (OpenWrt-2.0)) #47772 Mon Jan 8 00:41:10 CET 2018
Setting the PFC to its default value
Determined physical RAM map:
memory: 01000000 @ 00000000 (usable)
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200
CPU: BCM5352 rev 0 at 200 MHz
Using 100.000 MHz high precision timer.
Calibrating delay loop... 199.47 BogoMIPS
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: no core
PCI: Fixing up bus 0
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 3) is a 16550A
PCI: Setting latency timer of device 00:01.0 to 64
PPPoL2TP kernel driver, V0.13
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
Physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1000000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1400000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1800000 for the chip at 0x0
Physically mapped flash: Found an alias at 0x1c00000 for the chip at 0x0
Amd/Fujitsu Extended Query Table v3.3 at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Flash device: 0x400000 at 0x1c000000
bootloader size: 262144
Physically mapped flash: Filesystem type: squashfs, size=0x2144a0
partition size = 2211840
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x003f0000 : "linux"
0x00124000-0x00340000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x003f0000-0x00400000 : "nvram"
0x00340000-0x003f0000 : "ddwrt"
sflash not supported on this router
Initializing Cryptographic API
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
ip_conntrack version 2.1 (512 buckets, 4096 max) - 336 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_random match loaded
netfilter PSD loaded - (c) astaro AG
ipt_osf: Startng OS fingerprint matching module.
ipt_IPV4OPTSSTRIP loaded
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
roboswitch: Probing device eth0: found a 5325!
device br0 entered promiscuous mode
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
device vlan1 entered promiscuous mode
vlan1: Setting MAC address to 00 1d 7e dc 23 f5.
vlan1: dev_set_promiscuity(master, 1)
vlan1: dev_set_allmulti(master, 1)
vlan1: dev_set_promiscuity(master, -1)
device vlan1 left promiscuous mode
vlan1: dev_set_allmulti(master, -1)
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: dev_set_promiscuity(master, -1)
device eth0 left promiscuous mode
device vlan0 left promiscuous mode
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
device br0 entered promiscuous mode
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan0: del 01:00:5e:00:00:01 mcast address from master interface
vlan0: add 01:00:5e:00:00:01 mcast address to master interface
vlan0: dev_set_promiscuity(master, 1)
device eth0 entered promiscuous mode
device vlan0 entered promiscuous mode
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
vlan1: dev_set_allmulti(master, 1)
vlan1: dev_set_promiscuity(master, 1)
device vlan1 entered promiscuous mode
vlan1: del 01:00:5e:00:00:01 mcast address from vlan interface
vlan1: del 01:00:5e:00:00:01 mcast address from master interface
vlan1: Setting MAC address to 00 1d 7e dc 23 f5.
vlan1: add 01:00:5e:00:00:01 mcast address to master interface
vlan1: dev_set_promiscuity(master, -1)
device vlan1 left promiscuous mode
vlan1: dev_set_allmulti(master, -1)
did factory reset, nvram erase, no good.
Will follow tommorow. Advice if any ideas. Thanks.
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Wed Nov 06, 2019 6:40 Post subject:
From approximately mid 2018 VAP's on Broadcom units are problematic, you cannot connect or do not get an IP address. There are workarounds :
1) When VAP is not working at boot; workaround startup command Administration/Commands, Save as Startup:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
2) Alternative way to get VAP working: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=317181
3) An other user reports the following workaround (save as startup):
sleep 4; stopservice cron; stopservice wlconf; wlconf eth1 up; wlconf eth2 up; startservice cron;
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=319412
4)This one is from @Redhawk (guaranteed to work ):
sleep 20; stopservice nas; wlconf eth1 down; wlconf eth2 down; wlconf eth1 up; wlconf eth2 up; startservice nas; logger "VAP workaround executed"; _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Router/Version: Linksys WRT54G
Mode: v4
File: dd-wrt.v24_mini_wrt54g 11-04-2019-r41459.bin and dd-wrt.v24_mini_generic 11-04-2019-r41459.bin tested.
Kernel: Linux 2.4.37 #56878 Mon Nov 4 06:07:33 +04 2019 mips
Status: Radio OFF.
Previous working build used was 05-15-2019-r39800
Needed to have VAP working so went with this build.
VAP does not work when setting the WPA2 auth. Works without AUTH
Installed as far as 01-07-2018-r34411 dd-wrt.v24_mini_wrt54g.bin radio still OFF.
did factory reset, nvram erase, no good.
Will follow tommorow. Advice if any ideas. Thanks.
Was able to fix "Radio is OFF" by pushing dd-wrt.v24_mini_wrt54g 01-07-2018-r34411.bin, HARD 30/30/30.
dd-wrt.v24_mini_wrt54g 10-30-2019-r41418.bin Radio OK (haven't tested the rest).
Pushed dd-wrt.v24_mini_wrt54g 11-04-2019-r41459.bin and Radio was still ON.
Was able to fix "Radio is OFF" by pushing dd-wrt.v24_mini_wrt54g 01-07-2018-r34411.bin, HARD 30/30/30.
Just a friendly heads up, apparently if you 30/30/30 a Broadcom router you risk bricking it permanently. The procedure for resetting a Broadcom router is to turn the power on and push and hold the reset for 10 seconds or so. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
Was able to fix "Radio is OFF" by pushing dd-wrt.v24_mini_wrt54g 01-07-2018-r34411.bin, HARD 30/30/30.
Just a friendly heads up, apparently if you 30/30/30 a Broadcom router you risk bricking it permanently. The procedure for resetting a Broadcom router is to turn the power on and push and hold the reset for 10 seconds or so.
I believe you ment to say "ARM" routers
While yes ARM's are Broadcom.....
Most Broadcom's are NOT ARM....
At least none of the older verities like any of the wrt54g series
Also while not saying that 30/30/30 is not "potentially" harmful when performed on an ARM based router
I've never seen anyone actually report of any damages ever happening that was directly resulted from doing so..
Let alone a "permanent" brick?
¯\_(ツ)_/¯ _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
At least none of the older verities like any of the wrt54g series
Also while not saying that 30/30/30 is not "potentially" harmful when performed on an ARM based router
I've never seen anyone actually report of any damages ever happening that was directly resulted from doing so..
Let alone a "permanent" brick?
¯\_(ツ)_/¯
Thanks for the clarification. I got "yelled at" on these forums for saying I had 30/30/30'd my Broadcom router, and thought it was more serious than that. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Wed Nov 06, 2019 21:33 Post subject:
And it was probably either me or Malachi that yelled at you, because you're not s'posed to do it. All you need is 10 seconds on (Broadcom) ARM devices. Even on factory stock firmware.
Also, Qualcomm IPQ (Krait-based) processors are ARM. So are Marvell. And those two are also the reason why you DON'T do a 30-30-30 on ARM. Just to clarify. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Router Model / Version: Netgear Nighthawk R7000
File: netgear-r7000-webflash.bin
Reset: No
Mode: Gateway / AP - QoS (HFSC+CAKE)
Uptime: 0:10
Status: Bricked
Issues / Errors: Upon flashing, I set up the QoS with base settings of HFSC + CAKE and set up the password for wifi. After reboot I couldn't connect to both the wifi and ethernet anymore.
I'm not sure what the kernel is or the last build I was on. I tried to do a reset but the button doesn't seem to do anything. I held it for 10 seconds upon boot and it still had the same SSID and refused any connection. I also tried to connect to it using USB to TTL, but I'm not getting any output on boot. Not sure what else I can do.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Thu Nov 07, 2019 2:52 Post subject:
Malachi wrote:
Wasn’t me. I don’t yell at the 30/30/30 reset anymore.
Then it was probably me. Because 99 times out of 100, when someone with an ARM device comes on the forum saying they have problems and they read the Peacock thread and all this other stuff but nothing that says not to do it, the problems are because they did a 30-30-30. I could explain why it's bad, but I have no "glue" lol _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Thu Nov 07, 2019 2:54 Post subject:
Takaani wrote:
Router Model / Version: Netgear Nighthawk R7000
File: netgear-r7000-webflash.bin
Reset: No
Mode: Gateway / AP - QoS (HFSC+CAKE)
Uptime: 0:10
Status: Bricked
Issues / Errors: Upon flashing, I set up the QoS with base settings of HFSC + CAKE and set up the password for wifi. After reboot I couldn't connect to both the wifi and ethernet anymore.
I'm not sure what the kernel is or the last build I was on. I tried to do a reset but the button doesn't seem to do anything. I held it for 10 seconds upon boot and it still had the same SSID and refused any connection. I also tried to connect to it using USB to TTL, but I'm not getting any output on boot. Not sure what else I can do.
You will most likely need to use nmrpflash to tftp flash it back to an older build or factory firmware, but I don't see why this one bricked your router. Did the light all the way on the left turn amber before you let go of the reset? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
You will most likely need to use nmrpflash to tftp flash it back to an older build or factory firmware, but I don't see why this one bricked your router. Did the light all the way on the left turn amber before you let go of the reset?
No I let go before the light went amber. I can also try to do it after it goes amber unless that's the wrong way to do it.
Edit: Just tried after it turned amber and still the same result. I'm going to try nmrpflash once I figure out how to use it.
