Topic: WHITERUSSIAN RC2

WhiteRussian RC2 has just been released -
http://downloads.openwrt.org/whiterussian/

This is mostly a bugfix release; there's no new features but there are several important stability patches.

Re: WHITERUSSIAN RC2

hi,

just some more notes...

It would be really cool if you update your routers and test these images. Many bugs from rc1 are fixed.
WDS should work again. pppoe and pptp is now started via ifup.pppoe and ifup.pptp. Please add problem description and patches to this thread.

And all problems with the old v1.1 routers are fixed! thx nbd!

We will not any new features to white russian, so do not ask about. (feature freeze)

Developers of new packages should use cvs HEAD and provide patches for it.


good luck
wbx

Re: WHITERUSSIAN RC2

just some silly questions.
Are there big differences between today cvs head and white russian rc2?
I'm actualy using a RC1 jffs version.
If I flash a new version, what will be updated? is the root jffs filesystem erased?
If I backup my old install, what do I need to upgrade, only the kernel modules?

Thanks for your great work.

My hotspot managed by http://worldspot.net with openwrt and coovachilli

Re: WHITERUSSIAN RC2

all is answered here:
http://downloads.openwrt.org/whiterussian/00-README

Re: WHITERUSSIAN RC2

>Are there big differences between today cvs head and white russian rc2?

sure. cvs HEAD is different. more packages, many changes in the buildsystem to build more then broadcom specific kernels, preliminary support for texas instruments based boards (ar7) like linksys wag54g...

Re: WHITERUSSIAN RC2

I've been trying to get WDS and WPA-PSK working between a WRT54GS V1.1 and V2.0 box.  This post details my progress http://forum.openwrt.org/viewtopic.php?pid=9711#p9711

I just installed whiterussian RC2 and I once again started with a clean slate by doing a mtd erase nvram.  I then made all the settings necessary to get WDS working and I noticed that nvram get wl0_hwaddr still does not show the MAC address of the radio.  From previous experience I noticed that wl0_hwaddr usually displayed the same MAC as that listed for eth1 device.  Do I still have to set wds with the wl wds <my other box MAC> command or does nvram set_wl0_wds work?

I haven't actually tried to ping the other box yet as I'm at work and haven't done much with RC2 other than flash it, clear nvram and make a few settings.  I'll try to get WDS going today and report back on what I've done.

Should I just try and get it going in the Linksys firmware first then load OpenWRT?  I've seen a post to that effect.  I'd like to hear from someone who has started from scratch like me.  I think all these posts and instructions on the subject are leaving out key settings that I probably smoked when I did the erase nvram to go back to defaults.

Thanks in advance for advice & info.

Re: WHITERUSSIAN RC2

Some advice: Ignore the unset nvram variables like wl0_hwaddr. Just grab the mac address from iwconfig or ifconfig.
For making WDS and WPA-PSK work, you need to install the nas package (just use ipkg update; ipkg install nas).
You also don't need the wl utility at all. Set up WPA as usual, then set the wl0_wds variable to the mac address of the other router. After that run /sbin/wifi or reboot.

Re: WHITERUSSIAN RC2

nbd wrote:

Some advice: Ignore the unset nvram variables like wl0_hwaddr. Just grab the mac address from iwconfig or ifconfig.
For making WDS and WPA-PSK work, you need to install the nas package (just use ipkg update; ipkg install nas).
You also don't need the wl utility at all. Set up WPA as usual, then set the wl0_wds variable to the mac address of the other router. After that run /sbin/wifi or reboot.

This is were I'm getting into the weeds possibly.

The posts on the forum that I've seen don't really mention the fact that nvram get wl0_hwaddr does nothing, they only say that nvram set wl0_wds is broke and say to use the wl wds command to do the same thing.  I'm only seeking the truth!  Which is it and is RC2 still affected by these problems?

In the past I've installed the nas 3.90.23-3 package.  Is this still the one to be using with RC2 as I noticed a later package in the directory?

Are the hotplug, S41wpa, and nas sym links all OK in this package for use with RC2?

Re: WHITERUSSIAN RC2

Hi,

I installed the whiterussian rc2 on my WRT54g 2.2.
The problem is id does not work, I cannot ping the
device any more. I tried several times to install
the squashfs release (I did a reset to factory defaults
before, I upgraded from the Linksys firmware),
the same outcome, nothing works. Any idea?

Georg

Re: WHITERUSSIAN RC2

tty56 wrote:

Hi,

I installed the whiterussian rc2 on my WRT54g 2.2.
The problem is id does not work, I cannot ping the
device any more. I tried several times to install
the squashfs release (I did a reset to factory defaults
before, I upgraded from the Linksys firmware),
the same outcome, nothing works. Any idea?

Georg

I've been using the jffs2 version of RC1 & RC2 because I'm lazy (or plain dumb) and like the fact I can do wget, ipkg install etc., and things happen like a normal linux box and I don't have to bother with killing symlinks etc. on the squash version.

About the only thing I haven't tried yet is to load the Linksys firmware and get everything working and then load RC1 or RC2 and see what the difference is in nvram settings from what I have now.  It is making me pull my hair out and I don't have much to start with.

Re: WHITERUSSIAN RC2

Thanks hutchman, I tried the jffs version and it works. Seems to be a squashfs or ididnotreadthemanualcarefullyenoughtousesquashfs problem.

Re: WHITERUSSIAN RC2

nbd wrote:

Some advice: Ignore the unset nvram variables like wl0_hwaddr. Just grab the mac address from iwconfig or ifconfig.
For making WDS and WPA-PSK work, you need to install the nas package (just use ipkg update; ipkg install nas).
You also don't need the wl utility at all. Set up WPA as usual, then set the wl0_wds variable to the mac address of the other router. After that run /sbin/wifi or reboot.

Update on my progress.

Just to clear up some confusion from other posts I've read, I took your advice and set wl0_wds like you normally do on whiterussian RC2 and DID NOT use the wl wds command.

I was able to finally get WDS working with RC2!

Now I'm on to trying to get WPA with aes going.

Re: WHITERUSSIAN RC2

.... and there was much rejoicing!

I happy to report I have WDS WPA psk working with whiterussian RC2.  I used the nas 3.90.37-2 package from the whiterussian non-free download directory.

I started off with a nvram clean slateby doing a mtd erase nvram.  I set the nvram settings according to the links mentioned in my previous postings in case anyone else is having the same trouble I have had in the past and needs a roadmap to follow.

Great job guys!  I'd kiss you but I'm not that kind of guy.

14

Re: WHITERUSSIAN RC2

I flashed RC2 over an old version of openwrt from sometime last year and it works great on my WRT54GS

Very good work and really good welcome banner with useful information smile

Re: WHITERUSSIAN RC2

I flashed my Asus WL-500g Deluxe with openwrt-brcm-2.4-squashfs.trx image.
After flashing with mtd -e linux -r write /tmp/openwrt-brcm-2.4-squashfs.trx linux i get:

  1 All bugs added by David S. Miller <davem@redhat.com>         
  2 VFS: Mounted root (squashfs filesystem) readonly.   
  3 Mounted devfs on /dev                            
  4 Freeing unused kernel memory: 80k freed
  5 Algorithmics/MIPS FPU Emulator v1.5    
  6 Using /lib/modules/2.4.30/diag.o   
  7 diag boardtype: 00000000
  8 /sbin/mount_root: 24: nvram: not found
  9 Unlocking OpenWrt ...
 10 mount: Mounting none on /proc failed: Device or resource busy
 11 mount: Mounting none on /dev failed: Device or resource busy
 12 umount: /rom/proc: No such file or directory
 13 umount: /rom/dev: No such file or directory
 14 init started:  BusyBox v1.00 (2005.07.18-21:49+0000) multi-call binary
 15 BusyBox v1.00 (2005.07.18-21:49+0000) multi-call binary
 16 
 17 Usage: ipcalc [OPTION]... <ADDRESS>[[/]<NETMASK>] [NETMASK]
 18 
 19 Calculate IP network settings from a IP address
 20 
 21 Options:
 22         -b      --broadcast     Display calculated broadcast address.
 23         -n      --network       Display calculated network address.
 24         -m      --netmask       Display default netmask for IP.
 25         -p      --prefix        Display the prefix for IP/NETMASK.      -h      --hostname      Display first resolved host name.
 26         -s      --silent        Don't ever display error messages.
 27 
 28 
 29 Please press Enter to activate this console. jffs2.bbc: SIZE compression mode activated.
 30 eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.23.0                        
 31 PCI: Enabling device 01:03.0 (0004 -> 0006)                     
 32 eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
 33 device eth0 entered promiscuous mode                       
 34 device eth1 entered promiscuous mode

Errors found on line 8 and from line 16 to 28.

Olli has since left the OpenWrt project; these posts remain for historical reasons.

Re: WHITERUSSIAN RC2

So I tried to upgrade my Motorola WR850G to the new RC2.
I wget the file from my server and it is in .bin format.

I convert the file to .trx
     dd if=openwrt-motorola-squashfs.bin of=openwrt-motorola-squashfs.trx bs=32 skip=1

Output of command:
     root@OpenWrt:~# dd if=openwrt-motorola-squashfs.bin of=openwrt-motorola-squashfs.trx bs=32 skip=1
47743+1 records in
47743+1 records out

I then:
     mtd -r write openwrt-motorola-squashfs.bin linux

Output:
root@OpenWrt:~# mtd -r write openwrt-motorola-squashfs.trx linux
Bad trx header
If this is a firmware in bin format, like some of the
original firmware files are, use following command to convert to trx:
dd if=firmware.bin of=firmware.trx bs=32 skip=1

I then tried to TFTP and the TFTP times out everytime.
I have rebooted the Motorola manually and quickly, sowly, anyway I can think of... Still nothing, times out.
I have read all I could find on this process.

I am just at this point, Frustrated.
Is there a site with some good up to date information on the WR850G process.
I have RC1 running on the router currently, I just would like the new stuff.
Any suggestions?

Also I was looking for ways to forward ports to my lan from my wan, are there any good docs for the WR850G?

Thanks for all your help guys!!!!!!!
At this point I cannot even get back to the old Motorola firmware, I am sorta hosed. sad

17

Re: WHITERUSSIAN RC2

I should point out that all the binaries on the server are the exact same file, just with different headers.

motorola header + openwrt-brcm-2.4-squashfs.trx = openwrt-motorola-squashfs.bin
  wrt54g header + openwrt-brcm-2.4-squashfs.trx = openwrt-wrt54g-squashfs.bin
 wrt54gs header + openwrt-brcm-2.4-squashfs.trx = openwrt-wrt54gs-squashfs.bin

and similarly for the jffs2 files.

The linksys bin header is 32 bytes, the motorola one isn't .. doesn't make any difference because you're wasting time using the bin anyways; just download the trx file.

18 (edited by jeff 2005-07-24 17:51:08)

Re: WHITERUSSIAN RC2

For the record, I believe I tftp'd the firmware from the .bin file with no issues.

soelknight, did you mean to use this as a command? I see a .bin where I think you meant .trx .. but your "output" shows a .trx

soelknight wrote:

I then:
     mtd -r write openwrt-motorola-squashfs.bin linux

Output:
root@OpenWrt:~# mtd -r write openwrt-motorola-squashfs.trx linux
Bad trx header

Regarding tftp issues, make sure you are NOT hooked to your box via another switch. Connect directly to the box via ethernet and try hitting the tftp during different phases of the blinking light patterns.

Linksys WRT54G v3
OpenWrt 2.4.30 #1
White Russian RC2
:cool:

Re: WHITERUSSIAN RC2

I did mean the .trx and not the .bin, sorry about that.
I have tried multiple times trying to catch it, just not lucky I guess.

Should I be plugged into the WAN port of the Switch ports 1-4?
Cause I am in the switch ports right now... I will try soon here, I will let you know.

20 (edited by soelknight 2005-07-26 01:03:36)

Re: WHITERUSSIAN RC2

I did the tftp from my windows box from the WAN port and all the ports on the built in switch. Tried even doing it at many different times.

Command I am using is:
      tftp -i 192.168.1.1 PUT <firmware>.trx

This did it....
I downloaded just the .trx did wget from my server for the .trx file.
Did the mtd -r write <firmware name>.trx linux and it now is up to RC2.
Maybe this could be added for some release notes for the Motorola WR850G.

Thanks guys for all the help!

Re: WHITERUSSIAN RC2

Re: Motorola WR850G

I went through quite a hair pulling trying to get everything sorted out on the WR850G last month with RC1.  Here's the steps for debricking or updating or even reversing to the original Motorola firmware (yes, yes, I know -- it should go into the wiki.  When I have time, when I have time).  BTW, all my experimenting is done from Windows, so the intructions are Windows-centric:


!!Notes before flashing anything!!

The Motorola WR850G defaults to 192.168.10.1 on its LAN IP at boot, EVEN IF "lan_ipaddr" IS SET TO SOMETHING ELSE!  All your TFTP'ing will have to be done from a 192.168.10.x address.


Updating a virgin WR850G:

1. Follow the instructions in the wiki: http://wiki.openwrt.org/OpenWrtDocs/Ins … 305b71bdd1


Reverting an RC1 or RC2 WR850G to the original Motorola firmware:

1. Open up a hex editor and load in the Motorola firmware (I use HHD).
2. Delete the first eight bytes (everything before "HDR0") and save.
3. Make sure your "boot_wait" NVRAM value is set to "on" and saved (I use "Putty" for telneting/ssh).
4. Set your local machine's IP address to 192.168.10.5 (or anything between 192.168.10.2 and 192.168.10.254) and mask to 255.255.255.0.
5. Open up a console window and change to the directory the Motorola firmware is in.
6. Type in: "TFTP -i 192.168.10.1 PUT filename.bin" where "filename.bin" is your Motorola firmware.  DON'T HIT ENTER JUST YET!
7. Unplug your WR850G, plug it back in and wait a second.
8. Now hit Enter in your console window.
9. Your TFTP transfer should finish in a few seconds.  WAIT AT LEAST 60 SECONDS FOR THE FLASH TO PROGRAM!
10. Unplug your WR850G and plug it back in.  You now will have the old firmware.
11. Reset your local machine's IP address and mask back to where it was (DHCP on my machine).


Updating an RC1 WR850G to RC2:

1. Download "openwrt-brcm-2.4-squashfs.trx" (NOT "openwrt-motorola-squashfs.bin"!!).
2. Make sure your "boot_wait" NVRAM value is set to "on" and saved (I use "Putty" for telneting/ssh).
3. Set your local machine's IP address to 192.168.10.5 (or anything between 192.168.10.2 and 192.168.10.254) and mask to 255.255.255.0.
4. Open up a console window and change to the directory the RC2 firmware is in.
5. Type in: "TFTP -i 192.168.10.1 PUT openwrt-brcm-2.4-squashfs.trx".  DON'T HIT ENTER JUST YET!
6. Unplug your WR850G, plug it back in and wait a second.
7. Now hit Enter in your console window.
8. Your TFTP transfer should finish in a few seconds.  WAIT AT LEAST 60 SECONDS FOR THE FLASH TO PROGRAM!
9. Unplug your WR850G and plug it back in.  You now will have the RC2 firmware.
10. Reset your local machine's IP address and mask back to where it was (DHCP on my machine).


Debricking a WR850G that has "boot_wait" set to "on":

1. Follow either one of the two intructions above.


Debricking a WR850G that did NOT have "boot_wait" set to "on":

1. Unplug the Wr850G and open it up -- unscrew the one torx screw in the back (you can use a hex key driver if that's handy), then pop open the cover.  You will have to CAREFULLY pry the top off with quite a bit of force.  Use your fingers.  If it feels like you're about to break it, don't worry, it's pretty tough -- just try to not bend the top, which will stress crack the plastic.
2. Locate the flash chip (right next to the internal antenna).  On mine it's an Intel TE28F320.  All the V3 WR850G's have this.  If it's an older V2 or V1, it might have an AMD chip.
3. Set your local machine's IP address to 192.168.10.5 (or anything between 192.168.10.2 and 192.168.10.254) and mask to 255.255.255.0.
4. Open up a console window and change to the directory the firmware is in.
5. Type in: "TFTP -i 192.168.10.1 PUT filename.bin" where "filename.bin" is the firmware.  DON'T HIT ENTER JUST YET!
6. Get a sewing needle or pin.  Count down on the LEFT side (lettering on the chip should be upright) to lead 15.  CAREFULLY insert the sewing needle between leads 15 and 16* -- it should NOT require any force.
7. Now plug in your WR850G while holding the needle in place.
8. Wait two to three seconds, then remove the needle.
9. Now hit Enter in your console window.
10. Your TFTP transfer should finish in a few seconds.  WAIT AT LEAST 60 SECONDS FOR THE FLASH TO PROGRAM!
11. Unplug your WR850G and plug it back in.  You now will have debricked the WR850G.
12. Reset your local machine's IP address and mask back to where it was (DHCP on my machine).
13. If you have loaded the OpenWrt firmware, telnet in and change the "lan_ipaddr" NVRAM value to 192.168.1.1 and reboot your router.

*The reason we use leads 15-16 is because those address lines are right at the beginning of the kernel firmware area in the flash chip, and if the CFE/bootloader detects a corrupted kernel, it will automatically go into a TFTP receiving mode.


For those of you who want to use a serial port and or JTAG adapter, I have some simple schematics/instructions that I will post later.  You can get all the parts at Radio Shack for a few bucks and don't require any special skills to assemble other than soldering.  (There are no ICs, only a couple of transistors, and everything can breadboarded).

Re: WHITERUSSIAN RC2

Hello,
The JTAG cable permit to recover every linksys?

Thanks.

Bye

Re: WHITERUSSIAN RC2

I am getting the following error messages (syslog) upon bootup of Whiterussian RC2:

  Jan  1 00:00:31 (none) user.info : /etc/init.d/rcS: 11: /etc/init.d/S50pppoe: not found
  Jan  1 00:00:31 (none) user.info : /etc/init.d/rcS: 11: /etc/init.d/S60ntpclient: not found

Although there are links in /etc/init.d
  lrwxrwxrwx    1 root     root           24 Jan  1  2000 S50pppoe -> /rom/etc/init.d/S50pppoe
  lrwxrwxrwx    1 root     root           28 Jan  1  2000 S60ntpclient -> /rom/etc/init.d/S60ntpclient

The actual files do not exist in /rom/etc/init.d

  root@OpenWrt:/rom/etc/init.d# ls -la
  -rwxr-xr-x    1 root     root         1049 Jul 16 03:09 S10boot
  -rwxr-xr-x    1 root     root          278 May 31 09:46 S40network
  -rwxr-xr-x    1 root     root         2601 Jul 17 15:38 S45firewall
  -rwxr-xr-x    1 root     root          605 Jul 19 08:47 S50dnsmasq
  -rwxr-xr-x    1 root     root          333 Jul 19 08:47 S50dropbear
  -rwxr-xr-x    1 root     root           47 May 31 09:46 S50httpd
  -rwxr-xr-x    1 root     root           32 May 31 09:46 S50telnet
  -rwxr-xr-x    1 root     root           80 May  9 08:02 S99done
  -rwxr-xr-x    1 root     root          258 Jul 17 15:37 rcS

Someone might want to fix this in the next release.


Regards,
  footrot

24

Re: WHITERUSSIAN RC2

footrot wrote:

Someone might want to fix this in the next release.

The jffs2 partition is not automatically nuked durring an upgrade; these links are left over from the last firmware. If you run firstboot it will create new links but unless you run firstboot from failsafe it won't delete anything.

Re: WHITERUSSIAN RC2

cp /wrt54/openwrt/build_mipsel/nvram/*.so /wrt54/openwrt/staging_dir_mipsel/usr/lib
cp: cannot stat `/wrt54/openwrt/build_mipsel/nvram/*.so': No such file or directory
make[2]: *** [install-dev] Error 1

Run into this error with whiterussian rc2 and current dev cvs.
Even when running completely default settings.
Building on Red Hat 9