Posted by – April 5, 2011

I had a WRT54G (version 8) left over and thought of using it as either a repeater or a client: however, I believe that since V7, Cisco has stopped supporting client/bridge modes in their (consumer routers). I’ve been wanting to convert this router over into DD-WRT, but never really had time. Today, was the day and out of memory to get this going:

  1. Download the two files, the vxworks app and micro DD-WRT.
  2. Hard reset your WRT54G (keep the ‘reset’ button pressed for 20+ seconds).
  3. Set your computer to get the IP automatically and connect it to the router.
  4. Load up the admin page of the Linksys router and go to the Upgrade page and select the ‘vworkskiller’ file. After upgrading, the router will reboot. Note: at this stage, there’s no Linksys admin pages anymore.
  5. use tftp to upload the last file to the router
    1. Windows/DOS: tftp -i put dd-wrt.v24_micro_generic.bin
    2. Linux: atftp –option “mode octet” –verbose -l dd-wrt.v24_micro_generic.bin -p
  6. After upgrading, it will take a minute or so for the router to reboot. Browse to (using root/admin credentials) and you should be good to go and see the pretty DD-WRT admin pages.

Note: no guarantees here. I’m not responsible for any ‘bricking’ of your router.

Update: I did the tftp part on my linuxen b0xen: surprisingly, tftp isn’t installed by default on Windows Vista and higher.


You asked: Linksys WPSM54G

Posted by – February 3, 2010

My WPS54G just died yesterday: this is a Linksys (nee Cisco) Printerserver that supports a whole slew of USB based printers. I had it tied up to my Canon MF5650 printer and if I remember correctly, installing was as easy as.

So, to the local computer grocery chain where they only had the WPSM54G (Linksys info page) for a price of 89.99 CDN. The sad part was that we had to look for the device because obviously, not too many people will buy these printer servers. That is probably because most printers nowadays come with an ethernet connection. Additionally, installing printer servers can be confusing and I suspect many people will just give up after a couple of tries.

Here’s my first tip: You do not need to install the Linksys drivers or software. On all your local computers that need to have access to the printer, you only need the proper printer drivers and most likely you already installed those drivers.

So, here goes again:

  • Wire up the device up to your network. By default it will automatically get an IP address (DHCP): it shouldn’t be too hard to find it on the network.
  • Open up the ip address in your favourite webbrowser: leave the username empty and enter the default password (“password”).
  • Set the IP address to a static IP address, change the password and set the wireless router properties. Here comes something that got me stuck first. For some reason, it’s supposed to work on wireless and not on wired. I have not been able to get it to work on both: so, make sure you set the proper gateway and credentials to your router. After you installed the firmware, take out the wired ethernet cable.
  • Make sure you get the latest update of the firmware: 1014 is so shoddy that it didn’t detect my Canon printer. Version 1019, made the difference for me.
  • At this stage, it should be time to start setting up your Windows machines and the principle is the same as described in the posting regarding the WPS54G, that is in 5 easy steps: 0. Add Printer 1. Local Printer… (uncheck auto detection) 2. Create a new port (TCP/IP) 3. Enter IP address (generic network card) 4. Select the proper printer and you should be go.

Afterthoughts: We had tried to print pages on our old printer server the day before and the moment the 1019 update was applied, these prints made it through. Note that I used the same IP address for the new server: so the moment the printer started spitting out pages from yesterday, I knew that the printer should be working, despite what the Linksys software suggested to me (“No Printer found, LOL, try again”). In short, the software is extremely lacking here and you can take my advice above at heart: There’s no need to install that Linksys crap load. Make note of the printer support page though (if you have a multi-functional printer…)


My. Suck.s

Posted by – November 30, 2007

Earlier, I was looking for an OpenWRT version that could run my Linksys WRT54G. This is where I found out that the hardware version of my router (“8″) isn’t supported. Aw. Apparently, Linksys switched to a propriety embedded OS, the [infamous] VxWorks. Aw2.

There are holy wars being fought about routers, particularly which one sucks and which one doesn’t. Personally, I haven’t had many issues with Linksys hardware and the WRT54 I bought this summer (no review!) was a piece of cake to set-up. I wished I had bought the one with that extra USB slot, though.

Talking about that infamous VxWorks: it’s a real-time operating system (Wikipedia) which is competing hard against Microsoft’s Mobile/CE platform. It’s apparently ported to many processors and it powers (and powered) most likely your favourite spacecraft, including the Mars Pathfinder mission. There’s an interesting anecdote about how the software almost threw a kink in the cable, detailed in this article at Microsoft Research (with an interesting follow-up from the JPL).


Review: WPS54G

Posted by – November 3, 2007

For aWPS54G long time I’ve been looking for a print server so that I can access that Canon MF5xxx printer from the network, without resorting to leave a computer on all day (you know, via the regular shared printing mess). I finally managed to get the Linksys WPS54G (product description) from the local computer chain. It’s an older model so it is not too expensive (they go for 69 to 79 CDN). If you need access to a multi-purpose printer (you know the ones with faxing and scanning), you probably want to look for the WPM54 series of this device.

If you’re familiar with Linksys devices, the setup is always the same: generally, you grab an extra network cable, connect the device to your computer connect to the web-based configuration screen (using the default IP address, which is generally at, or the IP-address provided in the manual) and start changing settings. This isn’t true for the WPS54G: the default IP address is nowhere to be found in the manuals, so the only way to find out the device’s IP address is to start up the Print Server setup program and follow the on-screen instructions. I stopped halfway (right before it wants you to setup the wireless section) after the setup program revealed the Print Server’s IP Address (you guessed it, the device will look for a DHCP server first). This is where I changed the IP address and other settings straight from within the device’s web server (which will generally require a restart of your computer).

If you’re not familiar with networks and networking, the setup program will probably do for you, I guess: however, if you’ve found the IP address of the WPS54G, I’d recommend to assign a static IP address to this thing. You may need to make changes to your router, though.

The next step is to configure your desktop computers: there’s a portion in the setup program that will do this for you too but you can ignore that. If you’re on Windows, make sure that your computer’s workgroup matches the one you’ve setup on your print server. For all Windows versions, you generally go to Printers & Faxes, select ‘Add Printer’. When the Printer Wizard comes up select the ‘Local Printer attached to this computer’ (make sure to uncheck ‘automatically detect and install’). Then, ‘create a new port’ (type of port TCP/IP). In the next screen enter the IP address of the Print Server (use generic networking card/port), select the printer from the printer drivers list (notice that most likely your printer driver has already been installed because you have been printing to this printer before…) and then, print out your test page.

For the rest, the WPS54G works as promised in the flyers: it’s reasonably fast but it gets a bit hot though after printing a couple of jobs. You may also wish to upgrade to the latest firmware (you can download the latest firmware from here). You can configure a couple of goodies or ungoodies from within the device’s webpanel: I think I saw a couple of settings that allow you to send print jobs via e-mail, which may fill your uh, needs. And that’s basically it.

Nowadays, a lot of printer models come with networking capabilities. If you’re looking around for a new printer, it’s a good idea to consider one with an ethernet connection.

Feb 2nd, 2009: It looks like the WPS54G died on me. I’ll have to either look for the same model or see if I want to go look at the M version

Feb 4th, 2009: And here is the WPSM54G.


More Computer stuff

Posted by – August 11, 2006

After BEFSX41 fiddling for hours with a 7100 AP to discover that it does not want to work together with my Linksys router, I decided to give up for now. I suspect that it just doesn’t like retrieving an IP address from the router.

Talking about that router, initially I wasn’t happy with it, but after applying the latest firmware upgrade (January’s one, I don’t see a reason to upgrade to the June one) it has been running steadily. Compare that with D-Link: the last time there was a 7100 firmware upgrade was years ago.

There might be a chance that one day OpenWRT will support that D-Link one. For now, back to the 11 MBs AP.


Firmware. And WordPress bugs.

Posted by – January 28, 2006

Just new_wev3ersa2.jpga day ago, I discovered that Linksys finally has issued a firmware upgrade for their BEFSX41 broadband router/firewall. I discussed the router before and I’m reasonable happy with it. There are always little problems with it though: for example a traceroute literally drops the connection. When a connection is dropped, I always find it cumbersome to reconnect: for some kind of reason, the internal firewall just starts dropping packets. Lookin at the version info, it looks like some of these problems have been fixed:

1. Tracerouter in WAN will cause the device to reboot.

I noticed a couple of irritating bugs in WordPress ’2.0′, particularly around the new ‘Image manager’: sometimes the ‘image menu’ doesn’t want to pop-up: my java-script debugger returns a couple of errors like ‘doPopup is not defined’. However, there are more messages popping up before that error actually starts to appear:

Error: missing ; before statement
Source File: xxxx
Line: 28, Column: 167
Source Code: aa[904] = 'Some URL + Code'

Today, I noticed that my harddrive is getting full. Panic. 40 Gig. Only 1.3 Gig left. I’m cursed with something human: hamsteritus. Oh, I see: there are 13 ISO images of Debian Sarge in my jigdo folder: makes up for 8 GB. Reminder to self to buy CD-R/Ws.


What’s on your Internet today?

Posted by – April 19, 2005

I have been running the LinkSys router (and the WAP) since April 10th, so I might just spill my gall: the last time LinkSys issued a firmware update for the BEFSX41 was almost a year ago. Isn’t that a little bit too long ago?

So once in a while, the router acts like it’s in a stalemate: it’s not frozen, but the internal firewall just doesn’t let any packets through. The only way to correct this, is by turning off the firewall for a couple of seconds. My current network (as discussed before) isn’t really setup the right way either: the router is connected to a hub first, which then is connected to the cablemodem. It works, apparently and that’s the main thing that counts.

Also, I’ve managed to get an extra domain name (strncpy.org), as requested by Alfons. I have no idea why he liked that name, but it must have to do with this rant. Don’t ask me, but is it safe? As you noticed, this page can now safely referred to (and linked to) as ‘hoogervorst.ca’. Oh, the fun.