dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
135861
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

4 edits

mazilo

Premium Member

[Other] Own a FreeSwitch on a Seagate DockStar for $24.99

I will quickly summarize in this post on how to hack an inexpensive Seagate DockStar device ($24.99 from Buy + Free S/H) to run a plain-vanilla FreeSwitch v1.0.6.

WARNING: WHEN YOU RECEIVE YOUR SEAGATE DOCKSTAR DEVICE, PLEASE DON'T CONNECT IT TO A LIVE INTERNET UNLESS YOU HAVE DISABLE THE hbmgr.sh BY EDITING /etc/init.d/rcS FILE AS SHOWN IN BLOG. DOING SO WILL LET IT TO PHONE HOME TO PERFORM AN UPGRADE WITH A NEW FIRMWARE THAT HAS TELNET/SSH DISABLED AND AN UNKNOWN root PASSWORD. The only two ways to regain access the root account is either through a serial-console or activate your Seagate DockStar device to subscribe to a 1-year free subscription service to PogoPLUG firm to enable the SSH.

If you don't already know, a Seagate DockStar device is a Sheeva Plug computer runs on an ARM CPU clocked @1.2GHz with 128/256MB RAM/Flash, 4 USB2 ports (3 standard and 1 mini for a Seagate FreeAgent USB hard drive), and an RJ45 port (10/100/1000Mbps). The 256MB NAND/Flash drive is divided into two partitions, i.e. 32MB and 224MB. See the output of dmesg below. The original Seagate DockStar firmware is located on the 32MB partition. This leaves the 224MB partition un-used.

Since this device comes with a built-in of 4 USB2 ports, the easier way to hack this device to run an open-source firmware, i.e. OpenWRT, etc., is to let it boot off of an external USB partition. Unfortunately, the original u-boot manager doesn't have a capability to access any of the USB2 ports; however, it can be configured to boot off of the 224MB un-used partition. If we can sacrifice the emptied 224MB partition to hold a new u-boot manager that has a capability to access/detect any of the USB2 ports, then we can make a Seagate DockStar device to boot off of an external USB partition that contains other OS. To do this, I followed the step-by-step Pogoplug Setboot instructions. This will make a Seagate DockStar device to toggle boot between its original firmware on the internal NAND/Flash drive and a new firmware on an external USB partition. Once the original u-boot manager on a Seagate DockStar device has been reconfigured to boot off of its 224MB partition that contains a new u-boot manager, the rest is to prepare an external USB device with the choice of OS and application. For my needs, I go with an OpenWRT as the OS platform and FreeSwitch as one of the applications.

Here is the screen dumps from my Seagate DockStar device running an OpenWRT OS with FreeSwitch:
Connected to 192.168.1.123.
Escape character is '^]'.
 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------
 
BusyBox v1.16.2 (2010-07-04 06:54:02 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.
 
  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r22055) ------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@DockStar:/# uname -a
Linux DockStar 2.6.30.10 #1 Sun Jul 4 09:29:53 EDT 2010 armv5tel GNU/Linux
root@DockStar:/# free
              total         used         free       shared      buffers
  Mem:       127260        20660       106600            0           96
 Swap:       250104            0       250104
Total:       377364        20660       356704
root@DockStar:/# fs_cli
            _____ ____     ____ _     ___            
           |  ___/ ___|   / ___| |   |_ _|           
           | |_  \___ \  | |   | |    | |            
           |  _|  ___) | | |___| |___ | |            
           |_|   |____/   \____|_____|___|           
 
*******************************************************
* Anthony Minessale II, Ken Rice, Michael Jerris      *
* FreeSWITCH (http://www.freeswitch.org)              *
* Paypal Donations Appreciated: paypal@freeswitch.org *
* Brought to you by ClueCon http://www.cluecon.com/   *
*******************************************************
 
Type /help <enter> to see a list of commands
 
+OK log level  [7]
freeswitch@internal> sofia status
                     Name          Type                                       Data      State
================================================================================== ===============
                 internal       profile           sip:mod_sofia@192.168.1.123:5060      RUNNING (0)
            192.168.1.123         alias                                   internal      ALIASED
                 external       profile           sip:mod_sofia@192.168.1.123:5080      RUNNING (0)
    external::17471234567       gateway       sip:17471234567@proxy01.sipphone.com      REGED
================================================================================== ===============
2 profiles 1 alias
 
freeswitch@internal> 
 

Here is the output of a dmesg dump from an original Seagate DockStar firmware:
[    0.000000] Linux version 2.6.22.18 (bdietrich@brad-ux) (gcc version 4.2.1) #57 Mon Aug 31 16:31:01 PDT 2009
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000]   DMA zone: 256 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 32512 pages, LIFO batch:7
[    0.000000]   Normal zone: 0 pages used for memmap
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB 0MB 0MB 0MB = 128MB total
[    0.000000] Memory: 125824KB available (3588K code, 252K data, 120K init)
[    0.000000] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[    0.240000] Mount-cache hash table entries: 512
[    0.240000] CPU: Testing write buffer coherency: ok
[    0.240000] NET: Registered protocol family 16
[    0.240000] 
[    0.240000] CPU Interface
[    0.240000] -------------
[    0.240000] SDRAM_CS0 ....base 00000000, size 128MB 
[    0.240000] SDRAM_CS1 ....disable
[    0.240000] SDRAM_CS2 ....disable
[    0.240000] SDRAM_CS3 ....disable
[    0.240000] PEX0_MEM ....base e8000000, size 128MB 
[    0.240000] PEX0_IO ....base f2000000, size   1MB 
[    0.240000] INTER_REGS ....base f1000000, size   1MB 
[    0.240000] NFLASH_CS ....base fa000000, size   2MB 
[    0.240000] SPI_CS ....base f4000000, size  16MB 
[    0.240000] BOOT_ROM_CS ....no such
[    0.240000] DEV_BOOTCS ....no such
[    0.240000] CRYPT_ENG ....base f0000000, size   2MB 
[    0.240000] 
[    0.240000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.240000] 
[    0.240000]  Detected Tclk 200000000 and SysClk 400000000 
[    0.240000] MV Buttons Device Load
[    0.240000] Marvell USB EHCI Host controller #0: c0537600
[    0.740000] PEX0 interface detected no Link.
[    0.740000] PCI: bus0: Fast back to back transfers enabled
[    0.740000] SCSI subsystem initialized
[    0.740000] usbcore: registered new interface driver usbfs
[    0.740000] usbcore: registered new interface driver hub
[    0.740000] usbcore: registered new device driver usb
[    0.740000] NET: Registered protocol family 2
[    0.750000] Time: kw_clocksource clocksource has been installed.
[    0.840000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.840000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.840000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.840000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.840000] TCP reno registered
[    0.870000] RTC has been updated!!!
[    0.870000] RTC registered
[    0.870000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.870000]   o RAID 5 Xor calculation
[    0.870000]   o kernel memcpy
[    0.870000]   o kenrel memzero
[    0.870000] Number of XOR engines to use: 4
[    0.870000] cesadev_init(c00116b4)
[    0.870000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.870000] MV Buttons Driver Load
[    0.870000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.870000] squashfs: LZMA suppport for slax.org by jro
[    0.870000] JFFS2 version 2.2. (NAND) &Acirc;&copy; 2001-2006 Red Hat, Inc.
[    0.870000] io scheduler noop registered
[    0.870000] io scheduler anticipatory registered (default)
[    0.890000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.890000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.900000] serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[    0.900000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.910000] Loading Marvell Ethernet Driver:
[    0.920000]   o Cached descriptors in DRAM
[    0.920000]   o DRAM SW cache-coherency
[    0.920000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.930000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.940000]   o TCP segmentation offload enabled
[    0.940000]   o Receive checksum offload enabled
[    0.940000]   o Transmit checksum offload enabled
[    0.950000]   o Network Fast Processing (Routing) supported
[    0.960000]   o Driver ERROR statistics enabled
[    0.960000]   o Driver INFO statistics enabled
[    0.960000]   o Proc tool API enabled
[    0.970000]   o Rx descripors: q0=128
[    0.970000]   o Tx descripors: q0=532
[    0.980000]   o Loading network interface(s):
[    0.980000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000]     o eth1, ifindex = 2, GbE port = 1
[    0.990000] 
[    1.000000] mvFpRuleDb (c7ed5000): 1024 entries, 4096 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.010000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.020000] 
[    1.020000] Warning Sata is Powered Off
[    1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.040000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    1.050000] Scanning device for bad blocks
[    1.150000] Using static partition definition
[    1.150000] Creating 4 MTD partitions on "nand_mtd":
[    1.160000] 0x00000000-0x00100000 : "u-boot"
[    1.160000] 0x00100000-0x00500000 : "uImage"
[    1.170000] 0x00500000-0x02500000 : "root"
[    1.170000] 0x02500000-0x10000000 : "data"
[    1.180000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.180000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.220000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.240000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.240000] usb usb1: configuration #1 chosen from 1 choice
[    1.250000] hub 1-0:1.0: USB hub found
[    1.250000] hub 1-0:1.0: 1 port detected
[    1.370000] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.370000] USB Universal Host Controller Interface driver v3.0
[    1.650000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.800000] usb 1-1: configuration #1 chosen from 1 choice
[    1.800000] hub 1-1:1.0: USB hub found
[    1.810000] hub 1-1:1.0: 4 ports detected
[    2.160000] usb 1-1.2: new high speed USB device using ehci_marvell and address 3
[    2.260000] usb 1-1.2: configuration #1 chosen from 1 choice
[    2.270000] usbcore: registered new interface driver usblp
[    2.270000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    2.280000] Initializing USB Mass Storage driver...
[    2.280000] scsi0 : SCSI emulation for USB Mass Storage devices
[    2.290000] usbcore: registered new interface driver usb-storage
[    2.300000] USB Mass Storage support registered.
[    2.300000] usb-storage: device found at 3
[    2.300000] usb-storage: waiting for device to settle before scanning
[    2.300000] mice: PS/2 mouse device common for all mice
[    2.310000] i2c /dev entries driver
[    2.310000] Linux telephony interface: v1.00
[    2.310000] md: linear personality registered for level -1
[    2.320000] md: raid0 personality registered for level 0
[    2.330000] md: raid1 personality registered for level 1
[    2.500000] raid6: int32x1     97 MB/s
[    2.670000] raid6: int32x2    114 MB/s
[    2.840000] raid6: int32x4    122 MB/s
[    3.010000] raid6: int32x8    110 MB/s
[    3.010000] raid6: using algorithm int32x4 (122 MB/s)
[    3.010000] md: raid6 personality registered for level 6
[    3.020000] md: raid5 personality registered for level 5
[    3.020000] md: raid4 personality registered for level 4
[    3.030000] raid5: measuring checksumming speed
[    3.080000]    arm4regs  :  1071.200 MB/sec
[    3.130000]    8regs     :   754.800 MB/sec
[    3.180000]    32regs    :   899.600 MB/sec
[    3.180000] raid5: using function: arm4regs (1071.200 MB/sec)
[    3.190000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    3.190000] dm_crypt using the OCF package.
[    3.200000] sdhci: Secure Digital Host Controller Interface driver
[    3.200000] sdhci: Copyright(c) Pierre Ossman
[    3.210000] usbcore: registered new interface driver usbhid
[    3.210000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    3.220000] TCP cubic registered
[    3.220000] NET: Registered protocol family 1
[    3.230000] NET: Registered protocol family 17
[    3.230000] md: Autodetecting RAID arrays.
[    3.240000] md: autorun ...
[    3.240000] md: ... autorun DONE.
[    5.110000] Empty flash at 0x00de8e44 ends at 0x00de9000
[    8.800000] VFS: Mounted root (jffs2 filesystem) readonly.
[    8.800000] Freeing init memory: 120K
 
I hope this has inspired you to invest your $24.99 for your own Seagate DockStar device to host your own PBX system. I may not be able to get an asterisk-1.6.x properly hosted on a Seagate DockStar device running an OpenWRT OS, but that doesn't mean it is not possible. After all, this has been a very inexpensive way to own a PBX system.

[EDIT]: By now, I believe some of you have already received your Seagate DockStar device from Buy. So, I have attached the OpenWRT SVN firmware (contains the uImage Linux kernel, OpenWRT firmware, FreeSwitch v1.0.6, and other utilities) in a tarball file for you to use on your Seagate DockStar device (only if you wish).

In order to use the above firmware, you MUST mod your Seagate DockStar device so that it will load a firmware from an external USB storage. This can be done in two ways, i.e. using a PogoPlug Setboot as shown here or installing a new OpenWRT firmware on its internal NAND/Flash partition as shown here. My preference is to use a PogoPlug SetBoot, YMMV. If you use a PogoPlug SetBoot option, then follow the following steps to complete the installation:
    1. Follow the PogoPlug SetBoot step-by-step instructions all the way to step #2c. This will enable your device to boot a firmware on an external USB partition.
    2. Get a USB storage device (at least 100MB+, preferrably 256MB+) and format it with an EXT3 filesystem (similar to step #3 shown in PogoPlug SetBoot step-by-step instructions). I use Linux tar utility to untar the tarball file into my USB storage device mounted on /mnt (tar -jxf openwrt-kirkwood-rootfs.tar.bz2 -C /mnt).
    3. Plug the USB storage to your Seagate Dockstar device and power it up.
    4. Login into your Seagate DockStar device (you will need to find its IP Address from your router). Once logged into your device, type reboot to perform a reboot. The PogoPlug SetBoot approach will make a Seagate DockStar device to toggle booting between the original firmware and a new firmware found on an external USB storage.
    5. You can use a telnet utiility (no SSH yet as of this moment) to log into your Seagate DockStar device once it has finished booting. At this stage, no need for a username/password. Once you have logged into your Seagate DockStar device running a new OpenWRT SVN firmware, you can change its root password by using the 'passwd' utility. Just type passwd and hit return. Then, you will be prompted to enter for a new password as well as its confirmation. Once you have secured your device with a new root password, the next login MUST be done using a secured shell login, i.e. ssh (on Linux) or putty (on windows).
    6. By now, you can use a ps utility to see a lot of freeswitch processes are running. Execute fs_cli to get into freeswitch console. Once in the Freeswitch console, you can type /bye to exit to the shell.
    7. For further information on how to configure, operate, and maintain a FreeSwitch PBX system, please read the FreeSwitch Doc. Have fun and enjoy with your new FreeSwitch PBX system.

The following is a list of files I have attached here: OpenWRT SVN tarball firmware file, .config file to configure OpenWRT SVN source, and config-default file to configure Linux kernel for OpenWRT SVN, respectively. Please rename the config file to .config (the system didn't let me upload a .config file name).
config
18567 bytes
(config.zip).config file for menuconfig

config-default
1653 bytes
(config-default.zip)config-default file for Linux kernel

[attachment=3]


usa2k
Blessed
MVM
join:2003-01-26
Westland, MI

2 edits

usa2k

MVM

Re: [Other] Get your own FreeSwitch on a Seagate DockStar for $2

For $24.99/free shipping, I figure I'll play with one



Site-marked this thread.

(Compare price to Newegg!)

mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

said by usa2k:

For $24.99/free shipping, I figure I'll play with one
Honestly, for those who have been dreaming to run/own a PBX system, this offer is not a bad idea. Ironically, I only see less than a handful readers here have shown interests and committed to invest their $$$ on this device since my fisrt post here (which confirms a Seagate DockStar device running on an OpenWRT OS to host a FreeSwitch v.1.0.6). Please don't let this bad news deter you. If I can find my 4GB SD card, I sure will try to see if my Seagate DocKStar device can run a PlugPBX distro to assure you all. I just hope the offer from Buy is still going strong and for those who have missed the opportunity, perhaps it is time to act now.

One thing I forgot to mention in my previous post is so far my FreeSwitch runs very fast/smooth. It took less than 1 minute to get ready from boot on my Seagate DockStar device. On my Netgear WGT634U device, this would have taken at least 3 minutes from boot.
gbh2o
join:2000-12-18
Longs, SC

2 edits

gbh2o

Member

Have faith, your cheapness. Perhaps some of us are just waiting the sloooowwwww Fedex/SnailMail delivery (cheap, cheap)?!?! And, since I know that I have zero experience with OpenWRT, I'm just watching, waiting and learning. Personally, I would be happy to use your build efforts as a starting point for my own destructive coding tendencies. Keep charging ahead... it'll probably save me a lot of work! (Bashfully admits to having two Dockstars on order)

TheMole
join:2001-12-06
USA

1 edit

TheMole to mazilo

Member

to mazilo
I just picked up two -- one to break and the other to use

Thanks for the post.

{edit - removed duplicate link - sorry!}
MartyT
join:2004-09-03
Georgetown, SC

MartyT

Member

Ok, I took the hook. After telling Mazi it looked cheap and powerful but halfbaked, I relented and figured I'm simply a sucker for small powerful devices that can be hacked. Count me in!

mgraves1
Premium Member
join:2004-04-05
Houston, TX

mgraves1 to mazilo

Premium Member

to mazilo
I'm not entirely sure what I'll do with this...but I think that I will definitely try it out!
MartyT
join:2004-09-03
Georgetown, SC

MartyT

Member

I don't think you will want to use it for its intended purpose, based on my understanding of the software that comes with it. Looks like they want money later for the "cool software" that is included for one year.

It's a hack platform, pure and simple, IMO.

I'll admit, my favorite hacking platform is the Asus WL-520gu, which includes a wireless radio, but this is cheap enough to simply say, OK.

By the way, if you want to build a cheap Internet Radio using the 520gu, check this out.

»mightyohm.com/blog/2008/ ··· duction/

No need to install the serial port or the display, or to flash it using the serial port. I've got one running using the firmware posted by ilinux and a cheap HK 7.1 USB sound card.

brg
Premium Member
join:2001-01-03
Chicago, IL

brg to mazilo

Premium Member

to mazilo
What the heck, in for 1 with the caveat that I'm really hoping His Cheapness figures out how to get get Asterisk-1.6.x up-and-running.
MartyT
join:2004-09-03
Georgetown, SC

MartyT

Member

I know Mazi sincerely appreciates being given that title. I agree that he truly deserves it, along with our thanks for sharing his extensive knowledge of "hacking little things".

Thanks Mazi!
TBaritone
Premium Member
join:2010-01-19
Redmond, WA

TBaritone to mazilo

Premium Member

to mazilo
After installing OpenWRT, are the remaining USB ports still usable for network storage? Or printer/device sharing?
zamarac
join:2008-11-29
Canada

1 edit

zamarac to mazilo

Member

to mazilo
Amazon has now similar offer, I guess its Seagate's discount, they are shifting to a newer unit production probably. Latest OpenWRT Backfire release you mentioned in another thread also has Asterisk included. Any reason not to try that instead of your own Asterisk port?
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo to MartyT

Premium Member

to MartyT
said by MartyT:

I'll admit, my favorite hacking platform is the Asus WL-520gu, which includes a wireless radio, but this is cheap enough to simply say, OK.
Marty, I have never done this before; however, I believe one can probably make a DockStar device to support a wireless radio by adding a Linux supported USB WiFi dongle to one of its USB ports.
mazilo

mazilo to TBaritone

Premium Member

to TBaritone
said by TBaritone:

After installing OpenWRT, are the remaining USB ports still usable for network storage?
The rest of USB ports are still active and can be used.
Or printer/device sharing?
AFAIC, this has something to do with the additional Linux drivers + applications/software/utilities, i.e. samba, p910nd daemon/utility, etc. I haven't really looked into these capabilities, yet. My main goal is to turn my DockStar device into a PBX system. Sorry to disappoint you. Perhaps, others may want to help on this.
voip_wire
join:2010-07-02

1 edit

voip_wire to zamarac

Member

to zamarac
said by zamarac:

Amazon has now similar offer, I guess its Seagate's discount, they are shifting to a newer unit production probably. Latest OpenWRT Backfire release you mentioned in another thread also has Asterisk included. Any reason not to try that instead of your own Asterisk port?
It is buy.com selling through amazon. It is amazing how much the prices fluctuate for this. Amazon was selling it for $46 and is now up at $76. Newegg was selling it for $20+Shipping (total was essentially $25). It is up at $79. Interestingly, the open box version back then, as now was at $60 (or so)!
I ordered mine from buy.com through amazon (had a gift card), so I am patiently waiting for it to get shipped. Of course, given that mazilo is on a one-man crusade to popularize this unit, I may never receive it
-m

Edit - misc typos
crunchy
join:2009-04-21
Harrisburg, PA

crunchy to mazilo

Member

to mazilo
Thanks...bought mine yesterday. It will be a week or two before it gets here, though. I enjoy hacking devices, especially cheap ones!

usa2k
Blessed
MVM
join:2003-01-26
Westland, MI

1 edit

usa2k

MVM

FWIW: Mine has a FEDEX tracking number now with a 1 week arrival date.

EDIT: btw, its coming from Dallas, TX.

TheMole
join:2001-12-06
USA

1 edit

TheMole to mazilo

Member

to mazilo
Mazilo,

Which version of openwrt did you use? I can't seem to track it down.

Thanks.
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

said by TheMole:

Which version of openwrt did you use? I can't seem to track it down.
I compiled my own firmware from the OpenWRT SVN trunk.
larrycl
join:2009-04-07

larrycl

Member

Mazilo, this looks really cool.
I'm excited to try it out, but I'm pretty much a novice at hacking embedded linux systems. Would you be able to share the OpenWRT firmware you compiled? Or even share a disk image that I could dd to a flash drive?
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

said by larrycl:

Would you be able to share the OpenWRT firmware you compiled?
I reckon it is not a bad idea. I can always upload the firmware tarball or an external USB partition image to an open file sharing site. The only problem is you have no choice to choose what application/software/utility to put into your DockStar. For instance, I have included Asterisk v1.6.2 (even though it is not working), FreeSwitch v1.0.6, and some utilities (ettercap, strace, minicom, etc.) to the OpenWRT firmware. The size of this firmware can easily reach 100MB (uncompressed).

I strongly recommend everyone who wants to hack this device with an OpenWRT get his/her dirty to compile own firmware from the OpenWRT SVN trunk. The (not so complete) instructions can be found here. Or, if you prefer to let your DockStar run on other Linux distro, i.e. Ubuntu, the instructions can be found here. This approach will turn a DockStar device into a Linux Console/Desktop computer with development tools (compilers + libraries). This way, you can compile your own Asterisk/FreeSwitch and/or any open-source applications. Remember, after all a Seagate DockStar is based on an ARM CPU clocked @1.2GHz with 128MB RAM. So, it is a pretty small and powerful computer, especially if it is configured as a console and not a Desktop computer with GUI.

DracoFelis
Premium Member
join:2003-06-15

DracoFelis to mazilo

Premium Member

to mazilo
OK, you convinced me. I just ordered 2 of the things from Amazon (although they will likely take a week or two to arrive). While I don't know exactly if/when I'll have time to do extensive "hacking" of the things, at around I $25/each I figured I couldn't go too wrong. This thing just has the potential to make a really nice (presumably fairly low power) home Linux "application server" for the LAN.

And since these look like essentially rebranded (older model?) PogoPlugs, it was even more of a no-brainer for me. Because I had already just about decided to grab a real PogoPlug (at $99) to serve initially as a home file sharing device, and possibly later as a Linux hacking device. However, with the info you gave, I ended up spending 1/2 that much money, and I'm getting two devices instead of one. Granted they are rebranded devices, and they may even be older model hardware, but for the cost difference I figured it was worth the gamble.

NOTE: I did notice in one of the Amazon reviews for the thing, that the built-in firmware does have Windows network sharing (most likely SAMBA), you just have to do a couple of cute steps to enable it. So I figure I might end up using one of the devices to act as a very cheap NAS on my home LAN (possibly even with the default firmware built into the device).

However, back to VoIP uses. I would love to have a fully functional IP-PBX (Asterisk?) on the LAN, to give me some features that I just can't get with just my ATAs (I've pretty much pushed both my SPA-3000 and SPA-3102 to the limits of what they can do by themselves). And if that IP-PBX is both cheap and low power (which is looks like this device is), so much the better!

Let me know if/when you get things going. And if you can give us a disk image (ISO?) as a starting point, so much the better. I have done a fair amount of VoIP, but its been mostly with my SIP adapters. As such, I don't have much experience installing Asterisk (or any other IP-PBX) software, much less on some "embedded device" such as this. So anything that other "hackers" can figure out (to make the task easier), I'm all for.

BTW: Does anyone know if Asterisk has the ability to customize the CallerID name (as sent to the SIP phone) depending upon what caller ID number (and possibly which Asterisk SIP trunk) the call came in on? One feature I would really like in an IP-PBX (which I currently only get on calls coming in via my ViaTalk account), is what the provider "ViaTalk" refers to as "custom caller ID". The idea is that I would like the option to override the "name" field that shows on the ringing phones, based upon a lookup in the IP-PBX. This would allow me to do things like customize the callerID of friends/family, so that their name always shows up when their number is sent via CallerID (vs whatever their phone company chose to send as the "name" in CallerID). And it would also be nice to customize the "name" based upon which VoIP provider received the call (i.e. For example, so I can always know, simply by looking at the name portion of the phone, if/when the incoming call is from the provider servicing my toll free phone number). Anyone know if this (caller ID "name" override) feature is likely to be possible on a IP-PBX built on this (very cheap) hardware?
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

said by DracoFelis:

NOTE: I did notice in one of the Amazon reviews for the thing, that the built-in firmware does have Windows network sharing (most likely SAMBA), you just have to do a couple of cute steps to enable it. So I figure I might end up using one of the devices to act as a very cheap NAS on my home LAN (possibly even with the default firmware built into the device).
OpenWRT has a support for SAMBA3 as well as a small printer daemon (P910ND), too. If you really wanna hack a Seagate DockStar device to run an OpenWRT firmware, I strong encourage you to spend sometimes to play with building/compiling an OpenWRT from its SVN trunk. You will be able to customize the firmware to your own needs. If that isn't enough to convince you, perhaps this newly written HOWTO install an OpenWRT firmware to a Seagate DockStar NAND drive will. It will completely replace the original firmware with an OpenWRT firmware. And with a pivoroot scripts, the device will be able to detect an OpenWRT partition on an external USB storage. This means, one can put a lot of applications to run on a Seagate DockStar device. Currently, I have a 1GB USB memory stick used as the boot device for my Seagate DockStar device. I put OpenWRT + asterisk-1.6.2 (defunct) + freeswitch-1.0.6 + some utilities (i.e. ettercap, minicom, strace, etc.) on to this USB memory stick and the whole thing takes about 100MB of space.
However, back to VoIP uses. I would love to have a fully functional IP-PBX (Asterisk?) on the LAN, to give me some features that I just can't get with just my ATAs (I've pretty much pushed both my SPA-3000 and SPA-3102 to the limits of what they can do by themselves). And if that IP-PBX is both cheap and low power (which is looks like this device is), so much the better!
There is a chance you can make your Seagate DockStar device to run a PlugPBX distro which contains a FreePBX system with GUI (if that's what you like).
Let me know if/when you get things going. And if you can give us a disk image (ISO?) as a starting point, so much the better.
I sure don't mind. If you need further help on how to get you going with OpenWRT firmware compilation, I will be more than happy to help. Just PM me and we will take it from there with e-mails.
I have done a fair amount of VoIP, but its been mostly with my SIP adapters.
For those readers who don't know much about you, you certainly have contributed a lot on this as well as other VoIP forums I also frequented and I personally thank and salute you for that. Cheers.
isaacl
join:2009-07-26

isaacl

Member

Looks cool...
Deciding if I should go for one, but since I'm currently running PBX in a Flash on my PBX, and I don't know vanilla Asterisk, I'm not sure it's worth it...
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

said by isaacl:

..., but since I'm currently running PBX in a Flash on my PBX, and I don't know vanilla Asterisk, I'm not sure it's worth it.
If you read my post above, I did mention there is a possibility to let a Seagate DockStar device run a PlugPBX distro which contains a FreePBX system with GUI. I haven't done this and don't have any future plan (in my schedule) to do this, yet; however, someone here in the forum or even you may want to give it a try.

For $24.99 + free S/H (to US), this is a steal to have your own PBX system hosted on a Linux embedded system that draws no more than 10Watts of electricity, let alone noiseless (no mechanical moving parts)!

TheMole
join:2001-12-06
USA

TheMole

Member

Mazilo, et al.

As i mentioned above, I've picked up two of the Seagate DockStar's that we've all been discussing.

I'm interested in getting these going as dedicated VPN clients (for among other things, VoIP traffic between remote locations).

I have been using flashed WRT54GLs in the past, and this is half the price w/ more processing power and I happen to have two more clients I need to build out.

I've read up on all the links here. I think I'll go with openwrt firmware.

HOWEVER, I've never compiled anything from SVN before.. so i have a few (dump) questions:

(1) can i build the software on an x86 linux box then move it to the USB attached drive? Once I move it over will it boot w/o issue, or do i need to then reconfigure on the device itself?

(2) is there a SVN branch that i need to use to support the Seagate DockStar hardware? or will I choose my hardware when I build the firmware?

Thanks all. This is a great project which I'm looking forward to getting going.
voip_wire
join:2010-07-02

1 edit

voip_wire

Member

said by TheMole:

Mazilo, et al.

(1) can i build the software on an x86 linux box then move it to the USB attached drive? Once I move it over will it boot w/o issue, or do i need to then reconfigure on the device itself?
OpenWRT is really a build system. It provides Makefiles/Scripts based recipes to build an image that you flash/burn/copy to your target device.

1. Yes, you can compile on x86 for dockstar. The build system builds the necessary cross-compilers when you build the first time. Hence the first build takes a bit longer than a rebuild.

2. The target (dockstar, in our case) should boot fine. You will have to configure the system on the dockstar after the initial boot. You can SSH into it for text based configuration. There is web based GUI (LUCI) that is probably more user friendly. I don't know, cause I have never used it.

3. The SVN trunk should be fine. You select the target as well as the packages you want to install by running
make menuconfig
 
If you have ever compiled the linux kernel, this interface should be very familiar.

Having said all this, I am still waiting for my dockstar. So all this is from memory, past experience with ASUS and Buffalo routers. There is some general build information on »nuwiki.openwrt.org/doc/h ··· uildroot

I would be happy to share my experiences, once I have the dockstar in hand.

Cheers,
-m
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo to TheMole

Premium Member

to TheMole
said by TheMole:

(1) can i build the software on an x86 linux box then move it to the USB attached drive? Once I move it over will it boot w/o issue, or do i need to then reconfigure on the device itself?
I compile my OpenWRT firmware on my OpenSuSE Linux Desktop computer. The compilation will produce the binary firmwares for a Marvell Kirkwood platform which a Seagate DockStar is based on. Once the compilation produces the firmware, usually it can be uploaded to flash to the device. However, since there is no direct support for a Seagate DockStar device on OpenWRT, flashing a binary OpenWRT firmware produced by the compilation is a tricky process as seen on this new HOWTO: install OpenWrt on Seagate Dockstar. Remember, if you go this route and unless you know how to, there is no way to reflash your Seagate DockStar device with an original firmware from Seagate as of this writing. For my Seagate DockStar device, I enabled [X] tar.gz (under Target Images menu) using make menuconfig to produce an OpenWRT firmware in a tarball file. The reason is simply to extract the tarball file to an external USB partition and use it to boot my Seagate DockStar device with an OpenWRT OS. This way, the original firmware on my Seagate DockStar device will not be left intact. I recommend you go with this route first to make sure your built OpenWRT firmware will work and won't brick your Seagate DockStar device. If you happen to brick it, then you will need a serial-console cable to de-brick the device.
(2) is there a SVN branch that i need to use to support the Seagate DockStar hardware?
Actually, it is called an OpenWRT development branch as seen here. You can choose the released BackFire 10.3, Kamikazi 8.09, or development branch. For me, I chose the trunk from the development branch to use on my Seagate DockStar device. I believe the released BackFire 10.3 branch will work too.
or will I choose my hardware when I build the firmware?
Once you have downloaded a copy of OpenWRT source from one of the branches, you can execute make menuconfig to select which hardware platform to build firmware to use. For a Seagate DockStar, you will need to select [X] Marvell Kirkwood as the Target System and (X) Default as the Target Profile.

FYI, since a lot of (WiFi) NAT/Firewall routers are based on a Marvell Kirkwood, the default settings on OpenWRT build is for a router. As you know, a Seagate DockStar is a networking device and not a router, a lot of un-necessary packages will be built to include in the firmware using the default settings. AFAIK, this won't do any harm, except will degrade the performance of the device a bit. To add/remove the un-necessary packages, you can use make menuconfig to add/remove the packages. If you are a Linux hacker or at least are familiar with a Linux OS, you may also want use make kernel_menuconfig to add/remove modules in building the Linux kernel for your Seagate DockStar device. The more modules you remove, the leaner the Linux kernel will be.

TheMole
join:2001-12-06
USA

TheMole

Member

Thanks to both, voip_wire See Profile and mazilo See Profile. that's exactly what i needed.

I eagerly waiting for my two devices to arrive. i'll be sure to post my results here -- albeit, they aren't exactly going to be used to run asterisk or freeswitch, but my results might be interesting nonetheless.
mazilo
From Mazilo
Premium Member
join:2002-05-30
Lilburn, GA

mazilo

Premium Member

I had updated my original post in this thread with a very important information that I completely had forgotten about until now. For those who already read and/or passed the 1st post in this thread, you will miss the most important peace of information and I excerpt it below. I apologize for this mishap and hope no one has received his/her order and had plugged it into a live Internet feed, yet.

WARNING: WHEN YOU RECEIVE YOUR SEAGATE DOCKSTAR DEVICE, PLEASE DON'T CONNECT IT TO A LIVE INTERNET UNLESS YOU HAVE DISABLE THE hbmgr.sh BY EDITING /etc/init.d/rcS FILE AS SHOWN IN BLOG. DOING SO WILL LET IT TO PHONE HOME TO PERFORM AN UPGRADE WITH A NEW FIRMWARE THAT HAS TELNET/SSH DISABLED AND AN UNKNOWN root PASSWORD. The only two ways to regain access the root account is either through a serial-console or activate your Seagate DockStar device to subscribe to a 1-year free subscription service to PogoPLUG firm to enable the SSH.