Messages

1

Security and Networking / Almost Have Full Usb Networking With 5500

« on: August 02, 2005, 05:37:26 pm »

From Zauraus and using su mode:

route add default gw 192.168.129.1
route add -host  192.168.129.1 usbd0

Next, add the following in /etc/resolv.conf

nameserver ISPnameserverIP

I hope the above will help.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Just in case I had perhaps messed things up, I went back and flashed the ROM again from the OpenZaurus site.  I then followed [a href=\"http://openzaurus.org/wordpress/howto/usb-networking/]these instructions[/url] to get basic USB networking up and running.

Once I had confirmed that I was able to ping both ways (to and from Zarus and laptop), I executed the suggested "route" commands on my Zaurus and added the nameserver line to /etc/resolv.conf.

I'm still having serious connectivity issues from the Zaurus through my laptop.  I can get to my laptop, but not through it. Let me explain.

The ip my Zaurus is set to is 192.168.129.201.  I am able to ping from my laptop to this ip address with no problems.
The usb0 ip adddress on my laptop is 192.168.129.1.  I am able to ping from the Zaurus to this ip address with no problem.
The eth0 ip address on my laptop is 172.16.105.182.  I am able to ping from the Zaurus to this ip address with no problem.
The gateway from my network has an ip address of 172.16.105.1.  I am unable to ping this ip address from my Zaurus.  Similarly, I am unable to ping any of our nameservers by ip address.

What am I missing?  What am I doing wrong?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=90541\"][{POST_SNAPBACK}][/a][/div]

It sounds like you are doing it right. The problem is not so much on your Zaurus' side but on your laptop's side instead. Your laptop has to be setup to do IP forwarding for your Zaurus: right now your laptop is connected to the internet as a client, but it is probably not set up to act as a gateway for your Zaurus.
You can use iptables on your laptop for that. I can never quite remember how it is done in detail, but look at the HOWTO's on your laptop (should be in something like /usr/share/doc/HOWTO or somewhere around there): the ones that have "masquerading" (IPMasquerade and Simple-Masquerade?) will explain the issue in more detail and show how to set it up...
Hope this helps...

2

5x00 General discussions / Flashing 5500 First Time

« on: May 25, 2005, 11:21:21 pm »

Maybe you already checked this, but it sometimes Windows adds the extension ".bin" to binary files without telling you. Make sure that the kernel is named "zimage", not "zimage.bin"...

3

Linux Issues / Connection Issue Driving Me Nuts

« on: April 15, 2005, 06:26:05 pm »

I have a 5600 and I'm running gentoo. On both my laptop (PII 233) and my desktop (AMD 1.2Ghz) running kernel 2.6.11.5. running lsusb showss that the device is connected but I don't have usb0 appearing. I am not getting any errors in /var/log/messages. What could be wrong?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75435\"][{POST_SNAPBACK}][/a][/div]

If you don't have hotplug set up, you might have to do a "modprobe usbnet". Also, you might have to bring the appropriate network interface up ("usb0", I think)...

4

Accessories / Cf Or Sd? What Do You All Suggest?

« on: April 15, 2005, 11:46:46 am »

Dont forget to get a small CF card for flashing new ROM Images.

I have a 32mb card I use just for that purpose.

Oh, I believe that if you are interested in movie playback that movies may play better off of CF than they can off of SD  due to CF being faster.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75258\"][{POST_SNAPBACK}][/a][/div]

Thanks for the advice.

The 5500 that I bought came with an 8MB CF card, which I believe will work for flashing ROM images, and I was probably eventually going to pick up one of the Kingston 1GB CF cards in addition to an SD card of some yet to be determined capacity.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75362\"][{POST_SNAPBACK}][/a][/div]

Unfortunately, your 8MB CF card won't work for flashing roms - I believe you need at least 32MB (I think the rom image+kernel image just take up just a little more space than what a fat formatted 16MB card will give you).

5

Security and Networking / Aircrack - Fast Wep Cracking Tool

« on: April 14, 2005, 07:51:35 pm »

Maybe my last answer was a little too long winded....
I think there is absolutely nothing wrong with the binaries you are trying - it is just that aircrack needs to be able to allocate 80MB of memory, and that is impossible on any Z to date (even the newer ones only have 64megs of memory), unless you have a large swap file somewhere...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75250\"][{POST_SNAPBACK}][/a][/div]

OK, to test this what is the best way to set a swap file size on a SD card?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=75260\"][{POST_SNAPBACK}][/a][/div]

I am not the world's leading expert in doing this, but in order to create a swap file on your SD card, you could follow something like the following steps:
 

Code: [Select]

dd if=/dev/zero of=/mnt/card/swapfile bs=1M count=64
mkswap /mnt/card/swapfile
swapon /mnt/card/swapfileThis creates a 64mb file called "swapfile" on /mnt/card containing just 0s, initializes it as a swapfile, and then turns the swapfile on. As a more permanent solution, you would add an entry for this swapfile in your /etc/fstab, but the above steps will do as a quick and dirty method. You can check the status with

Code: [Select]

cat /proc/swapsand turn it off with

Code: [Select]

swapoff /mnt/card/swapfileMind you though that swapping on SD is probably agonizingly slow and puts some wear on your card (flash memory doesn't have the same amount of write cycles a harddrive has). I think I have used a swapfile on SD before, but only as a test, and certainly never for extended periods of time.
Hope this helps...

6

Security and Networking / Aircrack - Fast Wep Cracking Tool

« on: April 14, 2005, 06:49:38 pm »

Maybe my last answer was a little too long winded....
I think there is absolutely nothing wrong with the binaries you are trying - it is just that aircrack needs to be able to allocate 80MB of memory, and that is impossible on any Z to date (even the newer ones only have 64megs of memory), unless you have a large swap file somewhere...

7

Security and Networking / Aircrack - Fast Wep Cracking Tool

« on: April 14, 2005, 12:35:22 pm »

I looked at the aircrack source a while back. I believe the way it works (and I don't really know anything about it, so I might just be talking nonsense here) is by gathering statistical information about 24bit IVs that are part of each wireless packet.
In order to do this, aircrack allocates 5 bytes of memory for each possible IV - i.e. 5*2^24 = 80MB. Hence the program tries to allocate one big 80MB chunk of memory (cf. row 1012 in aircrack.c, version 2.1).
Since the Z has (at most) 64MB of ram (so your free memory is considerably less than that), you will need a big swap file in order to get this to work, otherwise it will always fail. So that's the error message you guys see.
Besides, I think that a capture file with enough packets in it will easily run in the hundreds of MB...
It seems like this whole endeavor is a little impractical on the Z.

8

Zaurus - pdaXrom / UCLX compressor

« on: November 04, 2004, 03:30:18 pm »

Hi pgas,

somebody already compiled uclx for arm processors: you can find on the old ZSI (www.killefiz.de/zaurus/, I believe). I have been using it for quite a while now, and it works fine with almost all executables I have tried.
It makes most sense on SD or CF cards, and I haven't really noticed much of a difference in startup speeds one way or the other.
You were right that it offers a slightly better compression ratio than jffs2, but in that case it also slows down execution times a little bit...
Beware that I have only tried this on a 5500, but I don't see why it should not work for the 860...

9

Angstrom & OpenZaurus / dev-img 1.5 - Problems in OZ

« on: September 16, 2004, 03:28:11 pm »

OZ doesn't have bash installed... "sh" is the built in busybox shell. It uses a slightly different syntax for defining functions in scripts.
Just replace "function mlink {... }" with "mlink { ... }" (i.e. just get rid of the word "function" in front of it).