I'm not certain it will fix the problems here, but crackly sound on my dockstar running debian was fixed by the /etc/asound.conf file in the second post in this thread: "USB sound - scratchy [ SOLVED ]" here: http://forum.doozan.com/read.php?2,2840

Thanks very much.  That worked perfectly.  I had tried it earlier, but had the wrong syntax (you might ask how I could get something so simple wrong).

ssh myname@192.168.1.1

I have a device on a remote network which I can access through ssh.  There is another device on the network which is accessible through ssh, but only locally, not remotely.  Is there a command line tool which I can use after sshing into the first device which I can use to access the second?

>What do you call "non-default" network?

All that I wished to do was set up wireless on a network which has a gateway of 192.168.10.1 and not use for the AP an ip of 192.168.1.1.  I may through ignorance gone about it in very roundabout (as well as unsuccessful) way.

I tried a number of hints from various threads, and did not save my starting point, so now I don't know what the original iptable settings were, or what changed them to the present values.

How you suggest I proceed?  (And thanks for you patience.)  I can, if need be, re-install debian on the guruplug.

Thanks.  Here are the outputs.  Unfortunately, I don't know exactly what I am looking for.

#iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE  all  --  anywhere             anywhere
MASQUERADE  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

#cat /proc/sys/net/ipv4/ip_forward
1

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:50:43:01:83:a8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.118/24 brd 192.168.10.255 scope global eth0
    inet6 fe80::250:43ff:fe01:83a8/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state UNKNOWN qlen 1000
    link/ether 00:50:43:01:83:a9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.78/32 brd 192.168.10.255 scope global eth1
4: uap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:23:1f:b4:29 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.179/24 brd 192.168.10.255 scope global uap0
    inet6 fe80::224:23ff:fe1f:b429/64 scope link
       valid_lft forever preferred_lft forever
5: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether b6:86:8d:84:38:22 brd ff:ff:ff:ff:ff:ff

What information can I provide that would be more diagnostic?

The output of "iptables -L" is as follows:
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:www

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

I'm trying to set up a guruplug as an access point on a network other than the default.  The gateway on this network is 192.168.10.1. I've been able to connect to the accesspoint, but with no connectivity to the internet.

In /etc/network/interfaces, I've set eth0 to 192.168.10.118, and uap0 to 192.168.10.179.  I changed /etc/resolv.conf to "nameserver 192.168.10.1".  I can ssh in to the eth0 ip and ping www.google.com.  So the guruplug has access to the internet on this network.

I left uap0 unsecured for testing.  I've modified /root/init_setup.sh to provide the ssid "Network101" and the ip to 192.168.10.179. 

I edited /etc/udhcpd.conf and changed all the references to the 192.168.10 subnet.  Network101 appears on my laptop, and I can connect to it.  But then I cannot connect to the internet through my browser, and
cannot successfully ping www.google.com or 192.168.10.1.

An odd thing is that iwconfig says "no wireless extensions" for uap0.  "uaputl sys_config" correctly reports the ssid and other parameters.

Any thoughts on what else I need to do to get this to work?

Congratulations on persisting until you got a working installation.

Looks like you're getting closer, but I don't know the significance of your error message.

What method did you use to get debian on the SD?  The EISA/EPIA installer allows to to install either to SD or to nand.  It does require a single USB stick formatted as a fat drive. 

You can look for u-boot commands by typing 'help'.  More specifically, you can type 'help fatload', 'help ext2load', 'help fatls', 'help ext2ls', 'help bootm'.

How is your sd partitioned--1, 2, or 3 partitions?  You may well find it easier to install fresh to nand than to copy over what you have.

I personally know of no reason to prefer the Ubuntu 9.04 distribution to Debian.  If you know Debian, I'd go for it. 

Recovering default values in u-boot won't help if what is in nand is not ok.  Since your plug's previous owner changed the boot environment, you don't know what is in nand, tho it appears to be something unbootable.

You might want to do a fresh install.  This can be done fairly easily with the ESIA/EPIA installer.  Unless you have a preference otherwise, I could recommend the Debian Squeeze nand installation, or the one for the original firmware, Ubuntu 9.04.  All you need for either can be downloaded from the Sourceforge site here:
https://sourceforge.net/projects/epia/

Download the installer and then back on the Sourceforge site click "View all files" to download the distribution files.

The installer thread, 9 pages worth, is here: http://plugcomputer.org/plugforum/index.php?topic=1400.0

bootcmd and bootargs continue to provide the information which u-boot uses to try to boot.  In your first posting, the part of bootcmd which said, "run boot_mmc" indicates that that was trying to boot from an SD card (mmc).  But the fact that you got a message about "scanning for usb devices' indicates that it was muddled, and was trying to read from usb.

But all that is history now.  What exactly did you do to get to the situation which the latest printenv shows?  This shows that u-boot is now trying to boot from nand.  You can run the separate parts of bootcmd individually to see exactly what is happening.  In particular you should run "read.e 0x800000 0x100000 0x400000" to see what the output is.  This is trying to read your uImage into memory location 0x800000 from nand location 0x100000 for 0x400000 bytes.  This is the typical nand boot process.  What is located there (i.e., what uImage did you try to load there)?

When you enter the 'boot' command in u-boot, what happens is governed by what is in the environment variables, 'bootcmd' and 'bootargs'.  What do you get when you do the following?

printenv bootcmd
printenv bootargs

Sorry not to be able to provide a detailed answer.  One method would be to install to mmc and then replicate the partitioning and data on usb.

You would then modify the u-boot commands to use the usb device.  Specifically, in u-boot look at bootcmd and boorargs and change the mmc references to suit the usb.