GoFlex Satellite

[avman]

Same version as you apparently, geert.

http://192.168.0.1/network-list.psp

seems to work ok, listing the 2 networks active here.

www/satellite/urls.py

is useful, thank you. The "find" command on my GFS always causes a segmentation fault if I search > 1 level deep (so no use). I think it's part of "Busybox" so I'll install a later BB  version to see if that's fixed. I get segmentation faults occasionally on a small mips® based box I have, but I can generally ignore them, but seemingly under ångstrom on the GFS, they are as good as fatal Do you get that too?

I've actually now installed "midnight commander" to help with navigation before I get RSI However it looks like it uses the system find so still gives segmentation faults. 

[geert56]

@avman

I hardly ever use "find". You might want to install findutils via opkg in /opt/bin.

Don't forget to put /op/bin in your path (/etc/profile) ahead of where the busybox

find resides.

I usually use jove as editor on small systems, but it wouldn't work well on GFS.

I tried uemacs but I don't like it. So I ended up installing emacs22, a full blown emacs.

Plenty of disk space anyway and the GFS processor is powerful enough.

Dired mode has problems with the busybox "ls" though. I installed coreutils-ls and

put this in my .emacs startup file:

(setq insert-directory-program "/opt/bin/coreutils-ls")

[avman]

Interesting that we get different results from the same firmware geert?

root@dm3730-am3715-evm:/home# ./connect.sh avman 4 ********

In if (connect.sh) /tmp/device_ssid exist

Killing lighttpd... Killing python... Killing dnsmasq... Killing udhcpd...

ssid = avman Enc = 4 pass = ********

Flag set...(given ssid matched with scanresults)

In wpa2 join Connection closed by foreign host. 

log_connect just registers localhost as the IP given to the GFS, but presumably you get a bona fide IP generated from your router? 

=====

root@dm3730-am3715-evm:/media/sda2/opt/bin# findutils-find / -name sda1

Segmentation fault

root@dm3730-am3715-evm:/media/sda2/opt/bin# findutils-find / -name sda1

/dev/sda1

/dev/.udev/names/sda1

^C  

then no more talky-talky 

So it looks like findutils calls the same seg fault generating code......

I'll see if I can find out more. 

[geert56]

@avman

Did you follow my post to the letter? Did you do this?

"in /home/connect.sh change:
udhcpc -h "www.goflexsatellite.com" -n
to:
udhcpc -i eth0 -h "www.goflexsatellite.com" -s /etc/udhcpc.d/50default"

Otherwise you don't get a proper IP address.

Does the findutils utility use shared libraries in /opt/lib? If so,

make sure LD_LIBRARY_PATH is set to /opt/lib. (I put it in /etc/profile)

[Correction]

My /usr/bin/find does not work fine.I get seg faults too. Mind that I mount my hard drive with

ntfs-3g and not ufsd. Maybe you root file system is somehow corrupted.

You could always do a firmware re-install.

Here'smy run of /usr/bin/find

root@goflexsat:~# find / -name sda1
/dev/sda1
/dev/.udev/names/sda1
/sys/devices/platform/ehci-omap.0/usb1/1-2/1-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
/sys/class/block/sda1
Segmentation fault

Maybe it's a busybox problem.

[avman]

My Linux skills are no match for yours geert, but I'm pretty good at making typo's, so yes, I've double checked line 81, just to be sure

As I don't have a working "find", where is ld.so.conf on GFS?

[geert56]

avman,

there is no ld.so.conf on the GFS!

You could download the firmware and then mount the root file system as a jffs2 image.

That way you can explore it offline on a linux box. That's what I do.

Are you sure your network uses WPA2? Did it ever work without encryption?

That's the way to proceed: switch off all encryption on your router also MAC address

filtering. Then try to do /home/connect.sh avman 1. The 1 meaning an OPEN network

I hope (maybe it should be a 0; try both). Also check your network with get-scanned-networks.psp.

My /usr/bin/find does sef fault on find / -name sda1, but works fine when run from another

directory, like find /media -name sda1. Instead of using find consider installing mlocate.

Its command "locate" very quickly finds a file from a database created with updatedb.

By the way, updatedb can use a config file /opt/etc/updatedb.conf. Put this line in it:

    PRUNEFS = "proc sysfs tmpfs"

My guess is that the "find" (and also updatedb") seg faults because it tries to explore the

proc, sysfs, and tmpfs file systems.

[avman]

geert,

that's why I couldn't find it manually then

I've a bit of experience with "yaffs2" from my media player (I converted that into a "home made" GFS, but Seagate has nothing to fear about competition from that - about 4 times GFS's size ;-) ) & I can easily peruse the directory structure on my desktop mac, but not so far tried jffs2, so I'll need to do some research there, thank you.

 WPA2, none, plus other forms of encryption, yes. It's a relatively high end router, Apple "AEBS" & works fine.

I suspect that JSON failure string was because I had my SSID hidden. It looks like GFS can't cope with that?

Here's what I get with no encryption:

In server_startup (ap mode)

root@dm3730-am3715-evm:/home# ./connect.sh avman 0
In if (connect.sh) /tmp/device_ssid exist
Killing lighttpd...
Killing python...

Killing dnsmasq...
Killing udhcpd...


ssid = avman
Enc = 0
pass =


Flag set...(given ssid matched with scanresults)
ssid = avman
pass =
enc = 0
Running DHCP Client...
udhcpc (v1.13.2) started
udhcpc: exec /etc/udhcpdc.d/50default: No such file or directory
Sending discover...
Sending discover...
Sending discover...
udhcpc: exec /etc/udhcpdc.d/50default: No such file or directory
Sending discover...
Sending discover...
Sending discover...
udhcpc: exec /etc/udhcpdc.d/50default: No such file or directory
Sending discover...
Sending discover...
Sending discover...
udhcpc: exec /etc/udhcpdc.d/50default: No such file or directory
^CThe obtained IP is :
IN else
Obtained IP address is 192.168.0.1
 rm: cannot remove '/tmp/try_old_connect': No such file or directory


mode = 1


In server_startup (ap mode)
^C

------------------------------------

50default does exist, so unsure what's happening there yet!

I'll try a later BusyBox today, as it's a pain having a broken "find"! I'll also look at mlocate.

It's strange because "find" works just fine from root level on the mips® box, & it has the proc etc. directories just like GFS.

[geert56]

avman, I hope that by now you found your typo in

/etc/udhcpc.d/50defaults.

There no extra "d"!

[avman]

geert,

dank u wel

Strangely though, GFS didn't respond to a broadcast ping, so I had to guess its IP initially. Subsequent ping to its IP are fine though.......

Right, on to the "find"