Unknown Squashfs compression

```
I can't unpack this router firmware - FREEPORT17.01.bin You can find it here -
https://docs.google.com/file/d/0By6Bi79J6LLVSVNGM3p2WS1kaWs/edit?usp=sharing

What steps will reproduce the problem?

1.[rzrusink@localhost FMK_060613]$ sudo ./extract-firmware.sh FREEPORT17.01.bin
FREEPORT17.01/

Firmware Mod Kit (extract) 0.88, (c)2011-2013 Craig Heffner, Jeremy Collake

Preparing tools ...
Scanning firmware...

Scan Time: 2013-06-15 22:26:23
Signatures: 193
Target File: /home/rusink/FMK_060613/FREEPORT17.01.bin
MD5 Checksum: 90ca7600b4e5462eebd244662f271769

DECIMAL HEX DESCRIPTION
--------------------------------------------------------------------------------
-----------------------
0 0x0 uImage header, header size: 64 bytes, header CRC:
0x443704BE, created: Tue Jan 17 12:07:57 2012, image size: 788187 bytes, Data
Address: 0x80000000, Entry Point: 0x80228000, data CRC: 0x4ACB9008, OS: Linux,
CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name:
"DOMOLINK CPE Series"
64 0x40 LZMA compressed data, properties: 0x5D, dictionary size:
8388608 bytes, uncompressed size: 2373284 bytes
983040 0xF0000 Squashfs filesystem, little endian, version 3.0, size:
2125487 bytes, 428 inodes, blocksize: 65536 bytes, created: Tue Jan 17
12:08:03 2012

Extracting 983040 bytes of uimage header image at offset 0
Extracting squashfs file system at offset 983040
Extracting 1104 byte footer from offset 3144684
Extracting squashfs files...

-And then program hangs. :(

What version of the product are you using? On what operating system?
Firmware Mod Kit (extract) 0.88,
OS Fedora 18

Please provide any additional information below.

I've faced to the same problem for several times with variouse firmwares like
this.

```

Original issue reported on code.google.com by `rzrusink` on 15 Jun 2013 at 6:39

Start by reproducing the reported command with extract-firmware.sh on FREEPORT17.01.bin and inspect the Squashfs extraction stage where the process hangs. Done means the firmware files are extracted successfully, but the issue does not name a test or implementation file to guide further work.

Written by the indexing model from the issue text.