First steps into Yoggie Pico firewall

Installed the default Yoggie software and plugged in he Pico stick. It took it about a minute to boot before Windows detected a new device. The driver installation went quite smoothly.

After that, the Yoggie tray icon was failing on my Vista. Also the network usage was blocked when I unplugged the Yoggie stick. I uninstalled the Yoggie software, but the network interface drivers remained on the system, so SSH connection into the Yoggie box continued to work.

The Yoggie software has created a new interface on my PC with the address 172.16.0.200/16. Guys, you took the whole RFC1918 172.16.* range just for a single point to point link – what a shame. Now I can’t use it inside any corporate LAN which uses these addresses.

OK, now to the interesting part. The device accepts SSH connections on root@172.16.0.1, password is “yoggie”. Inside you see a typical Busybox environment.

Here is the guide for the USB Gadget driver that is obviously used insde the Yoggie. It emulates an RNDIS Ethernet NIC. Some info for Linux and Mac users s available at the Gumstix Wiki.

dmesg follows:

# dmesg
Linux version 2.6.16.16 (root@ubuntu) (gcc version 3.4.4) #426 PREEMPT Sun May 13 13:00:40 UTC 2007
CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE)
Machine: Yoggie Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 32768
  DMA zone: 32768 pages, LIFO batch:7
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 0 pages, LIFO batch:0
  HighMem zone: 0 pages, LIFO batch:0
Run Mode clock: 208.00MHz (*16)
Turbo Mode clock: 520.00MHz (*2.5, active)
Memory clock: 208.00MHz (/2)
System bus clock: 208.00MHz
CPU0: D VIVT undefined 5 cache
CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
Built 1 zonelists
Kernel command line: console=ttyS1,115200 rw root=31:4 rootfstype=jffs2 ramdisk_size=40960 quiet yserial=PIF0-4107-0001-4235
IRQ84 (GPIO52): PID hash table entries: 1024 (order: 10, 16384 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 0MB 0MB 0MB = 128MB total
Memory: 127360KB available (1892K code, 342K data, 84K init)
Calibrating delay loop... 519.37 BogoMIPS (lpj=2596864)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Yoggie GPIO Leds driver v1.0, (c) 2006 Yoggie Security Systems.
NET: Registered protocol family 16
pxa27x: CPU frequency change support initialized
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered (default)
pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
RAMDISK driver initialized: 16 RAM disks of 40960K size 1024 blocksize
loop: loaded (max 8 devices)
Probing Nor flash at physical address 0x00000000 (16-bit bankwidth)
Nor flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x20000,blocks=64
RedBoot partition parsing not available
cmdlinepart partition parsing not available
Using static partitions on Nor flash
Creating 4 MTD partitions on "Nor flash":
0x00000000-0x00040000 : "BootLoader"
0x00040000-0x00060000 : "BootLoaderParams"
0x00060000-0x003e0000 : "Kernel"
0x003e0000-0x00800000 : "Empty"
Yoggie nand init
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
cmdlinepart partition parsing not available
Creating 2 MTD partitions on "yoggie-nand":
0x00000000-0x03c00000 : "System Area"
0x03c00000-0x08000000 : "Main"
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
TCP bic registered
NET: Registered protocol family 17
jffs2_scan_dirent_node(): Node CRC failed on node at 0x014527e0: Read 0xffffffff, calculated 0xc86797ae
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 84K
NET: Registered protocol family 1
JFFS2 notice: (170) check_node_data: wrong data CRC in data node at 0x01458800: read 0x33667c58, calculated 0xc70242d4.
I2C: i2c-0: PXA I2C adapter
EXT3 FS on ram0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
net2272: PLX NET2272 USB Peripheral Controller
net2272: irq 84, mapped mem c88ce000, chip rev 0011
net2272: running in 16-bit, no byte swap local bus mode
net2272: buffer configuration 80
net2272: version: 2006 October 17
ether gadget: using random self ethernet address
Yoggie Negotiator registered - /dev/negotiator
Allocated 256 bytes on XSCALE SRAM
Allocated 16 bytes on XSCALE SRAM
usb0: Ethernet Gadget, version: May Day 2005
usb0: using net2272, OUT ep-b IN ep-a STATUS ep-c
usb0: MAC be:3a:f4:6d:a4:ca
usb0: HOST MAC ea:d2:51:3b:7e:9f
usb0: RNDIS ready
ip_tables: (C) 2000-2006 Netfilter Core Team
ip_conntrack version 2.4 (1024 buckets, 8192 max) - 240 bytes per conntrack
usb0: high speed config #2: 100 mA, Ethernet Gadget, using RNDIS
#
Advertisements

,

  1. #1 by Marc on August 15, 2011 - 2:37 pm

    I have recently got my Yoggie open pico out of a dusty draw only to find the company have gone bust.
    do you have any of the sdk, docs and drivers archived anywhere as the yoggie site is dead now?
    Regards
    Marc

  2. #2 by txlab on August 15, 2011 - 2:48 pm

    I’ve sold everything to another enthusiast.

  3. #3 by Marc on August 15, 2011 - 2:50 pm

    Bother, Thanks anyway. I am having a hard time tracking down the old files. Back to google I guess 🙂

  4. #4 by txlab on August 15, 2011 - 2:58 pm

    or just trash it and buy a real embedded board suitable for development. There are dozens of them.

  5. #5 by Marc on August 15, 2011 - 2:59 pm

    I have a beagleboard which is much better I just dug this back out on a whim.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: