[isf-wifidog] Re: Q: Anyone have wifidog working on a GS usingwhiterussian

[Kenneth Craft]

Noticed you mention a G unit that is in disrepair.

I had 2 units here that were "bricked" due to failed firmware upgrades. The
router was still getting an IP, but nothing else worked. I followed the
following steps and was able to get them back up and running:

1. On my "Windows" machine, set the IP Address to 192.168.0.2 (the router
takes 0.1 for itself)
2. In the Driver settings of the card (in device manager) I set the speed to
Half duplex 10Mbit.
3. I held the reset button down and powered on the router. After 30 seconds
released the reset. (Linksys said so)
4. I setup my tftp to push the openwrt firmware. Same way you did using
microsoft tftp. Had to run it a few times for it to work.

Both of the "broken" routers are now running whiterussian, one is running
wifidog the other is not, for some reason svn isn't installed on that
router. When I have time I'll figure out why.

Hope that helps you get your G back working.


-----Original Message-----
From: wifidog-bounces at listes.ilesansfil.org
[mailto:wifidog-bounces at listes.ilesansfil.org] On Behalf Of Wireless Guy
Sent: Tuesday, August 29, 2006 1:59 PM
To: wifidog at listes.ilesansfil.org
Subject: [isf-wifidog] Re: Q: Anyone have wifidog working on a GS
usingwhiterussian

Raj,

I think I finally got everything straight on my GS unit so here's what I can
tell you I did.

You are correct that the bin file is the firmware for the device itself with
openwrt on it.
I had an old version of openwrt on there already so I could not just use the
linksys interface to upgrade the device.

What I did from my windows box (don't stone me for not having a linux laptop
) was to run:
tftp -i 192.168.1.1 PUT openwrt-wrt54gs.bin

and then plug in my router.

You may have to play with this a bit as the tftp session will only go thru
during the very beginning of the routers boot sequence.

I was very lucky to get it on the first try (no such luck with my G unit
which is still in disrepair).
once installed the device will automatically reboot itself.

You should be able to connect with normal telnet to 192.168.1.1 at the main
screen you can then assign a passwd for root.
on the next reboot telnet won't work and you'll need to use ssh.

that reboot can take a while b/c ssh needs to generate its keys.

Don't forget that once all that is done you'll need to go into /etc and do a
ls -l remove all the sym link files (e.g. rm dnsmasq.con) and copy over the
files from rom (cp /rom/etc/dnsmasq.conf . )

I'll keep going a bit in case you're actually following this process...

once all files are replaced you can use vi to edit some of the files.
I added my three nameservers to resolv.conf

you can then edit your ipkg.conf to have something like src wfd
http://downloads.openwrt.org/backports/rc5

run ipkg update
then try to run an ipkg install wifidog

If all goes well it will install itself and then you can modify the
/etc/wifidog.conf file to suit your needs.

Personally, I've had a lot of issue with dependancies but hopefully you
won't.
Just member that if things fail be sure to do a ipkg rmove wifidog before
you try anything else.
(cleaning up ipkg is not much fun.).

- W







--
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006
 
  

-- 
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/362 - Release Date: 6/12/2006