|Home||Reviews||Tools||Forums||FAQs||Find Service||ISP News||Maps||About|
how-to block ads
Here is a great chart:
Chart by jdepew
Here is another list:
CDF0 = WRT54G v1.0 / ADM6996L Chipset / CPU 125Mhz
CDF1 = WRT54G v1.0 / ADM6996L Chipset / CPU 125Mhz
CDF2 = WRT54G v1.1 / ADM6996L Chipset / CPU 125Mhz
CDF3 = WRT54G v1.1 / ADM6996L Chipset / CPU 125Mhz
CDF5 = WRT54G v2.0 / ADM6996L Chipset / CPU 200Mhz
CDF7 = WRT54G v2.2 / BCM5325EKQM Chipset / CPU 200Mhz
CDF8 = WRT54G v3.0 / BCM5325EKQM Chipset / CPU 200Mhz
CDF9 = WRT54G v3.1 / BCM5325EKQM Chipset / CPU 200Mhz
CDFA = WRT54G v4.0 / BCM5352E Chipset / CPU 200Mhz
CDFB = WRT54G v5.0 / BCM5352EKPB Chipset / CPU 200Mhz
CDFC = WRT54G v5.1 / BCM5352EKPB Chipset / CPU 200Mhz
CDFD = WRT54G v6.0 / BCM5352EKBG Chipset / CPU 200Mhz
CDFE = WRT54G v7.0 / AR2317 Chipset
CDFF = WRT54G v8.0 / BCM5354KFBG Chipset / CPU 240Mhz
CDFG = WRT54G v8.0 / BCM5354KFBG Chipset / CPU 240Mhz
NOTE: The WRT54G v5.0 has 2Mb/8Mb Ram, it uses VxWorks OS and is incompatible with 3rd Party Firmware.
For more info see this thread: /forum/remark,14563605
CL7A = WRT54GL v1.0 / BCM5352E Chipset / CPU 200Mhz
CL7B = WRT54GL v1.1 / BCM5352E Chipset / CPU 200Mhz
CO61 = WRT54GL v1.1 / BCM5352EKPBG Chipset / CPU 200Mhz
CGN0 = WRT54GS v1.0 / ADM6996L Chipset / CPU 200Mhz
CGN1 = WRT54GS v1.0 / ADM6996L Chipset / CPU 200Mhz
CGN2 = WRT54GS v1.1 / BCM5325EKQM Chipset / CPU 200Mhz
CGN3 = WRT54GS v2.0 / BCM5325EKQM Chipset / CPU 200Mhz
CGN4 = WRT54GS v2.1 / BCM5325EKQM Chipset / CPU 200Mhz
CGN5 = WRT54GS v3.0 / BCM5352E Chipset / CPU 200Mhz
CGN6 = WRT54GS v4.0 / BCM5352E Chipset / CPU 200Mhz
CGN7 = WRT54GS v5.0 / CPU 200Mhz
CGN8 = WRT54GS v5.1 / CPU 200Mhz
CGN9 = WRT54GS v6.0 / CPU 200Mhz
CGN9 = WRT54GS v7.0 / BCM5354KFBG Chipset / CPU 240Mhz
Thanks to linksysinfo
- easy to use, home user oriented, good www interface
- oriented to the power user/WISP, focus on routing, repeaters
- some advanced features VoIP, Kaid, etc.
- hacker's version, rw file system, for do-it-yourselfers
- easy to install distro that runs completely from RAM
Courtesy of Sveasoft6
Links to third party firmware are offered "as is" by forum members and is neither tested nor endorsed by broadbandreports.com. In other words: While we encourage forum members to discuss their experiences with firmware, we take no responsibility if you break your stuff using it.
WARNING: Before flashing your router's firmware, be sure to match the download page with your router's version.
Many threads have discussed this multiple times.
It's really a matter of personal preference and what features you're looking for.
Here is a solution for those that want to turn on the logging capabilities of the WRT54G. This will send logs (syslog) to the destination set in the syslog command (change to suit your needs).
I use Wallwatcher but KIWI syslog or any other syslog based viewer works fine.
The current busybox .60 implementation used in the Linksys 3.x.x code (and hyperWRT2.0x) has some funny behavior with klogd and with cron so this solution does not use cron and kills and restarts klogd every 15 minutes. If you dont run much traffic you can change this to a greater number. Gamers and bit torrent uses should be fine with the 15 minute (960 seconds) setting.
Be sure to remember to 'enable' logging in the web interface!!
ALSO be sure to put the address of your logging PC in place of my address on the 'syslogd' line - Mine is 192.168.1.99 - your address may be different!!!!
In the Startup script:
/sbin/syslogd -R 192.168.1.99
echo "#!/bin/sh" > /tmp/loggit.sh
echo "while true" >> /tmp/loggit.sh
echo "/usr/bin/killall -9 klogd" >> /tmp/loggit.sh
echo "sleep 1" >> /tmp/loggit.sh
echo "/sbin/klogd" >> /tmp/loggit.sh
echo "sleep 960" >> /tmp/loggit.sh
echo "done" >> /tmp/loggit.sh
chmod 700 /tmp/loggit.sh
/usr/sbin/iptables -R INPUT 7 -j logdrop
/usr/sbin/iptables -R INPUT 1 -j logdrop -m state --state INVALID
Thanks to dellsweig for instructions, full thread: /forum/remark,11974955
Linksys getting too hot? Hereís a solution!
What you need:
-12 marble blocks.Each should be about 1cm x 1cm, but the longest dimension should not before than 1.5cm. You can also use wood as an alternative if need be.However, the marble blocks can probably be picked up at a tile store,or maybe even a hardware store.
-A fine sandpaper. It shouldnít be that fine though since you will need to sand down the marble a bit.
-Krazy glue. I prefer the advanced formula.
How you do it:
• Glue 3 blocks together. This will make up one leg. Youíll obviously have 4 legs in total. Also, glue wonít stick well to polished surfaces.
• Sand down the edges if you want to even up the blocks a bit. Remember, donít shorten them.
• Line the legs up,side by side, and then tape them together. You can now sand the top sand bottoms to make their heights even.
• If you want, you can put felt pads on the bottom of each leg. You can use the circular self-stick pads and then trim them.
• Glue the legs onto the bottom of your device as shown in the picture. Let the glue dry a bit before you put your device back.
You have just raised your device by about 3cm. This will allow heat to dissipate and prevent your device from overheating. Although this might seem like a bit of work, itís well worth it.
Here is another way courtesy of AdolphHitler
Linksys Product Owners:
There have been many complaints and consequences related to the poor cooling method employed in most Linksys products.
Linksys has designed their products to be conveniently stacked, but, this poses a risk as the ventilation for their products is a symmetrical series of tiny holes on the tops and bottoms of the products. Stacking Linksys products defeats the efficiency of their intended cooling method.
There have been many ideas on how to keep Linksys products cool and here's mine.
We will not be using anything expensive or hard to obtain. The materials used here can be found in your very own home.
Obtain normal tacks, sometimes called push pins and a small screwdriver.
Quick cheap solution for heat dispersion: Buy a plastic-coated wire kitchen cabinet plate rack at Wal-Mart for $5-6. There is a pic of a similar (but more expensive) item here: http://www.organize.com/dech3ticoor.html Each shelf is large enough to hold a unit and the wire lets heat get out easily.
System Info -- Provides general information such as MACs and revision information.
SysInfo1 -- Provides mainly hardware information
Site Survey -- Searches for other nearby access points (N/A on Linksys firmware)
Wireless Active Table -- Displays active wireless clients
Cysaja -- Provides non-human readable information on router.
Borrowed from wrt54g.com
To block a service:
1. Click on the "Access Restriction" tab.
2. Click "Enable"
3. Give your policy a name
4. Click on "Edit List of PCs"
5. Enter a reference to your PC. The IP address of my pc is 192.168.1.44 so I should type in "44" in the second set of fields. Click "Save Settings" then close the box.
6. Select the service you would like to restrict from the drop down box. Port 80 (HTTP) is in the list.
Last, click "Save Settings" and you shouldn't be able to access the outside world on port 80.
I'm using HyperWRT2.0b3 with a v1 WRT54G
1- Activate the VPN server in your win2k3 server (plenty of tutorial on the web for that part), forward the TCP port 1723 to your server and activate PPTP pass through aka GRE 47 on your router. At this point you should be able to connect to your VPN and ping the server
2- On your Win2k3 server, In routing and remote access go to your server/IP routing/, open the properties of NAT/basic firewall go to address assignment check the DHCP option and put in the IP of your DHCP server (usually your router or win2k3 server). Also go to Name resolution and check the first option.
3- Let your server digest the new VPN settings for a minute even though its supposed to work right away my server proved me the opposite. You also have to reconnect to the VPN.
4- Teh ( <- not a typo ) MAGIC setting and for the love of god someone explain to me why this works!, set your MTU to manual and set it to 1400.
Normally you shouldn't have to mess around with this setting but for some reason it just wouldn't work with my router.
Hope that helps!
Fred aka thecrazy
I'm pretty sure the MTU has to be set to 1400 because of the additional protocol overhead with the tunnel. If it was left at 1500 the stack could put enough data into a packet that the additional overhead of the VPN tunnel headers would push it over 1500 bytes.