{"id":204,"date":"2015-07-21T14:01:56","date_gmt":"2015-07-21T18:01:56","guid":{"rendered":"http:\/\/72.167.111.237\/wpecsdump\/?page_id=204"},"modified":"2015-07-21T14:01:56","modified_gmt":"2015-07-21T18:01:56","slug":"part-i-how-can-i-break-this","status":"publish","type":"page","link":"https:\/\/www.ecsdump.net\/?page_id=204","title":{"rendered":"PART I: How Can I Break This?"},"content":{"rendered":"<p>Because of some storm damage,\u00a0I had to replace some items in my home network. I decided to rethink the entire setup. For years I have run my cable connection though an old AMD K6 system acting as a gateway system. This system ran OS\/2, had 2 network cards, used Injoy FW for NAT, Apache (with php &amp; mysql), Peer, and a ftp server. I moved to a Linksys 54G router as the gateway and purchased an ADS NAS Drive Kit to replace the other components. As far as Apache, I just moved that stuff to my external site.<\/p>\n<p>The NAS runs an embedded version of Linux using a\u00a0<a class=\"ext\" href=\"http:\/\/en.wikipedia.org\/wiki\/PMC-Sierra\">PMC-Sierra<\/a>\u00a0MSP (Multi Service Processor)\u00a0<a class=\"missingpage\" title=\"Create this page\" href=\"http:\/\/www.mgreene.org\/wikka\/SoC\/edit\">SoC<\/a>\u00a0(acquired from Brecis Communications). Of course I had to disassemble the unit and found that the MSP is a MSP2006 MIPS CPU with the following specs:<\/p>\n<p>Core: MIPS 4Km<br \/>Speed: 167 MHz Max<br \/>Interfaces: (2) 10\/100, PCI SDRAM, local bus, UARTs, SPI\/MPI 2-wire serial<\/p>\n<p>The\u00a0<a class=\"ext\" href=\"http:\/\/www.pmc-sierra.com\/products\/details\/msp2006\/\">PMC site has additional CPU specs<\/a>. This does not have a Memory Management Unit (MMU). Additionally, the IDE controller is an\u00a0<a class=\"ext\" href=\"http:\/\/www.ite.com.tw\/product_info\/PC\/Brief-IT8211_2.asp\">ITE 8211F<\/a>. Mosel Vitelic Corp 256Mbit (32MByte) SDRAM 3.3 VOLT, TSOP II \/ SOC BGA \/ WBGA PACKAGE 16M X 16, 32M X 8, 64M X 4 means it contains 64 meg of RAM from my readings.\u00a0<\/p>\n<p>I also found that the ADS unit is an OEM version, maybe with a couple of updated components, of the follow units:<\/p>\n<p>Allnet all6200<br \/>Flepo f6200<br \/><a class=\"ext\" href=\"http:\/\/www.longshine.de\/longshine\/p_storage.php?lang=eng\">Longshine 8210 \/ 8220<\/a><br \/><a class=\"ext\" href=\"http:\/\/www.netronixinc.com\/product_NH220.htm\">Netronix NH-220 (the ADS docs were named Netronix)<\/a><br \/><a class=\"ext\" href=\"http:\/\/www.hawkingtech.com\/support\/details.php?CatID=33&amp;FamID=117&amp;ProdID=242\">Hawking Net-Stor Network Storage Center HNAS1<\/a><\/p>\n<p>A couple quick checks of the firmware updates shows the headers:<\/p>\n<div class=\"code\">\n<pre>ADS 1.04 Firmware Update\nMAGICNUM=ADxO23spFc0Mn6li8SCq9kEr\nPRODUCT_ID=NH220\nCUSTOMER=ADS\nVERSION=v1.04(06-13-2006)\nLongshine Nobrand Frimware Update\nMAGICNUM=ADxO23spFc0Mn6li8SCq9kEr\nPRODUCT_ID=NH220\nCUSTOMER=NONBRAND\nVERSION=v1.03(06-30-2005)<\/pre>\n<\/div>\n<p>Ok, so from this I think one can conclude that the Longshine 8220 and ADS NAS-806-EF are all relabeled Netronix NH-220 units. From what I have read the old Longshine 8210, Hawking, Allnet units are 32 meg RAM and the 8220 and ADS units are 64 meg RAM units. I also found other units which seemed similar, but also had USB ports.<\/p>\n<p>A portscan showed port 24 and when I used telnet to connect the I received the\u00a0message\u00a0I had read about:<\/p>\n<div class=\"code\">\n<pre>TELNET] CONNECT (nasdrive\/192.168.1.2)\n***\n*** CONNECT TO 192.168.1.2:24\n*** date 08-26-07\n*** time 15:03:10\n***\n1452.14 1361.72\n\/etc\/issue                www.brecis.com                28 July 2003\n\t    Welcome to linux 2.4.20-br251 by BRECIS (Release 2.5.1)\n  Brecis linux incorporates changes from kernel.org, and uclinux.org as well\n  as locally derived features to provide a robust environment for the embedded\n  BRECIS mips chip.  Almost any program that can run with less than 64k of\n  stack should work.  Most all features of the linux kernel are provided.\n  The \"c\" runtime library originated at uclibc.org.  One nice feature is\n  that the fork() system call works (although slowly) for this MMU-less chip.\n  For more information on the operating system please visit these sites:\n  \thttp:\/\/www.uclinux.org\n\thttp:\/\/www.kernel.org\n\thttp:\/\/www.uclibc.org\n  On the CDROM distribution, see files:\n\tREADME\n\tCHANGES\t\tAccumulated change log.\n\tRELEASE-NOTES\tAdditional notes, and short FAQ.\n\tuClinux\/README\tInstructions for building\/changing things.\n[TELNET] INFO: DISCONNECTED\n***\n*** DISCONNECT\n*** time 15:03:10\n***<\/pre>\n<\/div>\n<p>Ok, I figured at this point I did not spend money much on this thing so I altered the\u00a0<a class=\"ext\" href=\"http:\/\/www.opennas.info\/\">OpenNAS<\/a>\u00a0firmware header and gave it a try! I first tried the LCS8220_402-zap3a_253.bin version from 2005 which with the altered header worked.\u00a0<\/p>\n<div class=\"code\">\n<pre>OpenNAS -  LCS8220_402-zap3a_253.bin file from\nMAGICNUM=ADxO23spFc0Mn6li8SCq9kEr\nPRODUCT_ID=NH220\nCUSTOMER=LONGSHINE                                 &lt;== Changed to ADS using Hexedit\/2\nVERSION=v4.02(24-02-2005)-ext3-zap3a<\/pre>\n<\/div>\n<p>I flashed through the web interface and once complete I pressed the reset for factory defaults. One issue I ran into was that my linksys router is 192.168.1.1 and the NAS started as 192.168.1.1. Once this conflict was cleared up I had the NAS up and running. It looked a lot like the ADS version with web interface, however, I was able to telnet into it and look around. Just for information, the default root password is all6200.<\/p>\n<p>Unfortunately, like the ADS firmware this version did not support EAs. So, I decided to go one step further. Since LCS8220_402-zap3a_253.bin was from 2005, I set about to flash the NAS to openNAS-0.9d-64MB.bin (25 Feb 2007).\u00a0<\/p>\n<p>If the previous flash was living on the edge then the next step was even worse. The openNAS does not have the header to edit, rather you have to flash via tftp or a special serial cable. The developer did have instructions as to how to add a header:<\/p>\n<div class=\"code\">\n<pre>dd if=original_firmware.bin of=header.bin bs=512 count=1\ncat openNAS-0.9d.bin &gt;&gt; header.bin<\/pre>\n<\/div>\n<p>The dd command strips the header of original_firmware.bin, which I used an ADS fireware update, to header.bin. Next, the the cat command combines the header and openNAS file. I assume one should be able to flash from this point. However, I found that with the old v4.02 firmware installed I could no longer flash, not to openNAS or back to ADS firmware. At this point I did think I was screwed!\u00a0<\/p>\n<p>I found the script that the NAS ran for flashing which I modified to just do a direct flash. It was something like this:<\/p>\n<p>dd if=\/mnt\/openNAS-0.9d.bin of=\/dev\/mtdblock<\/p>\n<p>I was sure the NAS would be a brick once this completed. Once the dd command had completed, I typed reboot at the prompt and did the factory reset. It seems that a bug in openNAS turns the NAS power light on and then it goes out, after that &#8220;oh shit&#8217; moment I realized the lan light was flashing so it was running. Also, openNAS does not assign a static IP to the NAS, but rather uses dhcp. Last, the http server does not start. After figuring all this out, and seeing I had not turned the NAS into a brick, I telnet&#8217;d into the box (root pw:all6200). Here is what I saw:\u00a0<\/p>\n<div class=\"code\">\n<pre>BusyBox v1.4.1 (2007-02-25 01:26:42 CET) Built-in shell (ash)\nEnter 'help' for a list of built-in commands.<\/pre>\n<\/div>\n<p>The \/var\/log\/messages file:<\/p>\n<pre>Nov 30 00:00:13 openNAS syslog.info syslogd started: BusyBox v1.4.1\nNov 30 00:00:13 openNAS user.notice kernel: klogd started: BusyBox v1.4.1 (2007-02-25 01:26:42 CET)\nNov 30 00:00:13 openNAS user.warn kernel: CPU revision is: 0001830a\nNov 30 00:00:13 openNAS user.warn kernel: Primary instruction cache 16kb, linesize 16 bytes (4 ways)\nNov 30 00:00:13 openNAS user.warn kernel: Primary data cache 16kb, linesize 16 bytes (4 ways)\nNov 30 00:00:13 openNAS user.warn kernel:\nNov 30 00:00:13 openNAS user.warn kernel:\nNov 30 00:00:13 openNAS user.warn kernel:\nNov 30 00:00:13 openNAS user.warn kernel: Linux version 2.4.20-br26 (christian@debianMobile) (gcc version 3.2 20030604 (BRECIS uClinux)) #2 So 25. Feb 02:12:18 CET 2007\nNov 30 00:00:13 openNAS user.warn kernel: Determined physical RAM map:\nNov 30 00:00:13 openNAS user.warn kernel:  memory: 00001000 @ 00000000 (reserved)\nNov 30 00:00:13 openNAS user.warn kernel:  memory: 000ff000 @ 00001000 (ROM data)\nNov 30 00:00:13 openNAS user.warn kernel:  memory: 00403000 @ 00100000 (reserved)\nNov 30 00:00:14 openNAS user.warn kernel:  memory: 03afd000 @ 00503000 (usable)\nNov 30 00:00:14 openNAS user.warn kernel: On node 0 totalpages: 16384\nNov 30 00:00:14 openNAS user.warn kernel: zone(0): 16384 pages.\nNov 30 00:00:14 openNAS user.warn kernel: zone(1): 0 pages.\nNov 30 00:00:14 openNAS user.warn kernel: zone(2): 0 pages.\nNov 30 00:00:14 openNAS user.warn kernel: Kernel command line:  console=ttyS0,57600\nNov 30 00:00:14 openNAS user.warn kernel: calculating r4koff... 000cb735(833333)\nNov 30 00:00:14 openNAS user.warn kernel: CPU frequency 166.66 MHz\nNov 30 00:00:14 openNAS user.warn kernel: Calibrating delay loop... 166.29 BogoMIPS\nNov 30 00:00:14 openNAS user.warn kernel: Memory: 59688k\/60404k available (1781k kernel code, 716k reserved, 83k data, 84k init)\nNov 30 00:00:14 openNAS user.info kernel: Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)\nNov 30 00:00:14 openNAS user.info kernel: Inode cache hash table entries: 4096 (order: 3, 32768 bytes)\nNov 30 00:00:14 openNAS user.warn kernel: Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)\nNov 30 00:00:14 openNAS user.warn kernel: Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)\nNov 30 00:00:14 openNAS user.warn kernel: Page cache: 64MB memory, maximum pages = 5120, maximum inactive pages = 300\nNov 30 00:00:14 openNAS user.warn kernel: Page-cache hash table entries: 16384 (order: 4, 65536 bytes)\nNov 30 00:00:14 openNAS user.warn kernel: POSIX conformance testing by UNIFIX\nNov 30 00:00:14 openNAS user.warn kernel: pcibios_init: assign resources, scan the buses.\nNov 30 00:00:14 openNAS user.warn kernel: Scanning bus 00\nNov 30 00:00:14 openNAS user.warn kernel: Found 00:80 [1283\/8211] 000180 00\nNov 30 00:00:14 openNAS user.warn kernel: Fixups for bus 00\nNov 30 00:00:14 openNAS user.warn kernel: Bus scan for 00 returning with max=00\nNov 30 00:00:14 openNAS user.info kernel: Linux NET4.0 for Linux 2.4\nNov 30 00:00:14 openNAS user.info kernel: Based upon Swansea University Computer Society NET3.039\nNov 30 00:00:14 openNAS user.warn kernel: Initializing RT netlink socket\nNov 30 00:00:14 openNAS user.info kernel: Journalled Block Device driver loaded\nNov 30 00:00:14 openNAS user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).\nNov 30 00:00:14 openNAS user.info kernel: squashfs: version 3.0 (2006\/03\/15) Phillip Lougher\nNov 30 00:00:14 openNAS user.info kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled\nNov 30 00:00:14 openNAS user.info kernel: ttyS00 at 0xbc000100 (irq = 19) is a 16550A\nNov 30 00:00:14 openNAS user.info kernel: ttyS01 at 0xb8400030 (irq = 13) is a 16550A\nNov 30 00:00:14 openNAS user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 6.31\nNov 30 00:00:14 openNAS user.warn kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx\nNov 30 00:00:14 openNAS user.warn kernel: IT8211: IDE controller on PCI bus 00 dev 80\nNov 30 00:00:14 openNAS user.warn kernel: IT8211: chipset revision 17\nNov 30 00:00:14 openNAS user.warn kernel: IT8211: not 100% native mode: will probe irqs later\nNov 30 00:00:14 openNAS user.warn kernel: IT8212: wait 5 seconds for hard disk ready before initialize IT8212 after cold boot.\nNov 30 00:00:14 openNAS user.warn kernel: ..... Done\nNov 30 00:00:14 openNAS user.warn kernel:     ide0: BM-DMA at 0xb9001030-0xb9001037, BIOS settings: hda:pio, hdb:pio\nNov 30 00:00:14 openNAS user.warn kernel:     ide1: BM-DMA at 0xb9001038-0xb900103f, BIOS settings: hdc:pio, hdd:pio\nNov 30 00:00:14 openNAS user.warn kernel: hda: MAXTOR STM3320620A, ATA DISK drive\nNov 30 00:00:14 openNAS user.warn kernel: hda: IRQ probe failed (0x0)\nNov 30 00:00:14 openNAS user.warn kernel: hdb: IRQ probe failed (0x0)\nNov 30 00:00:14 openNAS user.warn kernel: hdb: IRQ probe failed (0x0)\nNov 30 00:00:14 openNAS user.warn kernel: ide0 at 0xb9001008-0xb900100f,0xb9001012 on irq 1\nNov 30 00:00:14 openNAS user.warn kernel: blk: queue 804fd6a8, I\/O limit 4095Mb (mask 0xffffffff)\nNov 30 00:00:14 openNAS user.info kernel: hda: 625142448 sectors (320073 MB) w\/16384KiB Cache, CHS=38913\/255\/63, UDMA(33)\nNov 30 00:00:14 openNAS user.info kernel: Partition check:\nNov 30 00:00:14 openNAS user.info kernel:  hda: hda1\nNov 30 00:00:14 openNAS user.info kernel: brecismspeth.c:v1.97-zap1, Apr 16, 2005 BRECIS Communications, Corp., www.brecis.com\nNov 30 00:00:14 openNAS user.warn kernel: Blkmem copyright 1998,1999 D. Jeff Dionne\nNov 30 00:00:14 openNAS user.warn kernel: Blkmem copyright 1998 Kenneth Albanowski\nNov 30 00:00:14 openNAS user.warn kernel: Blkmem 1 disk images:\nNov 30 00:00:14 openNAS user.warn kernel: 0: 802EB060-5C6EB85F [VIRTUAL A02EB060-7C6EB85F] (RO)\nNov 30 00:00:14 openNAS user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 1024K size 1024 blocksize\nNov 30 00:00:14 openNAS user.info kernel: loop: loaded (max 8 devices)\nNov 30 00:00:14 openNAS user.info kernel: Copy engine driver installed\nNov 30 00:00:14 openNAS user.info kernel: nh200_gpio: Started polling GPIO pins.\nNov 30 00:00:14 openNAS user.notice kernel: b_flash flash device: bfc00000 at 400000\nNov 30 00:00:14 openNAS user.notice kernel:  Amd\/Fujitsu Extended Query Table v1.1 at 0x0040\nNov 30 00:00:14 openNAS user.notice kernel: number of CFI chips: 1\nNov 30 00:00:14 openNAS user.notice kernel: cfi_cmdset_0002: Disabling fast programming due to code brokenness.\nNov 30 00:00:14 openNAS user.notice kernel: Creating 6 MTD partitions on \"flash0\":\nNov 30 00:00:14 openNAS user.notice kernel: 0x00000000-0x00002000 : \"PMON-BOOT1\"\nNov 30 00:00:14 openNAS user.notice kernel: 0x00002000-0x00004000 : \"Boot config\"\nNov 30 00:00:14 openNAS user.notice kernel: 0x00004000-0x00006000 : \"POST\"\nNov 30 00:00:14 openNAS user.notice kernel: 0x00006000-0x0000c000 : \"Linux-Config\"\nNov 30 00:00:14 openNAS user.notice kernel: 0x00010000-0x00040000 : \"PMON-BOOT2\"\nNov 30 00:00:14 openNAS user.notice kernel: 0x00040000-0x00400000 : \"Linux-Image\"\nNov 30 00:00:14 openNAS user.info kernel: NET4: Linux TCP\/IP 1.0 for NET4.0\nNov 30 00:00:14 openNAS user.info kernel: IP Protocols: ICMP, UDP, TCP\nNov 30 00:00:14 openNAS user.info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes\nNov 30 00:00:14 openNAS user.info kernel: TCP: Hash tables configured (established 4096 bind 4096)\nNov 30 00:00:14 openNAS user.info kernel: NET4: Unix domain sockets 1.0\/SMP for Linux NET4.0.\nNov 30 00:00:14 openNAS user.info kernel: NET4: AppleTalk 0.18a for Linux NET4.0\nNov 30 00:00:14 openNAS user.warn kernel: FAT: bogus logical sector size 16418\nNov 30 00:00:14 openNAS user.warn kernel: FAT: bogus logical sector size 16418\nNov 30 00:00:14 openNAS user.info kernel:  find a reiserfs filesystem on (dev 1f:00, block 64, size 1024)\nNov 30 00:00:14 openNAS user.warn kernel: read_super_block: can't find a reiserfs filesystem on (dev 1f:00, block 8, size 1024)\nNov 30 00:00:14 openNAS user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.\nNov 30 00:00:14 openNAS user.warn kernel: Freeing prom memory: 1020kb freed\nNov 30 00:00:14 openNAS user.warn kernel: Freeing unused kernel memory: 84k freed [802c0000-802d5000]\nNov 30 00:00:14 openNAS user.warn kernel: Algorithmics\/MIPS FPU Emulator v1.5\nNov 30 00:00:14 openNAS user.info kernel: kjournald starting.  Commit interval 5 seconds\nNov 30 00:00:14 openNAS user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal\nNov 30 00:00:14 openNAS user.info kernel: EXT3-fs: mounted filesystem with writeback data mode.\nNov 30 00:00:17 openNAS user.info kernel: eth0: Using PHY address 1 with base address b8600000\nNov 30 00:00:17 openNAS user.info kernel: eth0: PHY is set for Auto-Negotiation\nNov 30 00:00:17 openNAS user.info kernel: eth0: AUTO NEGOTIATION COMPLETE\nNov 30 00:00:17 openNAS user.info kernel: eth0: PHY is in AUTO NEGOTIATION MODE\nNov 30 00:00:17 openNAS user.info kernel: eth0: PHY is set for 100Mbps Full Duplex\nNov 30 00:00:24 openNAS daemon.warn thttpd[147]: logfile is not within the chroot tree, you will not be able to re-open it\nNov 30 00:00:24 openNAS daemon.notice thttpd[147]: thttpd\/2.25b 29dec2003 starting on port 8080\nNov 30 00:00:24 openNAS daemon.warn thttpd[147]: initgroups - No such file or directory\nNov 30 00:00:24 openNAS daemon.info init: Starting pid 152, console \/dev\/ttyS0: '\/bin\/sh'\nNov 30 00:00:30 openNAS authpriv.info dropbear[154]: Child connection from 192.168.1.34:59109\nNov 30 00:00:31 openNAS user.err syslog: execv \/mnt\/user\/sbin\/smbd: No such file or directory\nNov 30 00:00:31 openNAS user.err syslog: execv \/mnt\/user\/sbin\/smbd: No such file or directory\nNov 30 00:00:54 openNAS auth.info login[161]: root login on 'stderr'\nNov 30 00:01:01 openNAS authpriv.info dropbear[154]: exit before auth: Failed to get remote version\nNov 30 01:01:23 openNAS daemon.notice thttpd[163]: thttpd\/2.25b 29dec2003 starting on port 80\nNov 30 01:01:23 openNAS daemon.warn thttpd[163]: started as root without requesting chroot(), warning only\nNov 30 01:01:27 openNAS daemon.info thttpd[163]: 192.168.1.34 - - \"UNKNOWN  UNKNOWN\" 400 0 \"\" \"\"\nNov 30 00:01:27 openNAS authpriv.info dropbear[165]: Child connection from 192.168.1.34:60134\nNov 30 00:01:27 openNAS user.err syslog: execv \/mnt\/user\/sbin\/smbd: No such file or directory\nNov 30 00:01:28 openNAS user.err syslog: execv \/mnt\/user\/sbin\/smbd: No such file or directory\nNov 30 00:01:28 openNAS authpriv.info dropbear[165]: exit before auth: Failed to get remote version\nNov 30 01:01:34 openNAS daemon.info thttpd[163]: 192.168.1.34 - - \"GET \/ HTTP\/1.1\" 304 0 \"\" \"Mozilla\/5.0 (OS\/2; U; Warp 4.5; en-US; rv:1.8.1.5) Gecko\/20070721 eSeaMonkey\/1.1.3\"\nNov 30 01:01:37 openNAS daemon.info thttpd[163]: 192.168.1.34 - - \"GET \/ HTTP\/1.1\" 304 0 \"\" \"Mozilla\/5.0 (OS\/2; U; Warp 4.5; en-US; rv:1.8.1.5) Gecko\/20070721 eSeaMonkey\/1.1.3\"\nNov 30 01:01:42 openNAS daemon.info thttpd[163]: 192.168.1.34 - - \"GET \/reboot HTTP\/1.1\" 404 0 \"http:\/\/192.168.1.30\/\" \"Mozilla\/5.0 (OS\/2; U; Warp 4.5; en-US; rv:1.8.1.5) Gecko\/20070721 eSeaMonkey\/1.1.3\"\nNov 30 01:01:47 openNAS daemon.info thttpd[163]: 192.168.1.34 - - \"GET \/expand HTTP\/1.1\" 404 0 \"http:\/\/192.168.1.30\/\" \"Mozilla\/5.0 (OS\/2; U; Warp 4.5; en-US; rv:1.8.1.5) Gecko\/20070721 eSeaMonkey\/1.1.3\"\nNov 30 00:10:55 openNAS auth.info login[172]: root login on 'stderr'\nNov 30 00:14:01 openNAS daemon.info thttpd[147]: up 817 seconds, stats for 817 seconds:\nNov 30 00:14:01 openNAS daemon.info thttpd[147]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 0 httpd_conns allocated\nNov 30 00:14:01 openNAS daemon.info thttpd[147]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 00:14:01 openNAS daemon.info thttpd[147]:   fdwatch - 166 polls (0.203182\/sec)\nNov 30 00:14:01 openNAS daemon.info thttpd[147]:   timers - 3 allocated, 3 active, 0 free\nNov 30 00:14:01 openNAS daemon.notice thttpd[147]: exiting due to signal 15\nNov 30 01:14:01 openNAS daemon.info thttpd[163]: up 758 seconds, stats for 758 seconds:\nNov 30 01:14:01 openNAS daemon.info thttpd[163]:   thttpd - 5 connections (0.00659631\/sec), 1 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 01:14:01 openNAS daemon.info thttpd[163]:   libhttpd - 31 strings allocated, 7600 bytes (245.161 bytes\/str)\nNov 30 01:14:01 openNAS daemon.info thttpd[163]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 01:14:01 openNAS daemon.info thttpd[163]:   fdwatch - 168 polls (0.221636\/sec)\nNov 30 01:14:01 openNAS daemon.info thttpd[163]:   timers - 3 allocated, 3 active, 0 free\nNov 30 01:14:01 openNAS daemon.notice thttpd[163]: exiting due to signal 15\nNov 30 01:14:16 openNAS daemon.warn thttpd[187]: logfile is not within the chroot tree, you will not be able to re-open it\nNov 30 01:14:17 openNAS daemon.notice thttpd[187]: thttpd\/2.25b 29dec2003 starting on port 8080\nNov 30 01:14:17 openNAS daemon.warn thttpd[187]: initgroups - No such file or directory\nNov 30 01:16:16 openNAS daemon.info thttpd[187]: spawned indexing process 192 for directory '.'\nNov 30 00:20:13 openNAS syslog.info -- MARK --\nNov 30 00:40:13 openNAS syslog.info -- MARK --\nNov 30 01:00:13 openNAS syslog.info -- MARK --\nNov 30 02:14:22 openNAS daemon.info thttpd[187]: up 3605 seconds, stats for 3605 seconds:\nNov 30 02:14:22 openNAS daemon.info thttpd[187]:   thttpd - 2 connections (0.000554785\/sec), 1 max simultaneous, 25000 bytes (6.93481\/sec), 2 httpd_conns allocated\nNov 30 02:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 02:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 02:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 737 polls (0.204438\/sec)\nNov 30 02:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 01:20:13 openNAS syslog.info -- MARK --\nNov 30 01:40:13 openNAS syslog.info -- MARK --\nNov 30 02:00:13 openNAS syslog.info -- MARK --\nNov 30 03:14:22 openNAS daemon.info thttpd[187]: up 7205 seconds, stats for 3600 seconds:\nNov 30 03:14:22 openNAS daemon.info thttpd[187]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 03:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 03:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 03:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 730 polls (0.202778\/sec)\nNov 30 03:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 02:20:13 openNAS syslog.info -- MARK --\nNov 30 02:40:13 openNAS syslog.info -- MARK --\nNov 30 03:00:13 openNAS syslog.info -- MARK --\nNov 30 04:14:22 openNAS daemon.info thttpd[187]: up 10805 seconds, stats for 3600 seconds:\nNov 30 04:14:22 openNAS daemon.info thttpd[187]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 04:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 04:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 04:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 730 polls (0.202778\/sec)\nNov 30 04:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 03:20:13 openNAS syslog.info -- MARK --\nNov 30 03:40:13 openNAS syslog.info -- MARK --\nNov 30 04:00:13 openNAS syslog.info -- MARK --\nNov 30 05:14:22 openNAS daemon.info thttpd[187]: up 14405 seconds, stats for 3600 seconds:\nNov 30 05:14:22 openNAS daemon.info thttpd[187]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 05:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 05:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 05:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 730 polls (0.202778\/sec)\nNov 30 05:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 04:20:13 openNAS syslog.info -- MARK --\nNov 30 04:40:13 openNAS syslog.info -- MARK --\nNov 30 05:00:13 openNAS syslog.info -- MARK --\nNov 30 06:14:22 openNAS daemon.info thttpd[187]: up 18005 seconds, stats for 3600 seconds:\nNov 30 06:14:22 openNAS daemon.info thttpd[187]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 06:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 06:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 06:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 730 polls (0.202778\/sec)\nNov 30 06:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 05:20:13 openNAS syslog.info -- MARK --\nNov 30 05:40:13 openNAS syslog.info -- MARK --\nNov 30 06:00:13 openNAS syslog.info -- MARK --\nNov 30 06:02:09 openNAS auth.info login[279]: root login on 'stderr'\nNov 30 07:14:22 openNAS daemon.info thttpd[187]: up 21605 seconds, stats for 3600 seconds:\nNov 30 07:14:22 openNAS daemon.info thttpd[187]:   thttpd - 0 connections (0\/sec), 0 max simultaneous, 0 bytes (0\/sec), 2 httpd_conns allocated\nNov 30 07:14:22 openNAS daemon.info thttpd[187]:   libhttpd - 30 strings allocated, 8400 bytes (280 bytes\/str)\nNov 30 07:14:22 openNAS daemon.info thttpd[187]:   map cache - 0 allocated, 0 active (0 bytes), 0 free; hash size: 0; expire age: 1800\nNov 30 07:14:22 openNAS daemon.info thttpd[187]:   fdwatch - 730 polls (0.202778\/sec)\nNov 30 07:14:22 openNAS daemon.info thttpd[187]:   timers - 3 allocated, 3 active, 0 free\nNov 30 06:20:13 openNAS syslog.info -- MARK --\nNov 30 06:28:37 openNAS auth.info login[287]: root login on 'stderr'\nNov 30 06:40:13 openNAS syslog.info -- MARK --\nNov 30 07:00:13 openNAS syslog.info -- MARK --<\/pre>\n<p>The first thing I noticed is that openNAS is not as easy to use as the original ADS firmware and that it requires more setup.\u00a0<br \/>\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Because of some storm damage,\u00a0I had to replace some items in my home network. I decided to rethink the entire setup. For years I have run my cable connection though an old AMD K6 system acting as a gateway system. This system ran OS\/2, had 2 network cards, used Injoy FW for NAT, Apache (with&hellip;<\/p>\n<p><a class=\"more-link\" href=\"https:\/\/www.ecsdump.net\/?page_id=204\" title=\"Continue reading &lsquo;PART I: How Can I Break This?&rsquo;\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":202,"menu_order":0,"comment_status":"open","ping_status":"open","template":"page-templates\/info_static.php","meta":{"footnotes":""},"categories":[2,9],"tags":[27],"wf_page_folders":[105],"class_list":["post-204","page","type-page","status-publish","hentry","category-archived","category-obsolete","tag-nas-806-ef"],"jetpack_sharing_enabled":true,"jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/pages\/204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=204"}],"version-history":[{"count":0,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/pages\/204\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=\/wp\/v2\/pages\/202"}],"wp:attachment":[{"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=204"},{"taxonomy":"wf_page_folders","embeddable":true,"href":"https:\/\/www.ecsdump.net\/index.php?rest_route=%2Fwp%2Fv2%2Fwf_page_folders&post=204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}