v4.00.7 for the G and v4.50.6 for the GS

- Adds SecureEasySetup push button support
- Resolves large file transfer issues
- Resolves issue with enabling TKIP after enabling WEP
- Updated QoS features
- Resolves issues with multiple Access Restrictions policies
- Resolves issue where multicast breaks when MAC filter status changes

WRT54G: ftp://ftp.linksys.com/opensourcecode/wr … 4.00.7.tgz
WRT54GS: ftp://ftp.linksys.com/opensourcecode/wr … 4.50.6.tgz

For those who find these things interesting...

The firmware looks like it's compressed. Using some other details I found on the web, I uncompressed part of the bin using instructions from http://www.faqs.org/docs/Linux-HOWTO/Li … HOWTO.html. (see step 6)

dd if=firmware.bin bs=60 skip=1 | zcat > comp.img

Unfortunately, I hit a wall from there.. The kernel on my debian box doesn't have cramfs installed. Using strings, however, I saw many references to squashfs - perhaps Linksys has switched?

If anyone makes further progress mounting this, please let me know. I'm interested to see what's hidden that wasn't included in the source.

The following command will give you the embedded squashfs:

dd if=WRT54GV3.1_4.00.7_US_code.bin of=squash skip=1 bs=686068

I was able to mount it with

mount -t squashfs -o loop squash ost/

OK, I extracted the firmware using those commands.  Now tell me, how the heck did you find the beginning marker for the squashfs partition?  Please, tell me everything, because I can only assume you're looking for a particular hex string.  Using hexdump is no good, because it wraps the lines and you can never guarantee you'll get the string of hex characters you're looking for in one chunk.

Thanks,

Kaldek

-> http://www.google.com/search?q=squashfs+magic
The four "magic" characters are: hsqs . (68 73 71 73 h)

Ah right.  So if I had half a brain and realised that these markers are referred to as "magic" markers I would have gone to google and found it hours ago.   Sheesh, 11 years in the biz (not development) and entire areas of fact slip you by...

Anyway, does anyoneknow of a hex searching tool like hexdump, that can search an entire file for a particular series of characters, and *then* format the output (as opposed to dumping the file, formatting it, then using grep to find te magic marker - which causes the problem I mentioned in my previous post).  I actually managed to find "hsqs" in this particular firmware image using hexdump, because it was thankfully in the middle of a line when dumped to ascii format.

Kaldek

(Last edited by kaldek on 5 Jul 2005, 05:02)

I usually just use hexedit which is included in most distributions I think (http://merd.sourceforge.net/pixel/hexedit.html)

With that editor you can quickly search for ascii strings or hex strings