The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
This is probably a stupid question but could the network encryption have anything to do with it?
What I am wondering is if you are open does the speed increase? I would participate but I am only 8meg down and 800k up so I don't see the issues. (Part of the problem living in the sticks)
(Last edited by northbound on 24 Jul 2015, 01:59)
This is probably a stupid question but could the network encryption have anything to do with it?
I wish. Disabled the encryption and it still was slow - http://www.dslreports.com/speedtest/932059
I should have known it would not be that simple but ya gotta start somewhere 
Did you notice the Re-xmit Avg Higher under the unencrypted? Weird.....
(Last edited by northbound on 24 Jul 2015, 02:07)
The cpu on these routers has a hardware encryption module (at least according to the quick search I did), so it's probably not the network encryption.
It wouldn't hurt to try disabling it to check through
Also, you may want to do a iw wlan1 scan (assuming that's the 5Ghz radio) and see what else is in your area and on what channel
for example, there were posts here earlier pushing you to use channels 149 or 157 but if someone near you is using those channels, you shouldn't try using them
iw wlan0 scan |grep -e SSID -e 'primary channel' -e signal:
will give you the ids, channels, and signal strengths of nearby stations
The cpu on these routers has a hardware encryption module (at least according to the quick search I did), so it's probably not the network encryption.
It wouldn't hurt to try disabling it to check through
Also, you may want to do a iw wlan1 scan (assuming that's the 5Ghz radio) and see what else is in your area and on what channel
for example, there were posts here earlier pushing you to use channels 149 or 157 but if someone near you is using those channels, you shouldn't try using them
iw wlan0 scan |grep -e SSID -e 'primary channel' -e signal:
will give you the ids, channels, and signal strengths of nearby stations
I wish I had fiber I have ran multiple scans and there is no AP around me on the 5Ghz. This can be done in Luci. But you have to be on 2.4Ghz to scan 5Ghz. Or hardwired)
(Last edited by northbound on 24 Jul 2015, 02:12)
The cpu on these routers has a hardware encryption module (at least according to the quick search I did), so it's probably not the network encryption.
It wouldn't hurt to try disabling it to check through
Also, you may want to do a iw wlan1 scan (assuming that's the 5Ghz radio) and see what else is in your area and on what channel
for example, there were posts here earlier pushing you to use channels 149 or 157 but if someone near you is using those channels, you shouldn't try using them
iw wlan0 scan |grep -e SSID -e 'primary channel' -e signal:
will give you the ids, channels, and signal strengths of nearby stations
No interfering channels - I wish it was that easy.
hey guys, new here. I installed RC3 on my router and now i can't access my router via https://www.linksyssmartwifi.com and my WiFi no longer works. I'd appreciate the help. Thanks in advance
hey guys, new here. I installed RC3 on my router and now i can't access my router via https://www.linksyssmartwifi.com and my WiFi no longer works. I'd appreciate the help. Thanks in advance
That link to access the web UI only works with stock firmware. Wireless is disabled by default in OpenWrt for security reasons. Go to http://192.168.1.1 and you should get access to your router and be able to configure wifi.
(Last edited by drawz on 24 Jul 2015, 04:33)
jrdnlc wrote:hey guys, new here. I installed RC3 on my router and now i can't access my router via https://www.linksyssmartwifi.com and my WiFi no longer works. I'd appreciate the help. Thanks in advance
That link to access the web UI only works with stock firmware. Wireless is disabled by default in OpenWrt for security reasons. Go to http://192.168.1.1 and you should get access to your router and be able to configure wifi.
That worked, Thanks a lot! Got me scared for a bit 
I can't see any way to search within a thread here. Any word on usb support for the WRT1200/1900AC's? I'm running the trunk build from 5 days ago on a WRT1200AC, and I haven't been able to figure out how to utilize either of the USB ports.
(Last edited by fecaleagle on 24 Jul 2015, 05:07)
usb3 port works fine, usb2 does not work (wrt1200ac)
I can't see any way to search within a thread here. Any word on usb support for the WRT1200/1900AC's? I'm running the trunk build from 5 days ago on a WRT1200AC, and I haven't been able to figure out how to utilize either of the USB ports.
This will get you started http://wiki.openwrt.org/doc/howto/storage?s[]=kmod&s[]=fs&s[]=ntfs
I am running trunk r46432 and both of my ports work on 1900ac
The 1900ac is not the exact same hardware. The 1200ac is similar to 1900 v2, and apparently the usb2 chipset isn't detected properly.
Understood but he said he could not use either so I assumed he did not know about mounting.
It might be fixed by the time the buildbot has a successful build
(Last edited by northbound on 24 Jul 2015, 12:07)
usb3 port works fine, usb2 does not work (wrt1200ac)
Thanks! I could have sworn I tried to fdisk -l and mount from both, but you are right, the usb3 port is good to go. :)
Understood but he said he could not use either so I assumed he did not know about mounting.
It might be fixed by the time the buildbot has a successful build :)
I did think that I had tried both and reported that neither worked. Thanks for your response as well. I'm coming from a WRT54G, so USB is just icing on the cake.
Issues #20 and #21 are frankly much more pressing. Does anybody know if WiFi bugs https://github.com/kaloz/mwlwifi/issues/20 and https://github.com/kaloz/mwlwifi/issues/21 affect the 1200AC as well? I understand the radios are the same. I had a lockup last night after a disconnect that required a reboot to resolve. Since I am running the trunk build and not RC2, I will enable logging and try to replicate tonight.
(Last edited by fecaleagle on 24 Jul 2015, 16:40)
Since moving to RC3, it's been a week, and no lockups. So far RC3 has been very stable, so I have nothing to work on 
It's hilarious I'll complain about problems, and then complain some more when there is nothing to work on 
(Last edited by davidc502 on 24 Jul 2015, 17:02)
will give you the ids, channels, and signal strengths of nearby stations
Thanks for the tip...
root@AC1900M:~# iw wlan1 scan |grep -e SSID -e 'primary channel' -e signal:
signal: -73.00 dBm
SSID: SHAW-65500D-5G
* primary channel: 149
signal: -91.00 dBm
SSID: SHAW-D5364F-5G
* primary channel: 149
signal: -90.00 dBm
SSID: OptikTV_10ADC53B
* primary channel: 157
signal: -86.00 dBm
SSID: OptikTV_960B400B
* primary channel: 157
root@AC1900M:~#
RickStep wrote:. . .
The issue then becomes what can influence time.
@alirz says that if he reboots the router once a week there is NO crash.
Those that reboot after a crash have several days up time before the next crash.
We seem NOT to be chasing why TIME is a real issue.
Rick
There are a couple things here
first off, as I understand it, this isn't a reliably reproducable thing. Some people have problems regularly, others have no problems at all.
if it's an improbable race, then the longer it's running the more likely it is to hit the race.
The driver does have internal state that it keeps. For example, it's list of what's connected to it. If it 'looses' an entry every once in a while, it will keep going for a while and then stop.
The fact that when the problem hits, it's not the entire system that dies, just the one wireless interface in an indication of a driver problem.
The kernel has a mechanism to deal with running out of memory (it looks at what it thinks is taking 'too much' memory and kills a process), this would show up in logs.
but I can always be wrong, so it's worth someone checking who can reproduce the problem.
Let me clarify again; I am using Linksys firmware. While I want/need better firmware (which is why I bought the WRT1900AC in May of 2014); up time is at the top of the list. Stock firmware here runs for weeks/months.
I may be chasing some phantoms here.
Since my original post I remembered that all devices in the household drop off the Linksys network map EXCEPT blackberry devices (2 Z10s, a Z30 & a Q5). The Blackberries also don't have the reserve battery usage that Blackberry claims.
At present there are no Android & Apple phones here; only an Apple iPad mini v2.
Question? Are Apple & Google possibly increasing battery life by turning off the radios and restarting them periodically to check for messages on WIFI (e.g. email). Text messages are delivered over cellular (as are email unless you are at home and connect through your router). This would produce a huge list of connected & disconnected devices (reference @dlang above "If it 'looses' an entry every once in a while, it will keep going for a while and then stop").
Just another thought. There has to be a way to determine why this router won't run for months without attention, providing it has clean battery backed up power.
Surely there are some that regularly read and/or post here that could monitor AND email out to a newly created web site monitoring of the 2 WIFI transmitters and other items that would make small local logs obsolete; in the short term.
Rick.
@RickStep
About two months ago I attempted to find out how long I could go without a crash. So I disabled the weekly reboot script. I went 13 or 16 days, I don't remember exactly, and then it crashed.
In my case I had no ping to the router, no internet, no ssh to the router. I don't remember checking if I could access my local network e.g my NAS during that time.
Power cycle is what brought is back online.
My longest uptime was 26 days, but 4.1 made it to stable and flashed a new images based on it otherwise it would have gone for longer. I still cannot reproduce either issues though I tried both RC2 and RC3.
nitroshift
My longest uptime was 26 days, but 4.1 made it to stable and flashed a new images based on it otherwise it would have gone for longer. I still cannot reproduce either issues though I tried both RC2 and RC3.
nitroshift
@nitroshift
How did you manage to boot a 4.1 image? I've tried and always get a kernel panic complaining about not finding the root device.
*EDIT*
here's the gory details from sysupgrade to boot up. This is upgrading from a recent 4.0 trunk to 4.1. I also tried from factory to 4.1 with same results.
root@wrt1900ac:/tmp# sysupgrade -v openwrt-mvebu-armada-xp-linksys-mamba-squash
fs-sysupgrade.tar
Saving config files...
etc/config/bandwidthd
etc/config/ddns
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/fstab
etc/config/luci
etc/config/network
etc/config/ntpclient
etc/config/openvpn_recipes
etc/config/qos
etc/config/rpcd
etc/config/samba
etc/config/sqm
etc/config/system
etc/config/ubootenv
etc/config/ucitrack
etc/config/uhttpd
etc/config/upnpd
etc/config/wireless
etc/crontabs/root
etc/dnsmasq.conf
etc/dropbear/dropbear_dss_host_key
etc/dropbear/dropbear_rsa_host_key
etc/e2fsck.conf
etc/firewall.user
etc/fw_env.config
etc/group
etc/hosts
etc/inittab
etc/iproute2/rt_tables
etc/opkg.conf
etc/passwd
etc/ppp/chap-secrets
etc/ppp/filter
etc/ppp/options
etc/profile
etc/protocols
etc/rc.local
etc/samba/smb.conf.template
etc/services
etc/shadow
etc/shells
etc/sysctl.conf
etc/sysctl.d/local.conf
etc/sysupgrade.conf
etc/uhttpd.crt
etc/uhttpd.key
etc/uhttpd.key
etc/uhttpd.crt
killall: watchdog: no process killed
Sending TERM to remaining processes ... logd logread rpcd netifd odhcpd crond uhttpd smbd nmbd ntpclient dnsmasq miniupnpd miniud
ubusd
Sending KILL to remaining processes ...
Switching to ramdisk...
[ 378.125640] UBIFS: background thread "ubifs_bgt0_1" stops
[ 378.162193] UBIFS: un-mount UBI device 0, volume 1
Performing system upgrade...
Unlocking kernel1 ...
Writing from <stdin> to kernel1 ...
[ 380.127906] ubi2: attaching mtd5
[ 380.648458] ubi2: scanning is finished
[ 380.674066] ubi2: attached mtd5 (name "rootfs1", size 37 MiB)
[ 380.679855] ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 380.686819] ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 380.693681] ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 380.700673] ubi2: good PEBs: 296, bad PEBs: 0, corrupted PEBs: 0
[ 380.706743] ubi2: user volume: 2, internal volumes: 1, max. volumes count: 128
[ 380.714039] ubi2: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 755108490
[ 380.723159] ubi2: available PEBs: 0, total reserved PEBs: 296, PEBs reserved for bad PEB handling: 20
[ 380.732516] ubi2: background thread "ubi_bgt2d" started, PID 3672
UBI device number 2, total 296 LEBs (37584896 bytes, 35.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
Volume ID 0, size 40 LEBs (5079040 bytes, 4.8 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 29458432
Volume ID 1, size 232 LEBs (29458432 bytes, 28.1 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs_data", alignment1
[ 383.456528] UBIFS: default file-system created
[ 383.463877] UBIFS: background thread "ubifs_bgt2_1" started, PID 3741
[ 383.635877] UBIFS: mounted UBI device 2, volume 1, name "rootfs_data"
[ 383.642528] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 383.651798] UBIFS: FS size: 28188672 bytes (26 MiB, 222 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
[ 383.661699] UBIFS: reserved for root: 1331420 bytes (1300 KiB)
[ 383.667613] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 098B424F-3AC3-40A0-B8C7-0061935F0F9D, small LPT model
[ 383.746453] UBIFS: un-mount UBI device 2, volume 1
[ 383.751637] UBIFS: background thread "ubifs_bgt2_1" stops
sysupgrade successful
[ 383.779769] reboot: Restarting system
BootROM 1.20
Booting from NAND flash
Step 1: First phase of PEX-PIPE Configuration
Step 2: Configure the desire PIN_PHY_GEN
Step 3 QSGMII enable
Step 4: Configure SERDES MUXes
Step 5: Activate the RX High Impedance Mode
Step 6: [PEX-Only] PEX-Main configuration (X4 or X1)
Step 6.2: [PEX-Only] PCI Express Link Capabilities
Step 7: [PEX-X4 Only] To create PEX-Link
Steps 7,8,9,10 and 11
Steps 12: [PEX-Only] Last phase of PEX-PIPE ConfigurationSteps 13: Wait 15ms before checking resultsSteps 14: [PEX-Only] In ord7
step 17: PEX0 pexUnit= 0
** Link is Gen1, check the EP capability
--> 0050
mvPexConfigRead: return addr=0x%x0050
--> 7001
--> 7001
--> A005
--> A005
--> 0010
--> 4C12
Gen2 client!
step 17: PEX1 pexUnit= 0
step 17: PEX2 pexUnit= 0
** Link is Gen1, check the EP capability
--> 0040
mvPexConfigRead: return addr=0x%x0040
--> 5001
--> 5001
--> 7005
--> 7005
--> 0010
--> DC12
Gen2 client!
step 17: PEX3 pexUnit= 0
PEX3 : Detected No Link. Status Reg(0x0004DA64) = 0x00000001
step 17: PEX4 pexUnit= 1
PEX4 : Detected No Link. Status Reg(0x00081A64) = 0x00000001
step 17: PEX5 pexUnit= 1
PEX5 : Detected No Link. Status Reg(0x00085A64) = 0x00000001
step 17: PEX6 pexUnit= 1
PEX6 : Detected No Link. Status Reg(0x00089A64) = 0x00000001
DDR3 Training Sequence - Ver 4.5.DDR3 Training Sequence - Static MC
DDR3 Training Sequence - HW Training Procedure
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
BootROM: Image checksum verification PASSED
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12 (Feb 06 2014 - 17:14:13) Marvell version: v2011.12 2013_Q1.2
Boot version:v1.3.25
Board: RD-AXP-GP rev 1.0
SoC: MV78230 B0
running 2 CPUs
Custom configuration
CPU: Marvell PJ4B (584) v7 (Rev 2) LE
CPU 0
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 250 [MHz]
DDR @ 600 [MHz]
DDR 32Bit Width, FastPath Memory Access
DDR ECC Disabled
DRAM: 256 MiB
Map: Code: 0x0fea7000:0x0ff5e2d4
BSS: 0x0ffefd80
Stack: 0x0f9a6ef8
Heap: 0x0f9a7000:0x0fea7000
NAND: Spansion 1Gb(ID=F101) 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
#### auto_recovery ####
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part == 1
[u_env] get boot_part_ready == 3
auto_recovery enabled:1, boot_part:1, boot_part_ready:3
[boot_count_read] block:0x140000, size:256KB, records:128
[boot_count_read_record] boot_count:1, next_record:35
[boot_count_write] erase:0, auto_recovery->block_offset:0x140000
Updating boot_count ...
[boot_count_write] offset:0x151800 , length:2048
done
PEX 0.0(0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.
boot_end Offset: 0x100000
u_env_off Offset: 0x100000
s_env_off Offset: 0x140000
devinfo Offset: 0x900000
===================
total_badCount: 0
boot_badCount: 0
u_env_badCount: 0
s_env_badCount: 0
buff_badCount: 0
===================
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net: mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run nandboot
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0xa00000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: ARM OpenWrt Linux-4.1.3
Created: 2015-07-25 17:03:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1599493 Bytes = 1.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.1.3 (ctalbot@buildhost) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r46432) ) #1 SMP Sat J5
[ 0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine model: Linksys WRT1900AC
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 10 pages/cpu @cfdd6000 s11584 r8192 d21184 u40960
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devint
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 255092K/262144K available (3218K kernel code, 134K rwdata, 888K rodata, 204K init, 157K bss, 7052K reserv)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc040ae7c (4108 kB)
[ 0.000000] .init : 0xc040b000 - 0xc043e000 ( 204 kB)
[ 0.000000] .data : 0xc043e000 - 0xc045faa4 ( 135 kB)
[ 0.000000] .bss : 0xc045faa4 - 0xc0487100 ( 158 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] Aurora cache controller enabled, 32 ways, 2048 kB
[ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a69ef12
[ 0.000008] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[ 0.000024] clocksource armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.000261] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 0.040066] pid_max: default: 32768 minimum: 301
[ 0.040148] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.040157] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.040482] CPU: Testing write buffer coherency: ok
[ 0.040634] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.041102] Setting up static identity map for 0x8280 - 0x82d8
[ 0.041397] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x2
[ 0.041530] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.042396] Booting CPU 1
[ 0.080057] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.080117] Brought up 2 CPUs
[ 0.080130] SMP: Total of 2 processors activated (2382.23 BogoMIPS).
[ 0.080135] CPU: All CPU(s) started in SVC mode.
[ 0.083233] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.083367] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.083424] pinctrl core: initialized pinctrl subsystem
[ 0.084027] NET: Registered protocol family 16
[ 0.084222] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.110100] cpuidle: using governor ladder
[ 0.141517] Switched to clocksource armada_370_xp_clocksource
[ 0.142246] NET: Registered protocol family 2
[ 0.142712] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.142734] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.142758] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.142797] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.142814] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.142946] NET: Registered protocol family 1
[ 0.143785] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.144193] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.144213] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.144935] io scheduler noop registered
[ 0.144949] io scheduler deadline registered (default)
[ 0.145536] armada-xp-pinctrl f1018000.pin-ctrl: registered pinctrl driver
[ 0.146010] irq: Cannot allocate irq_descs @ IRQ38, assuming pre-allocated
[ 0.146263] irq: Cannot allocate irq_descs @ IRQ70, assuming pre-allocated
[ 0.146701] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[ 0.146716] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.146726] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 0.146736] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.147224] PCI: bus0: Fast back to back transfers disabled
[ 0.147236] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.147248] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.147258] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.147655] PCI: bus1: Fast back to back transfers disabled
[ 0.148090] PCI: bus2: Fast back to back transfers disabled
[ 0.148488] PCI: bus3: Fast back to back transfers disabled
[ 0.148624] pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
[ 0.148637] pci 0000:00:02.0: BAR 8: assigned [mem 0xf8200000-0xf83fffff]
[ 0.148648] pci 0000:00:03.0: BAR 8: assigned [mem 0xf8400000-0xf85fffff]
[ 0.148661] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8007fff 64bit]
[ 0.148681] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.148693] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 0.148708] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf82fffff 64bit pref]
[ 0.148730] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8300000-0xf83fffff 64bit pref]
[ 0.148750] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.148759] pci 0000:00:02.0: bridge window [mem 0xf8200000-0xf83fffff]
[ 0.148774] pci 0000:03:00.0: BAR 0: assigned [mem 0xf8400000-0xf84fffff 64bit pref]
[ 0.148794] pci 0000:03:00.0: BAR 2: assigned [mem 0xf8500000-0xf85fffff 64bit pref]
[ 0.148811] pci 0000:00:03.0: PCI bridge to [bus 03]
[ 0.148821] pci 0000:00:03.0: bridge window [mem 0xf8400000-0xf85fffff]
[ 0.148865] pci 0000:00:01.0: enabling device (0140 -> 0142)
[ 0.148888] pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 0.149049] mv_xor f1060900.xor: Marvell shared XOR driver
[ 0.171600] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.211583] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[ 0.211678] mv_xor f10f0900.xor: Marvell shared XOR driver
[ 0.251582] mv_xor f10f0900.xor: Marvell XOR: ( xor cpy )
[ 0.291582] mv_xor f10f0900.xor: Marvell XOR: ( xor cpy )
[ 0.291767] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.292237] console [ttyS0] disabled
[ 0.312251] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 20, base_baud = 15625000) is a 16550A
[ 0.979371] console [ttyS0] enabled
[ 0.983505] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device
[ 0.991207] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[ 0.997601] nand: AMD/Spansion S34ML01G1
[ 1.001564] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.009159] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
[ 1.016321] Bad block table found at page 65472, version 0x01
[ 1.022428] Bad block table found at page 65408, version 0x01
[ 1.028546] 10 ofpart partitions found on MTD device pxa3xx_nand-0
[ 1.034769] Creating 10 MTD partitions on "pxa3xx_nand-0":
[ 1.040276] 0x000000000000-0x000000100000 : "u-boot"
[ 1.045777] 0x000000100000-0x000000140000 : "u_env"
[ 1.051087] 0x000000140000-0x000000180000 : "s_env"
[ 1.056415] 0x000000900000-0x000000a00000 : "devinfo"
[ 1.061913] 0x000000a00000-0x000003200000 : "kernel1"
[ 1.067452] 0x000000d00000-0x000003200000 : "rootfs1"
[ 1.073015] 0x000003200000-0x000005a00000 : "kernel2"
[ 1.078568] 0x000003500000-0x000005a00000 : "rootfs2"
[ 1.084136] 0x000005a00000-0x000008000000 : "syscfg"
[ 1.089607] 0x000000180000-0x000000900000 : "unused_area"
[ 1.095898] m25p80 spi0.0: mr25h256 (32 Kbytes)
[ 1.101644] libphy: Fixed MDIO Bus: probed
[ 1.105897] libphy: orion_mdio_bus: probed
[ 1.111354] mvneta f1070000.ethernet eth0: Using random mac address 22:aa:e7:1d:1b:d2
[ 1.120473] mvneta f1074000.ethernet eth1: Using random mac address 3a:88:c7:d1:f8:8b
[ 1.133333] NET: Registered protocol family 17
[ 1.137846] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if.
[ 1.150590] 8021q: 802.1Q VLAN Support v1.8
[ 1.154980] Registering SWP/SWPB emulation handler
[ 1.162756] hctosys: unable to open rtc device (rtc0)
[ 1.170593] UBIFS error (pid: 1): cannot open "ubi0:rootfs", error -19VFS: Cannot open root device "(null)" or unknown-block(6
[ 1.183423] Please append a correct "root=" boot option; here are the available partitions:
[ 1.191845] 1f00 1024 mtdblock0 (driver?)
[ 1.196941] 1f01 256 mtdblock1 (driver?)
[ 1.202068] 1f02 256 mtdblock2 (driver?)
[ 1.207162] 1f03 1024 mtdblock3 (driver?)
[ 1.212288] 1f04 40960 mtdblock4 (driver?)
[ 1.217383] 1f05 37888 mtdblock5 (driver?)
[ 1.222525] 1f06 40960 mtdblock6 (driver?)
[ 1.227617] 1f07 37888 mtdblock7 (driver?)
[ 1.232740] 1f08 38912 mtdblock8 (driver?)
[ 1.237828] 1f09 7680 mtdblock9 (driver?)
[ 1.242960] 1f0a 32 mtdblock10 (driver?)
[ 1.248135] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.256467] CPU1: stopping
[ 1.259203] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.1.3 #1
[ 1.265057] Hardware name: Marvell Armada 370/XP (Device Tree)
[ 1.270908] Backtrace:
[ 1.273397] [<c001bb8c>] (dump_backtrace) from [<c001bf14>] (show_stack+0x18/0x1c)
[ 1.280990] r6:00000000 r5:00000000 r4:c044b1f0 r3:dc8ba303
[ 1.286739] [<c001befc>] (show_stack) from [<c0188a8c>] (dump_stack+0x8c/0x9c)
[ 1.293995] [<c0188a00>] (dump_stack) from [<c001e09c>] (handle_IPI+0xe8/0x174)
[ 1.301327] r5:c043c858 r4:00000001
[ 1.304953] [<c001dfb4>] (handle_IPI) from [<c0009480>] (armada_370_xp_handle_irq+0xa8/0xe0)
[ 1.313416] r6:c048062c r5:00000020 r4:00000005 r3:00000020
[ 1.319161] [<c00093d8>] (armada_370_xp_handle_irq) from [<c000a5a0>] (__irq_svc+0x40/0x54)
[ 1.327539] Exception stack(0xcf853f28 to 0xcf853f70)
[ 1.332617] 3f20: cf853f70 fffffffa 3b9aca00 00000000 4a8350a0 00000000
[ 1.340830] 3f40: 0049b380 00000000 00000002 cfde19d0 c043b204 cf853fa4 0000001a cf853f70
[ 1.349038] 3f60: 00000006 c0265290 20000153 ffffffff
[ 1.354107] r10:c043b204 r9:cfde19d0 r8:00000002 r7:cf853f5c r6:ffffffff r5:20000153
[ 1.362036] r4:c0265290
[ 1.364610] [<c0265208>] (cpuidle_enter_state) from [<c0265434>] (cpuidle_enter+0x1c/0x20)
[ 1.372900] r10:c043b204 r9:c043d3c0 r8:c043c9c8 r7:c045aab4 r6:cfde19d0 r5:c039e07c
[ 1.380828] r4:c04404d8
[ 1.383399] [<c0265418>] (cpuidle_enter) from [<c0054ba8>] (cpu_startup_entry+0x1cc/0x28c)
[ 1.391700] [<c00549dc>] (cpu_startup_entry) from [<c001dd84>] (secondary_start_kernel+0x134/0x13c)
[ 1.400773] r7:c045fd20
[ 1.403337] [<c001dc50>] (secondary_start_kernel) from [<000095ac>] (0x95ac)
[ 1.410408] r5:00000015 r4:0f83c06a
[ 1.414032] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)(Last edited by tusc on 25 Jul 2015, 20:05)
@tusc
I'm running latest kernels in order to backport improvements to CC. I advise you run CC for the time being. Goodies are on their way.
nitroshift
RC2
use these two custom firewall rules to get a grip on ssh brute force attacks...
iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --set
iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --update --seconds 30 --hitcount 1 -j DROPMake sure that you have the iptables-mod-conntrack-extra and kmod-ipt-conntrack-extra packages installed.
(Last edited by gufus on 25 Jul 2015, 22:02)
RC2
use these two custom firewall rules to get a grip on ssh brute force attacks...
iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --set iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --update --seconds 30 --hitcount 1 -j DROPMake sure that you have the iptables-mod-conntrack-extra and kmod-ipt-conntrack-extra packages installed.
Due to the fw3 implementation, if using OpenWRT, INPUT needs to be delegate_input.
You can print the fw3 iptables rules via fw3 print to see how it routes traffic
Utilizing normal chain names on OpenWRT is a recipe for disaster, as it bypasses the security of how fw3 routes traffic, or the rules won't be applied at all.
For example, adding a rule to the Input Chain without specifying '1' would add it below the only rule under the Input chain (forward all traffic to delegate_input), meaning the rule would never be activated. Adding the rule as '1' would bypass the forwarding of traffic to delegate_input, thereby bypassing the firewall all together for inbound traffic.
Another way:
Set Rate Limit
iptables -N rate_limit
iptables -A rate_limit -p tcp --dport 22 -m limit --limit 3/min --limit-burst 3 -j DROP
iptables -A rate_limit -p tcp --dport 23 -m limit --limit 3/min --limit-burst 3 -j DROP
iptables -A rate_limit -p tcp --dport 1194 -m limit --limit 3/min --limit-burst 3 -j DROP
iptables -A rate_limit -p udp --dport 1194 -m limit --limit 3/min --limit-burst 3 -j DROP
iptables -A rate_limit -p ICMP --icmp-type echo-request -m limit --limit 3/sec -j ACCEPT
iptables -A rate_limit ! -p ICMP -j LOG --log-prefix " Connection dropped "
iptables -A rate_limit -p tcp -j REJECT --reject-with tcp-reset
iptables -A rate_limit -p udp -j REJECT --reject-with icmp-port-unreachable
iptables -A rate_limit -j DROPApply Rate Limit
iptables -I delegate_input -p ICMP --icmp-type echo-request -j rate_limit
iptables -I delegate_input -p tcp --dport 22 -m state --state NEW -j rate_limit
iptables -I delegate_input -p tcp --dport 23 -m state --state NEW -j rate_limit
iptables -I delegate_input -p tcp --dport 1194 -m state --state NEW -j rate_limit
iptables -I delegate_input -p udp --dport 1194 -m state --state NEW -j rate_limit(Last edited by JW0914 on 26 Jul 2015, 04:53)
Everything has been working fine for 3 days uptime. Then a self detected stall on cpu1 a few times then it happened on 0 also repeating. Cpu was getting hot so I rebooted the router. Anyone want the log file? I am sure it was on its way to going down wifi was still up so I am not sure it is the either of the 2 big problems. ver r46432
(Last edited by northbound on 26 Jul 2015, 05:21)
Sorry, posts 6651 to 6650 are missing from our archive.