New EKO Builds 4/7/12 18946 - Supports the new Cisco's

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next
Author Message
redhawk0
DD-WRT Guru


Joined: 04 Jan 2007
Posts: 11472
Location: Wherever the wind blows- North America

PostPosted: Thu Apr 12, 2012 1:13    Post subject: Reply with quote
As stated earlier in this thread...Repeater mode is broken...and has been for 5 months....but only in K26 builds....older V24 builds are working fine.


http://www.dd-wrt.com/phpBB2/viewtopic.php?p=680582#680582

redhawk

_________________
I do NOT provide personal assistance through chat or phone....so please don't ask.
Sponsor
UrbanVoyeur
DD-WRT User


Joined: 19 Jun 2010
Posts: 118
Location: Brooklyn, NY

PostPosted: Thu Apr 12, 2012 3:31    Post subject: Reply with quote
tatsuya46 wrote:

Repeater/client, not bridge. Selecting either of them with the proper SSID of the host unit & security etc, nothing happens it doesn't even connect or try to its like the radio is off. No security gives the same result.


I am able to get Client, Client Bridge, and Repeater Bridge to work. Repeater Bridge works for both wired and wireless clients. All clients on the secondary can connect to the internet, and where bridged, they can see the entire LAN.

In Repeater mode (NOT bridged), the wireless connection back to the primary works, as do wired clients to the secondary for internet. However, no client can connect to the the virtual wireless interface on the secondary, regardless of the security settings combinations.

Primary E3000 r16994 big
Secondary E900 r18946 mini

_________________
Linksys E900 dd-wrt v24-sp2 18946 mini
Linksys E3000 dd-wrt v24-sp2 15692 std-usb-nas
D-Link DIR-601 Gargoyle 1.5.3 ar71xx dir 600 a1 squashfs
Eko
DD-WRT Developer/Maintainer


Joined: 07 Jun 2006
Posts: 5772

PostPosted: Thu Apr 12, 2012 5:10    Post subject: Reply with quote
yeah... i can confirm repeater problem. Signal on virtual interface is just 0. Usually helps if you give radio a kick by turning it off/on. I'm investigating...
Something in wireless driver Sad
BasCom
DD-WRT Guru


Joined: 29 Jul 2009
Posts: 1378
Location: Germany

PostPosted: Thu Apr 12, 2012 8:41    Post subject: Reply with quote
i did an upgrade through a vpn connection (wrt320n). router did reboot, but didnt start openvpn itself and no webif access, no matter what connection. after telnet in, reboot, device didnt came back Very Happy so i have to see next tuesday.
_________________
RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
Bird333
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 809

PostPosted: Thu Apr 12, 2012 12:02    Post subject: Reply with quote
'My page' doesn't seem to be working on this build either. I just get a blank white screen when I click on the tab.
simpop12
DD-WRT Novice


Joined: 12 Apr 2012
Posts: 1

PostPosted: Thu Apr 12, 2012 16:01    Post subject: Soft reboot fails Reply with quote
Overall success with a Linksys WRT600N 1.1, flashed with 'mini-usb-ftp - build 18946M NEWD-2 Eko'. Only problem I've noticed is that when soft rebooting the router either from the interface or after a change of settings, the router is unresponsive, all the appropriate lights are on, but power blinks for 10 minutes +. Any ideas how to fix this? I have to hard reboot and then it works great.
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7364
Location: YWG, Canada

PostPosted: Thu Apr 12, 2012 18:42    Post subject: Reply with quote
Eko wrote:
yeah... i can confirm repeater problem. Signal on virtual interface is just 0. Usually helps if you give radio a kick by turning it off/on. I'm investigating...
Something in wireless driver Sad


Whats wrong with using the Broadcom driver that Tomato RAF/Toastman/Teaman/USB uses? It is newer & much more improved in nearly every aspect. Last time I tried to say this I got a "the generic reply" saying "Broadcom hasn't provided or it doesn't exist etc", well they have it so its out there.. & as this shows, is needed.

My sig unit will not even CONNECT, if it somehow is the GUI does not show it. Reverting to a old build is not an option as those builds have dead QoS, memory leaks & much other issues making them unusable.

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ----> DD-WRT v3.0-r44425 std
[QUALCOMM] DIR-862L ------------------------------> DD-WRT v3.0-r44412 std
[QUALCOMM] WNDR4300 v1 ------------------------> DD-WRT v3.0-r44412 std
[QUALCOMM] DIR-862L ------------------------------> DD-WRT v3.0-r44412 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 --------------------------> DD-WRT v3.0-r44251 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
defcon
DD-WRT Novice


Joined: 16 Nov 2010
Posts: 5

PostPosted: Thu Apr 12, 2012 20:04    Post subject: e4200 Reply with quote
upgraded my e4200 v1 from 18000 to 18946M NEWD-2 K2.6 Eko via the web interface resetting factory defaults. Worked fine, getting better speed wireless connections than before
crashfly
DD-WRT Guru


Joined: 24 Feb 2009
Posts: 2026
Location: Sol System > Earth > USA > Arkansas

PostPosted: Thu Apr 12, 2012 23:27    Post subject: Re: Soft reboot fails Reply with quote
simpop12 wrote:
Overall success with a Linksys WRT600N 1.1, flashed with 'mini-usb-ftp - build 18946M NEWD-2 Eko'. Only problem I've noticed is that when soft rebooting the router either from the interface or after a change of settings, the router is unresponsive, all the appropriate lights are on, but power blinks for 10 minutes +. Any ideas how to fix this? I have to hard reboot and then it works great.

Maybe this is related to passing the WAN dhcp through the WAN/LAN interface when starting up. Try checking your IP address right after rebooting your router. I have found that dhcp gets passed from WAN to the LAN side and I have an "external" IP address. After waiting 5 minutes or so, I can reacquire an IP address on the LAN side.

_________________
E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]

Try Dropbox for syncing files - get 2.5gb online for free by signing up.

Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7632

PostPosted: Fri Apr 13, 2012 3:11    Post subject: Reply with quote
tatsuya46 wrote:
Eko wrote:
yeah... i can confirm repeater problem. Signal on virtual interface is just 0. Usually helps if you give radio a kick by turning it off/on. I'm investigating...
Something in wireless driver Sad


Whats wrong with using the Broadcom driver that Tomato RAF/Toastman/Teaman/USB uses?


It is a binary blob for which they don't have the source code - they can not rebuild the driver and add repeater and client modes, they can't make any modifications to the driver.

_________________
Kernel panic: Aiee, killing interrupt handler!
p_shep
DD-WRT User


Joined: 14 Mar 2011
Posts: 51

PostPosted: Fri Apr 13, 2012 21:36    Post subject: Reply with quote
Seems to be working well on my e3000 in client bridge mode. Only have 2.4GHz running though, and nothing plugged into the Ethernet sockets... using it as a bitcoin mining rig attached to some FPGAs Smile
Murrkf
DD-WRT Guru


Joined: 22 Sep 2008
Posts: 12676

PostPosted: Fri Apr 13, 2012 22:20    Post subject: Reply with quote
Eko wrote:
yeah... i can confirm repeater problem. Signal on virtual interface is just 0. Usually helps if you give radio a kick by turning it off/on. I'm investigating...
Something in wireless driver Sad


Me too. No signal on virtual. Appears to be connected to primary when looking at primary though.

Loaded on my e3000 with the e3000 build and the nv60k build.

_________________
SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Gingernut
DD-WRT User


Joined: 29 Jul 2007
Posts: 229

PostPosted: Fri Apr 13, 2012 22:59    Post subject: Reply with quote
Murrkf wrote:
Eko wrote:
yeah... i can confirm repeater problem. Signal on virtual interface is just 0. Usually helps if you give radio a kick by turning it off/on. I'm investigating...
Something in wireless driver Sad


Me too. No signal on virtual. Appears to be connected to primary when looking at primary though.

Loaded on my e3000 with the e3000 build and the nv60k build.


Somthing similar occurs on the latest Atheros builds but only when 40mhz wireless band width is selected, 20mhz is ok. Maybe not the case, but hea, I thought I'd chime in.
rroot
DD-WRT Novice


Joined: 19 Dec 2011
Posts: 4

PostPosted: Sat Apr 14, 2012 1:48    Post subject: Reply with quote
Router is a Linksys E4200.
Loaded the "dd-wrt.v24-18946_NEWD-2_K2.6_std_usb_nas-nv60k.bin"

Install went smoothly, and checked a few settings such as
Nat/Qos> Port Forwarding, seems to be working fine
Nat/Qos> Port Triggering, Seems to be working fine
Wireless> Basic Settings, wl0 Seems to be working fine
Wireless> Basic Settings, wl1 Disabled atm, can't report on that
Wireless> Wireless Security, wl0 Seems to be working fine.

An Issue I noticed is with the Services> USB and NAS.
When the USB device is mounted then dismounted, I can not get any device to remount.
Even doing a software GUI reboot will not trigger the "Automatic Drive Mount"
If I physically do a Power Cycle on the Router (unplug and replug in power) then upon boot, the router will run the "Automatic Drive Mount" and properly mount the device.

My OS is Win XP Pro
Scenario I am going through to duplicate the issue.
I am mounting a single 500 GB WD as NAS, to test.
A. Mount
1. Connect Hard Drive to USB on e4200 (no power to hard drive yet)
2. Within GUI, Services>USB, Enable "Core USB Support,
3. In the same window, Enable USB Storage Support, Enable Automatic Drive Mount and Leave "Disk Mount Point" as /mnt
4. Turn on power to the Hard Drive
After the device is recognized, the "Automatic Drive Mount" will properly mount the Hard Drive and display the information in the lower window of the GUI.
5. Mouse to the NAS Tab and within File Sharing, Enable Samba.
6. Fill in Workgroup as Workgroup
7. In the Shares>Path I use the drop down arrow and select the appropriate Mount Point, then give it a name
8. In the Users, I add a user name, password and check the access share.

After the system settles down and windows locates the share I am able to browse the share locally.
Looking good so far. Full read/write, etc.
(just a few other thoughts I will ask about later, usb 1.1?, broadcasting, etc..)

B. Dismount: (basically reverse order)
1. In Services>NAS disable Samba. click apply settings
2. Power off to Hard Drive
2. In Services>USB disable "Core USB Support" click apply settings.

When I attempt to remount the device, it seems as if the "Automatic Drive Mount" is not being run.
There is not any mounting point information displayed within the 'Disk Info" box.
A reboot through the GUI Services>Services tab will not force a Automatic Drive Mount.
But a power cycle on the router will force the Automatic Drive Mount.

Within the Syslogs, I see the initial Mount, Dismount and Remount.
Even though it looks ok to my untrained eye, there may be something missing.
The logs are below:

Initial Mount: (and Samba Start)
kernel: usbcore: registered new device driver usb
kernel: usbcore: registered new interface driver hub
kernel: usbcore: registered new interface driver usbfs
kernel: USB20H mdio control register : 0x8000000c
kernel: USB20H mdio control register : 0x8000000c
kernel: SCSI subsystem initialized
kernel: USB Universal Host Controller Interface driver v3.0
kernel: ehci_hcd 0000:00:04.1: EHCI Host Controller
kernel: ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
kernel: ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
kernel: ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
kernel: hub 1-0:1.0: 2 ports detected
kernel: hub 1-0:1.0: USB hub found
kernel: ohci_hcd 0000:00:04.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:04.0: irq 5, io mem 0x18009000
kernel: ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
kernel: usb usb1: configuration #1 chosen from 1 choice
kernel: hub 2-0:1.0: 2 ports detected
kernel: hub 2-0:1.0: USB hub found
kernel: usb usb2: configuration #1 chosen from 1 choice
kernel: PCI: Setting latency timer of device 0000:00:04.0 to 64
kernel: PCI: Setting latency timer of device 0000:00:04.1 to 64
kernel: ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
kernel: Initializing USB Mass Storage driver...
kernel: USB Mass Storage support registered.
kernel: usbcore: registered new interface driver usb-storage
kernel: usb 1-1: new high speed USB device using ehci_hcd and address 2
kernel: scsi0 : SCSI emulation for USB Mass Storage devices
kernel: usb 1-1: configuration #1 chosen from 1 choice
kernel: usb-storage: device found at 2
kernel: usb-storage: waiting for device to settle before scanning
kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel: fuse init (API version 7.8)
kernel: scsi 0:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4
kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
kernel: sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
kernel: sd 0:0:0:0: [sda] Attached SCSI disk
kernel: sd 0:0:0:0: [sda] Write Protect is off
kernel: sd 0:0:0:0: [sda] Write Protect is off
kernel: /dev/scsi/host0/bus0/target0/lun0: p1
kernel: sd 0:0:0:0: [sda] Mode Sense: 10 00 00 00
kernel: sd 0:0:0:0: [sda] Mode Sense: 10 00 00 00
kernel: usb-storage: device scan complete
syslog: Samba3 : samba started
- - -

Samba Stop and Dismount:
syslog: smbd : samba successfully stopped
syslog: nmbd : nmbd successfully stopped
syslog: smbd : samba hanging, send SIGKILL
syslog: nmbd : nmbd hanging, send SIGKILL
kernel: usb 1-1: USB disconnect, address 2
kernel: ehci_hcd 0000:00:04.1: remove, state 1
kernel: ohci_hcd 0000:00:04.0: USB bus 2 deregistered
kernel: ohci_hcd 0000:00:04.0: remove, state 1
kernel: usb usb1: USB disconnect, address 1
kernel: usb usb2: USB disconnect, address 1
kernel: ehci_hcd 0000:00:04.1: USB bus 1 deregistered
- - -

Attempt to Remount: (enable Core USB and turn on Hard Drive)
kernel: USB20H mdio control register : 0x8000000c
kernel: USB20H mdio control register : 0x8000000c
kernel: ehci_hcd 0000:00:04.1: EHCI Host Controller
kernel: ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
kernel: ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
kernel: ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
kernel: hub 1-0:1.0: 2 ports detected
kernel: hub 1-0:1.0: USB hub found
kernel: usb usb1: configuration #1 chosen from 1 choice
kernel: USB Universal Host Controller Interface driver v3.0
kernel: hub 2-0:1.0: 2 ports detected
kernel: hub 2-0:1.0: USB hub found
kernel: ohci_hcd 0000:00:04.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:04.0: irq 5, io mem 0x18009000
kernel: ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
kernel: usb usb2: configuration #1 chosen from 1 choice
kernel: ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
kernel: scsi2 : SCSI emulation for USB Mass Storage devices
kernel: usb 1-1: configuration #1 chosen from 1 choice
kernel: usb 1-1: new high speed USB device using ehci_hcd and address 2
kernel: usb-storage: device found at 2
kernel: usb-storage: waiting for device to settle before scanning
kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
kernel: scsi 2:0:0:0: Direct-Access Ext Hard Disk PQ: 0 ANSI: 4
kernel: sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
kernel: sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
kernel: sd 2:0:0:0: [sdb] Write Protect is off
kernel: sd 2:0:0:0: [sdb] Write Protect is off
kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
kernel: /dev/scsi/host2/bus0/target0/lun0: p1
kernel: sd 2:0:0:0: [sdb] Mode Sense: 10 00 00 00
kernel: sd 2:0:0:0: [sdb] Mode Sense: 10 00 00 00
kernel: usb-storage: device scan complete
- - -
_Robb_
DD-WRT User


Joined: 14 Jan 2012
Posts: 324
Location: Wr PL

PostPosted: Sat Apr 14, 2012 22:06    Post subject: Reply with quote
SSH is till an issue (key regeneration at startup - dropbearconvert gives segmenation fault) on E4200.
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=681752#681752
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next Display posts from previous:    Page 4 of 9
Post new topic   Reply to topic    DD-WRT Forum 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