Today I'm going to walk you through upgrading your router's firmware to the powerful open source DD-WRT firmware. Photo by puruan. *You'll be upgrading the firmware twice, first using the mini firmware, then using the standard. His special feature Hack Attack appears every Tuesday on Lifehacker.

Firstly, Is it advisable to install a custom firmware on my modem-router? Tai Real Football 2013 Crack Full Viet Hoa. If no issues in installing., 1.

How do i go about installing DD-WRT on Belkin N300 (F9J1002v1)? (Leaning towards DD-WRT. After googling i noticed this firmware seems to be widely used) 2.

Is the procedure model specific.should i do anything differently for my router? Which version of the firmware should i use? Note: The reason i want to change the firmware is to have bandwidth usage statistics for all pc's together at home.

Not sure which firmware has this feature. (Statistics for individual PC's would be great!). You are going to have to really dig to find this answer. You should not even think to install a third party firmware unless you really know how to find the answers to these questions yourself. It is very easy to get a dead router if you load firmware for a router with exactly the same name but a slightly different hardware revision. It is not hard to load third party firmware but you must be very careful and be sure you know what you are doing. In general belkin had extremely poor support for third party firmware.

I do know that most routers that start with F9 are not supported. Even on routers that do have supported chipset you have to be very careful you do not load these to the DSL versions of the router. There is a extremely limited number of dsl routers supported because of open source issue with distribution of DSL drivers. Not real easily.

Obviously you could run something the the resource manager on each device and then combine them or set the firewall on each machine to log and then combine that but I am sure that is not what you are really wanting. Even if you load dd-wrt it does not produce these reports directly. The feature in dd-wrt is called netflow or something similar. It send records to a server for each data flow that you can then run reports on. It is very tough since a router has no place to store long term data for just a router to do this. You might be able to see how much is being used at the instant you look but not much more.

Pretty much this type of report is generated by a firewall which tends to have disk drives. Of course you can use a free one like pfsense on a old PC but it is still a matter of placing this between the end machines and the internet. The hard one when you have DSL is the wireless since it will directly go to the internet and you can't stick anything in between. If you were to really want to do this I would go the pfsense method since you are going to need a server anyhow.

I would get a new router to run your home network.mostly to get the wireless users. You would plug dsl router--pfsense box--new router. Of course I would make sure the new router can run dd-wrt if you ever wanted some advanced feature.

Unfortunately it seems your average person could care less about how much and what is using their connection so the router manufactures do not include this in your average consumer router.

After finding, I was curious to see which vendors might have similar algorithms, so I grabbed some Belkin firmware and started dissecting it. This particular firmware uses the SuperTask! RTOS, and in fact uses the same firmware obfuscation as on the Linksys WRT120N: DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- 0 0x0 Obfuscated Arcadyan firmware, signature bytes: 0x12010920, see 666624 0xA2C00 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 454656 bytes Being a known obfuscation method, was able to de-obfuscate and extract the compressed firmware image. The next step was to figure out the code’s load address in order to get a proper disassembly in IDA; if the code is disassembled with the wrong load address, absolute memory references won’t be properly resolved. Absolute addresses in the code can hint at the load address, such as this loop which zeros out the BSS data section. BSS zero loop BSS zeroing loops are usually easy to spot, as they will zero out relatively large regions of memory, and are typically encountered very early on in the code. Robert Buettner Epublibre. Here, the code is filling everything from 0x802655F0 to 0x80695574 with zeros, so this must be a valid address range in memory.

Further, BSS is commonly located just after all the other code and data sections; in this case, the firmware image we’ve loaded into IDA is 0x2635EB bytes in size, so we would expect the BSS section to begin somewhere after this in memory. A reasonable disassembly listing With a reasonable disassembly, searching for a WPS pin generation algorithm could begin in ernest. When looking for functions related to generating WPS pins, it’s reasonable to assume that they’ll have to, at some point, calculate the WPS pin checksum. It would be useful to begin the search by first identifying the function(s) responsible for calculating the WPS pin checksum. However, without a symbol table, finding a function conveniently named “wps_checksum” is not likely; luckily, MIPS C compilers tend to generate a predictable set of immediate values when generating the WPS checksum assembly code, a pattern I noticed when reversing D-Link’s WPS pin algorithm. Using an to search for these immediate values greatly simplifies the process of identifying the WPS checksum function. GenerateDefaultPin(char *buf, int unused, char *mac, char *serial); MAC addresses are easily gathered by a wireless attacker; serial numbers can be a bit more difficult.

Although serial numbers aren’t particularly random, GenerateDefaultPin uses the least significant 4 digits of the serial number, which are unpredictable enough to prevent an external attacker from reliably calculating the WPS pin. Or, at least that would be the case if the Belkin’s 802.11 probe response packets didn’t include the device’s serial number in its WPS information element.