root@DD-WRT:/jffs# ipkg
-sh: ipkg: not found
root@DD-WRT:/jffs# opkg
-sh: opkg: not found
root@DD-WRT:/jffs#
Does there some docs of ddwrt-v3.0 ipkg or opkg description? I can't find in wiki. Thx.
IPKG is not supported anymore and opkg is available on my builds after you ran the preperation script "bootstrap" _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
root@DD-WRT:/jffs# ipkg
-sh: ipkg: not found
root@DD-WRT:/jffs# opkg
-sh: opkg: not found
root@DD-WRT:/jffs#
Does there some docs of ddwrt-v3.0 ipkg or opkg description? I can't find in wiki. Thx.
IPKG is not supported anymore and opkg is available on my builds after you ran the preperation script "bootstrap"
Got a way to run bootstrap:
mkdir /jffs/opt
mount -o bind /jffs/opt /opt
Then I got this;
root@DD-WRT:/jffs# bootstrap
Bootstrap is checking prerequisites...
USB automounter is enabled.
Found a valid partition: /opt.
Proceed with download and install of opkg? (y/n) [default=n]:
y
Connecting to www.desipro.de (212.227.247.157:80)
wget: server returned error: HTTP/1.1 403 Forbidden
Connecting to www.desipro.de (212.227.247.157:80)
wget: server returned error: HTTP/1.1 403 Forbidden
Error opening signature file opkg.ipk.sig
1995932864:error:02001002:lib(2):func(1):reason(2):NA:0:fopen('opkg.ipk.sig','rb')
1995932864:error:2006D080:lib(32):func(109):reason(128):NA:0:
Error: Signature does not match.
After many, many months of waiting. My R8500 is finally working with the latest firmware by <Kong>
DD-WRT Kong Mod for NETGEAR R8500 (2017-11-01 CHK)
Thank you so much Kong, hope future updates also work for mine.
Officially the only working versions for mine are:
K3_R8500_17-Feb-2016.chk
Nov-01-2017-dd-wrt.K3_R8500.chk (KONG)
Posted: Mon Dec 18, 2017 3:23 Post subject: R8500 boot loop MP2 242 12473-02
Probably beating a dead horse but I'll give it one last try. Dreaded boot loop for netgear R8500. tried a number of netgear FW's including earliest version R8500-V1.0.0.28_1.0.15 and most current R8500-V1.0.2.106_1.0.85. All go thru an extended boot loop cycle that does eventually stop. I've also tried the latest BS and K3 DD wwrt versions - the former appears to lock the system up while the latter just loops.
K3 is reported to work on variant -03 but alas i have -02. For grins I've attached the boots for netgear and K3 as well as nvram show results.
A good number of these units are being sold on eBay "as is". I've been successful in recycling improperly flashed routers in the past, so took a chance and bought one for under $50. This R8500 v1 is by far the hottest router I've ever owned and fear it is damaged beyond repair.
Thanks to an old post here, I have the 2.4GHz radio working under firmware V1.0.0.42_1.0.23, but have been unable to get the 5GHz radios to work.
Has anyone had any success fixing these defective units? I don't have a bootlog, but if I remember correctly it almost looks like the PCI-E switch is not being detected or not detecting the 5GHz radios.
A good number of these units are being sold on eBay "as is". I've been successful in recycling improperly flashed routers in the past, so took a chance and bought one for under $50. This R8500 v1 is by far the hottest router I've ever owned and fear it is damaged beyond repair.
Thanks to an old post here, I have the 2.4GHz radio working under firmware V1.0.0.42_1.0.23, but have been unable to get the 5GHz radios to work.
Has anyone had any success fixing these defective units? I don't have a bootlog, but if I remember correctly it almost looks like the PCI-E switch is not being detected or not detecting the 5GHz radios.
I've bought about 5 or 6 in similar condition. Even with serial logs and kong's help, I wasn't able to fix any. _________________ I am far from a guru, I'm barely a novice.
Hey there R8500 users. Any word when or if the Kong builds will fix the issues where the port assignments are not visible in the GUI? For example, Port 5/6 not visible.
Also, any progress on Link Aggregation 802.3ad LACP for the Kong builds? This feature seems to be in the code, but not entirely working in the GUI.
maybe onto something as for the r8500's with reboot isues.. I just flashed the latest March build and what I have noticed is that it reboots when connecting to wifi.. so I tried each radio one at a time to see if it was isolated to just one.. what I found is that connecting to the 2.4G WL1 radio is fine, but when I connect to either of the 5G "WL0,2" it instantlay reboots. Wondering if it was a complete crash or something semi graceful I opened it up and connected to the serial port. Here is what it shows when connecting to one of those 5G radios before a reboot:
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Wed Mar 21, 2018 10:19 Post subject:
@ black6spdz, open up a SVN ticket and report:
http://svn.dd-wrt.com/timeline _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
I've improved cooling by using copper shims directly from cpu/wifi radios to the heatsink. I also noticed there was no screw in the middle.. wondering if this was an assembly problem and could have caused this router "and others?" to everheat befor I got my hands on it. Now it runs 50-55c on all temps but still reboots connecting to the 0 and 2 5G radios. One more issue is the netgear firmware connects at 1Gb to my old laptop's NIC "realtek" but with dd-wrt only at 100Mb. _________________ DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Sat Mar 24, 2018 9:59 Post subject:
@ black6spdz,
This is a known issue in repeater bridge mode.
But as WAPs both 5Ghz Radios should work fine. Are you using it as repeater bridge?
If not, just force the wl0 to higher channels > 144 manually set.
wl2, set it manually to channels < 52
Should work _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
no, with either of the 5 Ghz radios "Wl0,2" in AP mode as SOON as a client attempts to connect it throws that error I posted earlier and reboots. So I even tried using one of the 5G radios in client mode to connect to my main home AP and it does the same, basically and endless reboot loop as soon as it rebboted and reconnected to the AP. I factory reset it and have it working again but I'm scratching my head why everything else works ok "2g radio, USB/NAS functionality, etc". Are the 5G radios/chips just fubar'd? _________________ DD-WRT w/ Superchannel, Ubiquiti RS Pro @800Mhz, Ubiquiti SR71-A a/n,g/n