Get the brcm47xx firmware image openwrt-15.05-brcm47xx-mips74k-linksys-wrt320n-v1-squashfs.bin from https://downloads.openwrt.org/chaos_calmer/15.05/brcm47xx/mips74k/

Upgrade that via factory firmware's Administration → Firmware Upgrade selection.

I needed 2,4ghz wireless “n” so i went for the propertary driver (kmod-brcm-wl) from start,
i didn't have time to play around with the open source drivers in CC (final).

I have tested this one driver (kmod-brcm-wl) now in CC (final), and it works fine on my WRT320N (bought in sweden).

I have earlier tested all the available broadcom drivers including kmod-brcm-wl for this router, and all have failed to work in various ways with CC develop release (unknown revision, was a few months ago..)

After that i went to fallback on BB as this wikipage told it was untested WiFi-wise. B43 driver works in 54mbit mode, and the link drops randomly, alot! if lucky, it worked 5mins without dropping. kmod-brcm-wl driver did not work at 'N' speed (300mbit) if i remeber correctly it worked at 54mbit mode but i dont remeber at what extent as i continued to use b43 even though it dropped connection.

i'm sure someone will get the open source drivers to work sometime.. then update the wiki with more subcategorys for the other drivers..

With CC (final) it works and whats needed as post-install on a vanilla installation (installation part above).

• install packages.. “opkg install kmod-brcm-wl wl wlc nas”

• Disable B43 modules from loading at boot.
• remove file “/etc/modules.d/b43” (or remove b43 kmod package)
• or modify that file so it says “#b43” instead.

• New/reconfigured “/etc/config/wireless”.
  • back it up on your desktop if you want or just overwrite as i did.

config wifi-device 'wl0'
  option type 'broadcom'
  option disabled '0'
  option channel '4'
  option txpower '16'

config wifi-iface
  option device 'wl0'
  option network 'lan'
  option ssid 'OpenWrt'
  option key 'passphrase'
  option mode 'ap'
  option encryption 'psk2'

• reboot and wireless should be up and running after the reboot (or init the modules and run the commands in the post below

tnx goes to this post where i found how to do it..

This guide on dmach.net can be used too. It's actually a better guide.

Mirrored from: http://www.jiggy.ca/2011/03/how-to-mod-ciscolinksys-wrt320n-to-e2000/ Which is no longer present (checked 2013/06/24)

Posted on March 3, 2011 by Dave Kincade

This is a companion piece to my article explaining how to powerfully network your house. While setting up two Cisco/Linksys WRT320Ns to use DD-WRT, I saw in the DD-WRT wiki page that upgrading the firmware to the E2000 model can solve some problems.

I’d just gotten the routers so I never got a chance to see what those problems are, but I’m a sucker for new firmware so I had to upgrade. buddee’s guide is great and includes everything you need to do the upgrade, but I had a bit of a headache after reading his post so I’m going to lay it out here.

1. You need DD-WRT on your router already. If you’re entering from my networking article, then you’ve just put on an older trailed build which is just fine.
2. Download a cfe_e2k.bin file which contains the actual configuration for the E2000 and another trailed DD-WRT build, but for E2000. Note: you may need to go to the guide to download the files.
3. Open the cfe_e2k.bin in a hex edior. As per buddee’s recommendation, HxD is a good choice. I just grabbed the portable version since I don’t see much more hex editing in the near future.
4. You need to modify three values that are right next to each other. I found it easiest to just search for “mac=” and let HxD find it. buddee lists the offsets as starting at 0x3E098.
5. The MAC address, serial number (SN), and PIN are all found underneath the router. Replace the values in the file with the values on your router. Make sure you leave the colons where they are, and I used capital values for the alphabetical hex characters, if it matters. Make sure you work in the “text” area (i.e. the part you can actually read). Just save when you’re done.
6. Backup your WRT320N CFE by going to http://192.168.1.1/backup/cfe.bin. It’ll take a minute so be patient. I’m honestly not sure how you’d get the chance to restore it if something goes wrong, bit it’s better to have it.
7. You need to get the CFE to the router. I haven’t found a better way that buddee’s suggestion to use winSCP. Enable sshd by going to DD-WRT via http://192.168.1.1 and going to “Services” and scrolling down to sshd. The defaults (password login, no SSH TCP forwarding) should be fine. Apply the settings.
8. Open winSCP and set up a new connection to 192.168.1.1 with username as “root” and whatever password you’ve set up for the router. Make sure you set the protocol to “SCP” since it will fail even with the SFTP fallback to SCP.
9. Transfer your cfe_e2k.bin file into the /tmp folder. You can close winSCP now.
10. Open up a telnet session to the router. Windows comes with a telnet client, which you can enable by typing “Turn Windows Features on or off” into the start menu or find the option in the control panel.
11. Once telnet is enabled, open a command prompt and enter “telnet 192.168.1.1″ and enter the same credentials as before (root / password that you know).
12. In the telnet session, enter the following commands:
13. “cd /tmp” – navigate to the /tmp folder where the cfe_e2k.bin file was stored.
14. “mfe unlock cfe” < –note that this may now be “mtd”
15. “mfe write -f cfe_e2k.bin cfe” – actually write the new CFE. This is the only really sensitive part of this process, so make sure you don’t disrupt the process. After it’s finished, you’re done with telnet, winSCP, and HxD.
16. Now you want to update the firmware to a E2000 version. It’s probably a bad idea to reboot the router before updating the firmware. Go to http://192.168.1.1/Upgrade.asp and select the trailed E2000 build downloaded earlier, and make sure you select “reset to default settings”. You may be able to go right to a new DD-WRT build rather than this older trailed build but I didn’t want to risk it.
17. After the firmware update has happened, you can go ahead and update to a newer firmware. If you go to http://192.168.1.1/Status_Router.asp, you should see something like this:

Congrats!

How to add tags