Belkin Play Max F7D4301v1 now partially supported

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... , 25, 26, 27  Next
Author Message
maczet
DD-WRT Novice


Joined: 31 Jan 2017
Posts: 2

PostPosted: Thu Feb 02, 2017 9:29    Post subject: Reply with quote
I try:
ftp://ftp.dd-wrt.com/betas/2017/02-01-2017-r31221/broadcom_K3X/dd-wrt.v24-31221_NEWD-2_K3.x_mega.bin

and it work ok.
Sponsor
jenom
DD-WRT Novice


Joined: 29 Jun 2011
Posts: 29

PostPosted: Thu Feb 09, 2017 15:11    Post subject: Reply with quote
What router do you have? F7D8301 ?

There are Belkin F7D models listed: (except the 4301/8301)
3301
3302
4302
7301
7302
8302

Did you try any of those?

How did you flash it, step by step ?

Both radio works?

Both USB detected & works?

Thanks.
jenom
DD-WRT Novice


Joined: 29 Jun 2011
Posts: 29

PostPosted: Fri Feb 10, 2017 0:33    Post subject: Belkin F7D8301 Reply with quote
I went ahead and tried the latest R31277.
Started with K26 mini from CFE prompt, next K26 mega, and finally K3x mega.

If anybody interested , here are the problem messages from terminal output on K3X mega :

startup nvram driver
found nvram
found cfe nvram
check if nvram copy is required CFE Size is 32768
nvram copy magic is 48534C46
max nvram space = 65536
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 296K (80626000 - 80670000)
start service
starting Architecture code for broadcom
udevtrigger[748]: parse_config_file: can't open '/etc/udev/udev.conf' as config file: No such file or directory
boardnum 12345
boardtype 0xd4cf
boardrev 0x1204
nvram invalid, erase
Booting device: Belkin F7D4301 / F7D8301 v1
roboswitch: Probing device 'eth0'
roboswitch: trying a 53115! at eth0
roboswitch: found a 53115! at eth0
emf: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
[USB] checking...
/etc/preinit: line 44: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexis tent directory
/etc/preinit: line 44: can't create /proc/sys/net/ipv4/ip_conntrack_max: nonexis tent directory
removing lockfile
device br0 entered promiscuous mode
br0: Invalid argument
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
br0: Invalid argument
eth1: Not supported
base addr .......I blanked it out !!!
local bit addr ..I blanked it out !!!
eth1: Invalid argument
eth1: Not supported
eth1: Operation not permitted
nbw = 20
channel 6, val 20
0, 1000, 0, 6
spec 1006
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
eth1: Not supported
enable bss eth1 0 (0)
wl: Unsupported
device eth1 entered promiscuous mode
br0: Invalid argument
eth2: Not supported
base addr ................I blanked it out !!!
local bit addr ...........I blanked it out !!!
eth2: Invalid argument
eth2: Not supported
eth2: Operation not permitted
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
enable bss eth2 0 (0)
wl: Unsupported
device eth2 entered promiscuous mode
br0: port 3(eth2) entered forwarding state
br0: port 3(eth2) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
br0: port 1(vlan1) entered forwarding state
device br0 left promiscuous mode
device br0 entered promiscuous mode
device br0 left promiscuous mode
function start_hwmon not found
cannot open /proc/irq/163/smp_affinity
cannot open /proc/irq/169/smp_affinity
device vlan2 entered promiscuous mode
cannot open /proc/sys/net/ipv4/conf/br0/loop
br0: port 3(eth2) entered forwarding state
br0: port 2(eth1) entered forwarding state
br0: port 1(vlan1) entered forwarding state

It looks like, this needs plenty of more work !
jenom
DD-WRT Novice


Joined: 29 Jun 2011
Posts: 29

PostPosted: Fri Feb 10, 2017 2:00    Post subject: Belkin F7D8301 Reply with quote
went back to a 2014 FW from KONG
installed fine, everything works with some delays when on webpage try to save and apply settings
when I looked at terminal, the same messages showed up about the connected eth1 or eth2 ports:


root@DD-WRT:~# gethostbyname: Success
gethostbyname: Success
[APPLY] Wireless_Basic (null) (null)
submit_button=[Wireless_Basic] submit_type=[save]
name=[Wireless_Basic] type=[save] service=[wireless] sleep=[1] action=[5]
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
nvram lock, waiting....
nvram lock, waiting....
nvram lock, waiting....
gethostbyname: Success
[APPLY] Wireless_Basic (null) (null)
submit_button=[Wireless_Basic] submit_type=[save]
name=[Wireless_Basic] type=[save] service=[wireless] sleep=[1] action=[5]
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
nvram lock, waiting....
nvram lock, waiting....
nvram lock, waiting....
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
bridge br0 is still up; can't delete it
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
eth1: Invalid argument
nbw = 20
eth1: Invalid argument
eth1: Invalid argument
eth1: Operation not supported
eth1: Operation not supported
eth2: Operation not supported
wl1.1: No such device
wl1.2: No such device
wl1.3: No such device
eth2: Operation not permitted
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Operation not supported
eth2: Operation not supported
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
device br0 already exists; can't create bridge with the same name
br0: Invalid argument
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
br0: Invalid argument
eth1: Operation not supported
wl0.1: No such device
wl0.2: No such device
wl0.3: No such device
eth1: Operation not permitted
eth1: Invalid argument
nbw = 20
eth1: Invalid argument
eth1: Invalid argument
eth1: Operation not supported
eth1: Operation not supported
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: Invalid argument
eth2: Operation not supported
wl1.1: No such device
wl1.2: No such device
wl1.3: No such device

So this problem exist for a very long time !
here is dmesg:


root@DD-WRT:~#
root@DD-WRT:~# dmesg
Linux version 2.6.24.111 (bluebat@linux-vm-os64.site) (gcc version 4.1.2) #616 Sat Jun 7 21:37:12 CEST 2014
CPU revision is: 00019740
Determined physical RAM map:
memory: 04000000 @ 00000000 (usable)
Entering add_active_range(0, 0, 16384) 0 entries of 256 used
Zone PFN ranges:
Normal 0 -> 16384
HighMem 16384 -> 16384
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 16384
On node 0 totalpages: 16384
Normal zone: 0 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 16384 pages, LIFO batch:3
HighMem zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 16384
Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 512 (order: 9, 2048 bytes)
CPU: BCM4716 rev 1 at 453 MHz
Using 226.500 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 58628k/65536k available (3545k kernel code, 6848k reserved, 1374k data, 188k init, 0k highmem)
Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Generic PHY: Registered new driver
PCI: Using membase 8000000
PCI: Initializing host
PCI: Reset RC
PCI: no core
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Fixing up bridge
PCI: Setting latency timer of device 0000:01:00.1 to 64
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
F7D4301v1 GPIO Init
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
squashfs: version 3.0 (2006/03/15) Phillip Lougher
io scheduler noop registered
io scheduler deadline registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = Cool is a 16550A
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
et_module_init: passivemode set to 0x0
PCI: Setting latency timer of device 0000:00:02.0 to 64
VID 0 is set in nvram, Ignoring
eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.9
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:01:01.0 to 64
Physically mapped flash: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x00007f Chip ID 0x0000cb
Physically mapped flash: Found an alias at 0x800000 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 0x1800000 for the chip at 0x0
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x800000 at 0x1c000000
bootloader size: 196608
nvram size: 32768
Physically mapped flash: Filesystem type: squashfs, size=0x5b7e01
partition size = 6021120
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00030000 : "cfe"
0x00030000-0x007f0000 : "linux"
0x00192000-0x00750000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x007f0000-0x00800000 : "nvram"
0x00750000-0x007f0000 : "ddwrt"
Found a 0MB serial flash
sflash: found no supported devices
Broadcom Watchdog Timer: 0.07 initialized.
u32 classifier
Performance counters on
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
ctnetlink v0.93: registering with nfnetlink.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
TCP bic registered
TCP cubic registered
TCP westwood registered
TCP highspeed registered
TCP hybla registered
TCP htcp registered
TCP vegas registered
TCP scalable registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Welcome to PF_RING 3.2.1
(C) 2004-06 L.Deri <deri@ntop.org>
NET: Registered protocol family 27
PF_RING: bucket length 128 bytes
PF_RING: ring slots 4096
PF_RING: sample rate 1 [1=no sampling]
PF_RING: capture TX No [RX only]
PF_RING: transparent mode Yes
PF_RING initialized correctly.
PF_RING: registered /proc/net/pf_ring/
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
_nvram_init(void *sih)
_nvram_init(void *sih) calling nvram_rehash
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 188k freed
roboswitch: Probing device eth0: found a 53115!
br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
device vlan1 entered promiscuous mode
device eth0 entered promiscuous mode
device eth1 entered promiscuous mode
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: port 2(eth1) entering learning state
br0: port 1(vlan1) entering learning state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
device vlan2 entered promiscuous mode
device vlan2 left promiscuous mode
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
_nvram_commit(struct nvram_header *header)
nvram_rehash calling nvram_free
nvram_free freed 257 elements
nvram_rehash
nvram_rehash done.
device vlan1 left promiscuous mode
br0: port 1(vlan1) entering disabled state
device eth1 left promiscuous mode
br0: port 2(eth1) entering disabled state
device eth2 left promiscuous mode
br0: port 3(eth2) entering disabled state
device vlan1 entered promiscuous mode
br0: port 1(vlan1) entering learning state
device eth1 entered promiscuous mode
br0: port 2(eth1) entering learning state
br0: topology change detected, propagating
br0: port 1(vlan1) entering forwarding state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
device eth2 entered promiscuous mode
br0: port 3(eth2) entering learning state
br0: topology change detected, propagating
br0: port 3(eth2) entering forwarding state
root@DD-WRT:~# gethostbyname: Success
gethostbyname: Success
gethostbyname: Success
gti
DD-WRT Novice


Joined: 11 Feb 2016
Posts: 9

PostPosted: Fri Oct 27, 2017 0:27    Post subject: Re: fixed Reply with quote
speakxj7 wrote:
testerddwrt wrote:
speakxj7 wrote:
got recent k3.x working [completely] from scratch (factory reset in dd-wrt) (including routing, wired, and all radios)

need k3.x kernel for 5ghz support

after factory reset, connect over default wifi and make the following changes from telnet, etc.

Code:

root@DD-WRT:~# nvram set lan_ifnames="vlan1 eth1"
root@DD-WRT:~# nvram set vlan0ports="0 1 2 3 8*"
root@DD-WRT:~# nvram set vlan1ports="3 2 1 0 8*"
root@DD-WRT:~# nvram set vlan2ports="4 8"
root@DD-WRT:~# nvram commit
root@DD-WRT:~# reboot


tested on 29739

first change fixes lan interfaces (switch is live), last 3 changes fix port assignments and cpu/default vlans (wan port and routing).

some bugs/conflation in the dd-wrt firmware on vlan numerology but this dances around them p.d.g.

will report a bug later... been running from this setup for a week as primary router and it's kicking ass.



speakxj7: Is your router Belkin N600 F7D8301? Which particular ddwrt firware did you use?
I'm currently using dd-wrt.v24-21061_NEWD2_K2.6_mega.bin2_K2.6_mega.bin
date: 2013-04-19

Don't want to risk and afraid to brick if I choose wrong unsupported ddwrt firmware for Belkin N600 F7D8301.

Please let me know. Thanks so much.


confused about what was unclear, but yeah
Belkin F7D4301 / F7D8301 v1

and
ftp://ftp.dd-wrt.com/betas/2016/05-19-2016-r29739/broadcom_K3X/dd-wrt.v24-29739_NEWD-2_K3.x_mega.bin
i'll double check the NV build spec, pretty sure that was it. [edit: yeah that's it]

keep in mind that you'd have to mess up pretty bad to brick this thing, since it has the mini cfe server baked in.

sorry for delay, some reason didn't get notified.


Hello speakxj7 and anyone:

Sorry need to revive this old thread and get some help here.

- For my F7D4301 I followed speakxj7 notes above to the tee and used the same r29739 fw and did the same telnet command he listed after flashing. All good and running fine for over a year. Grateful for his info.

- Now I want to get that CRACK thing fixed for good. I know the new r33607 FW has the CRACK fix.

Questions:
1. Has anyone tried to install this newest FW onto a F7D4301:
ftp://ftp.dd-wrt.com/betas/2017/10-25-2017-r33607/broadcom_K3X/dd-wrt.v24-33607_NEWD-2_K3.x_mega.bin

2. If I am to install that new r33607 K3.x mega FW ==> Do I still need to run that same Telnet code as before to fix those VLAN stuff??

Thanks for any comments!!
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Thu Nov 23, 2017 4:10    Post subject: Re: fixed Reply with quote
Fwiw, I updated a F7D8302 from the latest OEM firmware (file dated Dec 2010) directly to the K3X 33772 trailed build using the GUI, as I couldn't get the CFE webgui to come up (tried both the mentioned methods of booting with reset and also booting with WPS). Did a reset and now working great!
gti wrote:
- Now I want to get that CRACK thing fixed for good. I know the new r33607 FW has the CRACK fix.
The krack fix is not in that build for Broadcom; it's in 33772.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
gti
DD-WRT Novice


Joined: 11 Feb 2016
Posts: 9

PostPosted: Thu Nov 23, 2017 7:58    Post subject: Re: fixed Reply with quote
jwh7 wrote:
Fwiw, I updated a F7D8302 from the latest OEM firmware (file dated Dec 2010) directly to the K3X 33772 trailed build using the GUI, as I couldn't get the CFE webgui to come up (tried both the mentioned methods of booting with reset and also booting with WPS). Did a reset and now working great!
gti wrote:
- Now I want to get that CRACK thing fixed for good. I know the new r33607 FW has the CRACK fix.
The krack fix is not in that build for Broadcom; it's in 33772.


Yes 33772 latest would be my choice too now that it is available. I am using 33772 too in my other E4200 fine.

My question is related to the fact that with older DD-WRT Firmware for the F7D4301 ... people are reporting VLAN/LAN port issues and thus people came up with those script to fix it after flashing.

I want to know if the newest firmware like this 33772 would still need those script to be run .... as I don't have time or want to do any debugging after I flash it if something goes wrong.

For your F7D8302 ... did you use older dd-wrt firmware before?? Different model may not have the same issue.
So if yours never had any problem before then it is safe to say newer ones should works the same.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Thu Nov 23, 2017 19:32    Post subject: Re: fixed Reply with quote
gti wrote:
For your F7D8302 ... did you use older dd-wrt firmware before??
I just got it at Goodwill a couple days ago; I updated to the latest OEM f/w, then flashed directly to the 33772 build using the GUI.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
native_tx
DD-WRT User


Joined: 26 Feb 2014
Posts: 169
Location: Texas

PostPosted: Sun Nov 26, 2017 21:59    Post subject: Reply with quote
as for me, i installed the r33772 using the CFE but since I moved to Spectrum, my belkin won't reach the advertised bandwidth 100/10 properly and after speed testing the 100/10 turns to 114/11, but still the belkin can be used as a wap.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Sun Nov 26, 2017 22:36    Post subject: Reply with quote
native_tx wrote:
as for me, i installed the r33772 using the CFE but since I moved to Spectrum, my belkin won't reach the advertised bandwidth 100/10 properly and after speed testing the 100/10 turns to 114/11, but still the belkin can be used as a wap.
Do you mean that your 100/10 service tests at 114/11, but your Belkin router (what model?) running 33772 (k3x?) doesn't achieve those speeds (wired?)? If running k3x, I presume SFE is enabled, and that you did a reset and manual setup?
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
native_tx
DD-WRT User


Joined: 26 Feb 2014
Posts: 169
Location: Texas

PostPosted: Wed Nov 29, 2017 16:42    Post subject: Reply with quote
jwh7 wrote:
native_tx wrote:
as for me, i installed the r33772 using the CFE but since I moved to Spectrum, my belkin won't reach the advertised bandwidth 100/10 properly and after speed testing the 100/10 turns to 114/11, but still the belkin can be used as a wap.
Do you mean that your 100/10 service tests at 114/11, but your Belkin router (what model?) running 33772 (k3x?) doesn't achieve those speeds (wired?)? If running k3x, I presume SFE is enabled, and that you did a reset and manual setup?



Testing is always done wired. The ISP advertises 100/10, speed test show gives 114/11 but those numbers were done a different model i had tested on linksys e3200 but my belkin f7d4302 fell short at least by 20mbps the upload achieved the 11mbps, with no qos, disabled the sfe, in order to run some qos testing but maybe I didn't give it a good looking into, the install i used the cfe for installing the mega build r33772 kind of use to that method, sorry for the confusion from my OP.
speakxj7
DD-WRT Novice


Joined: 09 May 2013
Posts: 25

PostPosted: Tue Feb 13, 2018 22:43    Post subject: Reply with quote
just following up here. recently did a upgrade on my isp service tier, and i'm pleased to report that SFE (on a k3x build) is working great.

wired, this little guy seems to route 300/300.

i've got a heavier duty router in the wings, but this thing keeps on chugging.
wcnngt
DD-WRT Novice


Joined: 06 Dec 2011
Posts: 15

PostPosted: Tue Aug 20, 2019 1:33    Post subject: what's the fully working k3 build Reply with quote
Can anyone tell me what's the latest fully working k3 build? thanks.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14126
Location: Texas, USA

PostPosted: Tue Aug 20, 2019 8:55    Post subject: Re: what's the fully working k3 build Reply with quote
wcnngt wrote:
Can anyone tell me what's the latest fully working k3 build? thanks.


I see you found this thread that I referenced in the other thread. Hopefully, someone chimes in with an answer. There really needs to be a wiki for this device.
piers7
DD-WRT Novice


Joined: 03 Sep 2019
Posts: 1

PostPosted: Wed Sep 04, 2019 14:50    Post subject: Re: fixed Reply with quote
speakxj7 wrote:

Code:
root@DD-WRT:~# nvram set lan_ifnames="vlan1 eth1"
root@DD-WRT:~# nvram set vlan0ports="0 1 2 3 8*"
root@DD-WRT:~# nvram set vlan1ports="3 2 1 0 8*"
root@DD-WRT:~# nvram set vlan2ports="4 8"
root@DD-WRT:~# nvram commit
root@DD-WRT:~# reboot

tested on 29739

first change fixes lan interfaces (switch is live), last 3 changes fix port assignments and cpu/default vlans (wan port and routing).


gti wrote:

I want to know if the newest firmware like this 33772 would still need those script to be run .... as I don't have time or want to do any debugging after I flash it if something goes wrong.


My painful trial-and-error testing has lead me to understand that as of 33772 you don't need to do any of this - that the 'factory reset' configuration will work as-is, provided you wait and perform a second reboot after the box has booted up after flash-and-reset. It comes up with lan_ifnames=vlan1,eth1,eth2 (which is not exactly what speakxj7 had above) but seems to work.

I also realize that connecting via the WiFi is (counter intuitively) the 'safe' option after flashing/reset, having let https://wiki.dd-wrt.com/wiki/index.php/Switched_Ports sink in a bit. That could have saved me much frustration starting out.

I would love, however, for someone to explain patiently to me what is going on with the vlan1ports config line being the same as vlan0ports, but with the non-CPU ports backwards.

Also why - given that both 'vlan2ports=4 8' and 'wan_ifname=vlan2' tell me the WAN is on VLAN2, does the VLANs tab in the web GUI show the 'W' port as VLAN 1? What *is* that VLANs tab attempting to show me anyway?

(edit: corrected a mistake from previous version of this post which was just wrong, and schooled me about actually doing the second reboot)
Goto page Previous  1, 2, 3 ... , 25, 26, 27  Next Display posts from previous:    Page 26 of 27
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum