I am totally unsure if this is the right part of the forum, so my apologies for perhaps not placing it right.
To the actual question. I am quite upset with my Zyxel Armor X1 (WAP6806) AP.
I’ve started poking it, and will continue to do so until I trash it, or get another firmware on it if possible. But to get there, I need to figure out some parts…
Not first, but the reason for the question - how do I get the amount of blocks, or calculate the size of the ramdrive and the storage for the firmware - without the normal binaries?
This means, I have a layout of proc that is not in my head normally populated…
(perhaps it is, but I am to n00b to get it right).
The heads up here is that according to the rest of the internet, it’s a openWRT fork-ish attempt by zyxel (let’s just say I am not that impressed with the garbage the left in).
Here’s what I have started to map out.
# from /proc -
# pwd
/proc
# ls
13482 6002 1683 1074 990 45 30 26 22 13 9 5 self fs sys mtd timer_list pagetypeinfo slabinfo cpuinfo meminfo softirqs diskstats
12324 3840 1604 1033 447 38 29 25 16 12 8 3 mounts driver irq execdomains modules vmstat filesystems devices stat kcore partitions
6223 1685 1395 1028 139 37 28 24 15 11 7 2 net tty misc ioports kallsyms zoneinfo locks interrupts uptime kmsg mt7621
6100 1684 1385 1021 47 31 27 23 14 10 6 1 sysvipc bus scsi iomem buddyinfo vmallocinfo cmdline loadavg version crypto
#
# cat diskstats
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
1 2 ram2 0 0 0 0 0 0 0 0 0 0 0
1 3 ram3 0 0 0 0 0 0 0 0 0 0 0
1 4 ram4 0 0 0 0 0 0 0 0 0 0 0
1 5 ram5 0 0 0 0 0 0 0 0 0 0 0
1 6 ram6 0 0 0 0 0 0 0 0 0 0 0
1 7 ram7 0 0 0 0 0 0 0 0 0 0 0
1 8 ram8 0 0 0 0 0 0 0 0 0 0 0
1 9 ram9 0 0 0 0 0 0 0 0 0 0 0
1 10 ram10 0 0 0 0 0 0 0 0 0 0 0
1 11 ram11 0 0 0 0 0 0 0 0 0 0 0
1 12 ram12 0 0 0 0 0 0 0 0 0 0 0
1 13 ram13 0 0 0 0 0 0 0 0 0 0 0
1 14 ram14 0 0 0 0 0 0 0 0 0 0 0
1 15 ram15 0 0 0 0 0 0 0 0 0 0 0
31 0 mtdblock0 0 0 0 0 0 0 0 0 0 0 0
31 1 mtdblock1 0 0 0 0 0 0 0 0 0 0 0
31 2 mtdblock2 0 0 0 0 0 0 0 0 0 0 0
31 3 mtdblock3 0 0 0 0 0 0 0 0 0 0 0
31 4 mtdblock4 0 0 0 0 0 0 0 0 0 0 0
31 5 mtdblock5 0 0 0 0 0 0 0 0 0 0 0
31 6 mtdblock6 0 0 0 0 0 0 0 0 0 0 0
31 7 mtdblock7 0 0 0 0 0 0 0 0 0 0 0
31 8 mtdblock8 0 0 0 0 0 0 0 0 0 0 0
31 9 mtdblock9 0 0 0 0 0 0 0 0 0 0 0
# cat partitions
major minor #blocks name
31 0 131072 mtdblock0
31 1 1024 mtdblock1
31 2 1024 mtdblock2
31 3 1024 mtdblock3
31 4 1024 mtdblock4
31 5 32768 mtdblock5
31 6 32768 mtdblock6
31 7 1024 mtdblock7
31 8 16384 mtdblock8
31 9 44032 mtdblock9
#
# cat mounts
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
none /var ramfs rw,relatime 0 0
none /etc ramfs rw,relatime 0 0
none /tmp ramfs rw,relatime 0 0
none /media ramfs rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
none /dev/pts devpts rw,relatime,mode=600 0 0
#
# cd driver
# ls
nand
# cat nand
ID: 0xc2f1, total size: 128MiB
Current working in polling mode
#
So, I guess I did manage to grab the NAND-size anyway - yay for digging while typing…
Could this mean, that I do have a 128mb nand flash, and the following memory where the ramdrive lives?
# free
total used free shared buffers
Mem: 58928 40452 18476 0 0
Swap: 0 0 0
Total: 58928 40452 18476
# Has anyone any pointers on this one in terms of if I could possibly just link and lift in binaries in some way?