Fractal, not sure if this is something you can fix, but the 5GHz Blue LED is solid on the WNDR3400, I have clients connected so it should flash with activity.
The 2.4GHz LED does flash with activity when clients are connected.
I've found these two threads, but they don't specifically address the issue.
OpenVPN Server is working for me in the latest build 20058
Was not working in the last one.
Hi Msignor,
I have tested this in the morning and it's working, but not for my purpose...
I can make it works for the Clients like computers, but not for my clients E4200 with DD-WRT. I'm sure and as I said in other post these routers aren't a good clients, because with the WRT160NL is working fine and as expected.
Many thanks Fractal to provide a version with a working OpenVPN server although that for me isn't working.
Regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Last edited by Bronk-S on Mon Oct 01, 2012 19:22; edited 1 time in total
Unfortunately, SVN 2580 is still present in build 20058. Will be trying another USB drive here in a second. EDIT2: Second USB Drive caused other problems for the device as can be seen in comment 32 in the SVN Ticket.
Quote:
root@Dark-Knight:~# dmesg
Linux version 2.6.24.111 (compiler@chaos) (gcc version 4.1.2) #14 Sun Sep 30 14:53:35 PDT 2012
CPU revision is: 00019749
Determined physical RAM map:
memory: 07fff000 @ 00000000 (usable)
memory: 08000000 @ 87fff000 (usable)
Entering add_active_range(0, 0, 32767) 0 entries of 256 used
Entering add_active_range(0, 557055, 589823) 1 entries of 256 used
Zone PFN ranges:
Normal 0 -> 131072
HighMem 131072 -> 589823
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0 -> 32767
0: 557055 -> 589823
On node 0 totalpages: 65535
Normal zone: 0 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 32767 pages, LIFO batch:7
HighMem zone: 0 pages used for memmap
HighMem zone: 32768 pages, LIFO batch:7
Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order. Total pages: 65535
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: BCM5300 rev 1 at 600 MHz
...
...
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>
decode 1f02
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 188k freed
roboswitch: Probing device eth0: found a 53125!
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
PCI: Setting latency timer of device 0000:00:04.1 to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:04.1: EHCI Fastpath: New EHCI driver starting
ehci_hcd 0000:00:04.1: irq 6, io mem 0x18004000
ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
uhci_hcd: USB Universal Host Controller Interface driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
PCI: Setting latency timer of device 0000:00:04.0 to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:04.0: irq 6, io mem 0x18009000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new high speed USB device using ehci_hcd and address 2
SCSI subsystem initialized
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-1.4: new high speed USB device using ehci_hcd and address 3
usb 1-1.4: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
scsi 0:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] Attached SCSI removable disk
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
etherip: Ethernet over IPv4 tunneling driver
usb 1-1.2: new high speed USB device using ehci_hcd and address 4
usb 1-1.2: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
scsi 1:0:0:0: Direct-Access Corsair Voyager 1100 PQ: 0 ANSI: 0 CCS
sd 1:0:0:0: [sdb] 15820800 512-byte hardware sectors (8100 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Assuming drive cache: write through
/dev/scsi/host1/bus0/target0/lun0: p1 p2 p3
sd 1:0:0:0: [sdb] Attached SCSI removable disk
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
ehci_hcd 0000:00:04.1: fatal error
ehci_hcd 0000:00:04.1: force halt; handshake b8004014 00004000 00004000 -> -145
ehci_hcd 0000:00:04.1: HC died; cleaning up
usb 1-1: USB disconnect, address 2
usb 1-1.2: USB disconnect, address 4
sd 1:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdb, sector 1802303
Buffer I/O error on device sdb1, logical block 225280
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421901
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421902
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421903
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421904
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421905
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421906
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421907
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421908
lost page write due to I/O error on sdb1
Buffer I/O error on device sdb1, logical block 421909
lost page write due to I/O error on sdb1
sd 1:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00
end_request: I/O error, dev sdb, sector 3375167
Aborting journal on device sdb1.
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
ext3_abort called.
EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
usb 1-1.4: USB disconnect, address 3
usb 2-1: new full speed USB device using ohci_hcd and address 2
scsi 1:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sdb1): ext3_find_entry: reading directory #95233 offset 0
scsi 1:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sdb1): ext3_find_entry: reading directory #111105 offset 0
scsi 1:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0
scsi 1:0:0:0: rejecting I/O to dead device
EXT3-fs error (device sdb1): ext3_find_entry: reading directory #111105 offset 0
usb 2-1: not running at top speed; connect to a high speed hub
usb 2-1: configuration #1 chosen from 1 choice
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
usb 2-1.2: new full speed USB device using ohci_hcd and address 3
usb 2-1.2: device descriptor read/64, error -145
root@Dark-Knight:~#
Optware does not run on this. My usb drive is mounted to /opt but it seems optware isn't running. Is there something that is stopping all the 'S**' scripts from running once /opt is mounted? Since optware is not running, Samba doesn't work for me.
Optware does not run on this. My usb drive is mounted to /opt but it seems optware isn't running. Is there something that is stopping all the 'S**' scripts from running once /opt is mounted? Since optware is not running, Samba doesn't work for me.
Yes I agree. Optware is not running with it's services anymore. I believe Fractal mentioned that new USB drivers were included in this build, so maybe we need to reformat drive and start optware from scatch again. Not sure. Also I noticed that I can't roll back to a earlier build back to 18024. Wondering if anyone else having the same issue?.
Joined: 31 Aug 2009 Posts: 2448 Location: Third Rock from the Sun
Posted: Tue Oct 02, 2012 6:29 Post subject:
Mega-wrt160nv3, Openvpn-wrt160nv3 and Std_usb_nas-wrt160nv3 are all too large for the flash on that device. _________________ Peacock Thread-FAQ -- dd-wrt Wiki
Mega-wrt160nv3, what is that?
wrt160Nv3 has 4MB flash and can not run a mega build, neither an openvpn or std-usb-nas build.
Eko has made small-openvpn builds in the past but I don't know if that is possible now when OpenVPN and other modules has grown in size. _________________ Kernel panic: Aiee, killing interrupt handler!
Optware does not run on this. My usb drive is mounted to /opt but it seems optware isn't running. Is there something that is stopping all the 'S**' scripts from running once /opt is mounted? Since optware is not running, Samba doesn't work for me.
Yes I agree. Optware is not running with it's services anymore. I believe Fractal mentioned that new USB drivers were included in this build, so maybe we need to reformat drive and start optware from scatch again. Not sure. Also I noticed that I can't roll back to a earlier build back to 18024. Wondering if anyone else having the same issue?.
You shouldn't have to reinstall Optware. The router is supposed to run the scripts in the /opt directory. I rolled back to an older firmware but the timer did run out. I waited probably another 5 minutes before I did a hardware reset. I was really scared I was going to brick it because it never did reboot on its own. After I did the reset, it booted back up into the old firmware.
OpenVPN Server is working for me in the latest build 20058
Was not working in the last one.
Hi Msignor,
I have tested this in the morning and it's working, but not for my purpose...
I can make it works for the Clients like computers, but not for my clients E4200 with DD-WRT. I'm sure and as I said in other post these routers aren't a good clients, because with the WRT160NL is working fine and as expected.
Many thanks Fractal to provide a version with a working OpenVPN server although that for me isn't working.
Regards.
I would have to say to check your configuration or reset your router to defaults and try again.
Fractal has this working as a client, and I have it working as a Server.
You may also want to try lowering your encryption away from 256 bit (if your using it) I personally am using the bare defaults, 128 / CBC / Blowfish and it works fine.
I would have to say to check your configuration or reset your router to defaults and try again.
Fractal has this working as a client, and I have it working as a Server.
You may also want to try lowering your encryption away from 256 bit (if your using it) I personally am using the bare defaults, 128 / CBC / Blowfish and it works fine.
I can confirm that from my side I used all the encryption, without, tun, tap, etcetc and nothing success...
Today I have tried to use the WRT160NL as a Server and the E4200 as a client at the same results, doing in the opposite way after this last test everything succes the WRT160NL is capable to be a client/server, but I'm under impresion that the E4200 isn't able to be a client...
Last shot using the nvrambak.bin of the WRT160NL in the E4200 it works, but after a reboot the router can't boot.
Many thanks and I hope that Sash give me the opportunity to raise the ticket.
Regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Tue Oct 02, 2012 17:59 Post subject:
Bronk-S wrote:
Last shot using the nvrambak.bin of the WRT160NL in the E4200 it works, but after a reboot the router can't boot.
off topic but I had to chime in.
you restored a config backup from an atheros chipset device to a broadcom device. That was not good. I don't think serial will work.. maybe, but I don't think so. _________________ [Moderator Deleted]
