E4200 Firmware 1.03 Evaluation
After using 1.03 firmware for the past few days, it would appear that there is a new Broadcom driver in it for the wireless NICs as the 5gHz performance seems to be a little more fussy when it comes to connecting to it with a weaker signal.
My Macbook appears to struggle maintaining a stable link from a distance away and the connection times out too easily compared to 1.02.
Has anyone else experienced this too?
Cisco e4200 Firmware 1.03 firmware released
Firmware 1.03 for the Cisco e4200 has been released. I have noticed that 1.02 doesn’t play nice with 2011 Macbook Air with Lion.
Download from here: http://homesupport.cisco.com/en-apac/support/routers/E4200
I’ll report back once I have done some testing. In the mean time here is the change log:
Cisco Consumer Products
Product: E4200
Classification: Firmware Release History
—————————————————————————
IMPORTANT:
- The safest way to perform the firmware upgrade is to use a wired computer.
- DO NOT power cycle the Router during the firmware upgrade process.===========================================================================
Last Release Date: Sept 28, 2011
Last Firmware version: 1.0.03 (build 14)- Added supports of Native IPv6 over PPPoE Internet connection when only keep
alive option is selected.
- Added supports of Native IPv6 on guest network if there are more than two
available IPv6 subnets
- Added supports of Native IPv6 on Parental Control
- Added supports of 3TB Hard drive with NTFS and HFS+ format
- Improved firmware upgrade stability
- Improved IPv6 WAN performance
- Fixed media server unstable issue
- Fixed Cisco LED flashing issue
- Fixed some minor bugs
- DLNA certified
- IPv6 Gold logo certified
- UPnP certified===========================================================================
Release Date: June 14, 2011
Firmware version: 1.0.02 (build 13)- Added support of USB printer connected to the router’s USB port, so that
a user may send a print job to the printer via the local area network.
** This feature requires Cisco connect software v1.4 or later **
- Added support of Native IPv6 and 6rd tunnel Internet connections
- Added supports of bridge mode
- Prevented devices on the guest network to access any private IP
address (RFC 1918)
- Updated wireless driver to improve interoperability
- Fixed some storage relative issues
- Fixed some browser-based configuration utility bugs
- Fixed some minor bugs===========================================================================
Release Date: March 7, 2011
Firmware version: 1.0.01 (build 10)- Fixed 2.4GHz wireless unstable issue
- Disabled IPv6-to-IPv4 Tunneling feature to improve Interoperability===========================================================================
Release Date: Nov 14, 2010
Firmware version: 1.0.00 (build 13)- Initial release
Back Again
Once I took the site down, I had many requests from users to join the site, so I have put it back up. I’ll leave it in the background for now and post when ever I feel like.
Over and Out
Well after more than a year of blogging about Dlink and their products, I am no longer motivated to continue blogging about either.
I no longer buy DLink as they insist on using the ubicom platform for their devices and I have yet to see a stable build for their firmware.
Even their new products are based off the same platform and so will have the same issues as their old. I suspect their late CEO was pushed out for the decision/agreement to lock in ubicom which cost them dearly based on their financial results published earlier.
I’ll leave the site going for a little while so as to allow people to grab what ever firmware they need.
The only one bit of advise I can give you all as home network consumers, only buy devices based off the Broadcom platform. This means netgear, linksys/Cisco, Buffalo and believe it or not, apple. Broadcom platforms appear to be the most stable and offer alternative firmware builds.
Good Bye and all the best.
Monitoring Bandwidth and Other Router Distro’s
I had a comment from Bogman posted to me asking a whole lot of really good questions which I responded to but thought it would make for a good blog, so here it is.
I have tried the experimental tomatousb builds since Build 54 on an E3000 and miniDLNA is broken for streaming to the PS3. The rumor is that Teddy had a death in the family and fixes are probably not going to happen soon.
As far as the E4200 is concerned, is there a way to keep track of bandwidth usage short of flashing the considerably slower dd-wrt or tomatousb firmwares?
Yeah I had read about Teady Bear loosing his wife but no one has confirmed it yet. I really hope that it is just a bad rumor and nothing more. Poor guy, what a terrible thing to go through.
There is another off-shoot of tomato called Tomato RAF by Victek (tomato raf), it appears to be quite stable and well maintianed but uses the older broadcom driver and hence won’t support 5gHz band. You may want to confirm this yourself though. Here is the firmware tomato-E4200USB-NVRAM60K-1.28.9006MIPSR2_RAF-VPN-NOCAT.bin Specific version for E4200, USB + Extended Sysinfo + VPN + Captive Portal. Updated June 13th. 2011.
As for a DLNA server, with many of the firmware distro’s, you have the option of installing optware and then installing a dlna server that is regularly maintained rather than the one packaged with the firmware.
Much like all distro’s, they will not be faster than the stock firmware that Cisco has put out due to the following reasons:
- Stock firmware uses fast-nat which is not compatible with some of the features in DD-WRT and many other distro’s.
- Stock firmware has proprietary code that allows the router to perform CTF (Cut Through Forwarding) which basically allows the router to interpret the IP header as it is coming in and once the Destination IP address is determined, begins to forward the bits straight away. This means that the router performs at almost line speed (CPU limiting of course), rather than maintaining a buffer which assembles the packet and is then interpreted for transmission.
The interesting thing is that the stock firmware has a broken twonky media server too, I am wondering if there is a broken common library that is stopping all media servers on 2.6 kernals.
As for your question on tracking bandwidth, yes there is a few approaches to take.
- The router should support SNMP (both stock and distro’s), so you could get a tool that will connect to your router via SNMP to track bandwidth. The unfortunate part is that you will need a machine that is always on to keep counting the traffic usage. If you have a linux based file server, then that is the ideal choice as there are quite a few advanced/professional server and bandwidth monitoring applications available with web interfaces, MRTG is one well established application.
- Using distro’s like DD-WRT, you can setup optware and install applications that will do this, perhaps even MRTG.
Cisco E4200 Firmware Added to Blog
Some users have been having issues with Townky Media server in the latest 1.0.02 firmware and have been wanting to downgrade. So I have added the both 1.0.01 and 1.0.02 to the blog and can be found on your right.
I am waiting for the latest 2.6 Kernel Broadcom drivers to make their way into the opensource disto’s so that I can try TomatoUSB firmware. Having said that, the stock firmware is very fast.
Cisco E4200 Firmware 1.0.02 Released
I guess I will now be posting blogs about the e4200 as well. Cisco has now released firmware v1.0.02 which includes IPv6. It might be interesting to note that the firmware has grown in size from the previous version 1.0.01 by 3 megabytes. I’ll try and make some time to investigate if they have moved to kernel 2.6 or if it is still with 2.4. At any rate, here is the change log:
Last Release Date: June 14, 2011
Last Firmware version: 1.0.02 (build 13)- Added support of USB printer connected to the router’s USB port, so that
a user may send a print job to the printer via the local area network.
** This feature requires Cisco connect software v1.4 or later **
- Added support of Native IPv6 and 6rd tunnel Internet connections
- Added support of bridge mode
- Prevented devices on the guest network to access any private IP
address (RFC 1918)
- Updated wireless driver to improve interoperability
- Fixed some storage relative issues
- Fixed some browser-based configuration utility bugs
- Fixed some minor bugs===========================================================================
Release Date: March 7, 2011
Firmware version: 1.0.01 (build 10)- Fixed 2.4GHz wireless unstable issue
- Disabled IPv6-to-IPv4 Tunneling feature to improve Interoperability===========================================================================
Release Date: Nov 14, 2010
Firmware version: 1.0.00 (build 13)- Initial release
No More New Firmware for DIR855 DIR655 & DGL4500
Really bad news fellow DLink consumers;
I have had an interesting discussion with someone who develops firmware for network equipment. He/She suggests that there will be no more scheduled firmware releases for the DIR855, DIR655 and the DGL4500. DLink will most likely continue to sell these products until superseded by the upcoming new models, they should continue to provide technical support but there are likely no developers working on the current series product firmwares. The developers will all be allocated to the new upcoming models and subsequent firmware releases once the products are released.
You are most likely wrong if you think you are getting any more new firmwares unless something very drastic happens and the developers will need to be re-allocated to these products.
I do not know if DLink use internal developers or if they outsource the development but this is a sad turn of events for DLink customers.
Share Internet Connection Between 2 Houses
There are quite a number of people out there that will share their internet connection with another house. However, most believe that either, both houses must be on the same network/LAN or two networks/LANs and must be isolated (ie, first network cannot access the second).
Lets first layout the the topology so that I can explain the statement above.
- We have House 1 which has the internet subsciption
- House 1 and Router 1 setup to access the ISP and it’s IP address will most likely be 192.168.1.1
- We then have House 2 which is piggy backing off House 1 and sharing the subscription.
- We have PCs in House 1 using the subscription which we will call PCs 1
- PCs in House 2 using House 1 subscription which we will call PCs 2
What the majority of people will do when sharing the internet subscription in House 1 with House 2, is that they will setup a wireless connection between Router 1 and PCs 2 directly. The problem with this is that PCs 2 will have varying degrees of performance depending on their location relative to Router 1 and that PCs 2 maybe prone to dropouts. Further, if you sharing files between PCs 2, then performance will be really really bad and should one of the PCs 2 wireless connection dropout, then it will not be accessible for the rest of PCs 2.
The Standard Solution
The standard solution (that Cisco, DLink, Netgear, etc try to sell you) is the setup a wireless bridge between the two houses. This is basically having 2 wireless access points that can be put into bridged mode, placed in each house. The two access points when placed into bridge mode, will act as if there is a virtual network cable between the two. So what you would do is take Access Point 1, connect it into one of the ports in Router 1 and place in an optimal location relative to House 2. You would then buy a Network Switch plug all PCs 2 into it, position Access Point 2 in an optimal location relative to House 1 and connect it to the Network Switch.
What you have achieved here is the fastest and most stable possible wireless connection between House 1 and House 2 that will not be prone to dropouts. Further more, file transfers between PCs 2 will be at least 10 times faster if not 20 to 30 times.
However, and here it comes, PCs 2 is very heavily dependant on Router 1 and the stability of the bridge between House 1 and House 2. Should Router 1 become offline, it will not only bring down PCs 1 but PCs 2 as well. Better yet, should the bridge become offline, then PCs 1 will still have an active network but PCs 2 will all be offline.
Basically both houses form 1 network.
The Better Solution
Now that I have aquired my shiney new Cisco e4200 (which leaves my DLink DIR-855 in its dust) I figured l’d move the DLink into the second house and isolate the network (I have 2 houses on my land). So I have the Cisco as Router 1 in House 1 and the DLink as Router 2 on House 2. Basically, I replaced the switch in House 2 with Router 2 and plugged Access Point 2 into the WAN port of Router 2.
A very important note before I go on, you must have a different network address between House 1 and House 2. In my case, Router 1 is on network 192.168.1.0 and Router 2 is set to 192.168.2.0. DLink, by default, use 192.168.0.0 which isn’t good practice, I would avoid using this address, google it if you are interested but I am not going to elaborate on it as I would have to explain subnetting the 192.168 class first.
What you have achieved here is that you have created 2 isolated networks, should anything happen to Router 1 or the bridge, Network 2 and PCs’2 will be unaffected except that they will loose their internet connection.
However, what you will find so far, is that PCs’2 can access PCs 1 but not the other way. This is because the Router 2 is configured as a gateway and is performing NAPT (the manufactures misleading refer to it a NAT). NAPT or network address port translation effectively stops incoming traffic from the WAN port to the LAN if the LAN did not first establish the communication (google it for more details).
DLink routers will not allow you to change the router from Gateway to Router mode, they can be tricked into bridge mode but that will not allow you to create an isolated network. So if you do use a DLink as your Router 2, you will have to contend with double NAPT when access the internet or needless NAPT when accessing Network 1 from Network 2 or vice versa.
You will need to fix the IP address of WAN port on Router 2 for reasons explained later. There are two options here, you can set Router 2 internet connection to DHCP/Automatic IP address, at which case, in Router 1, you will need to set up a DHCP reservation for Router 2. Or you can specify Static IP for your internet connection in Router 2 with the following:
- IP Address, 192.168.1.2
- Subnet mask. 255.255.255.0
- DNS Address. 192.168.1.1
To allow PCs 1 to gain access to PCs 2, you will need to setup static routes in Router 1. Most routers should have this option but will look different in each brand of router. Basically what you need to enter in is the following:
- Network Name, in this example, Network 2.
- Destination Network address, in this example, 192.168.2.0
- Subnet Mask, 255.255.255.0
- Gateway, this will be the IP address on the WAN port of Router 2 based on what you chose in the paragraph above.
Where still not quite there.
Even Better solution
If you can, do not use DLink on the second network but perhaps a router that will support DD-WRT/Open-WRT. Then you will be able to add the following in the commands menu:
iptables -I FORWARD -s 192.168.1.0/24 -j ACCEPT iptables -I FORWARD -s 192.168.0.0/16 -j ACCEPT
This helps with devices trying to discover services on the networks.
Closing Thoughts
If you want to share your Internet Subscription, then you have to learn a little bit about networking. If you want a stable network between the two, then you have to be prepared to spend some money. You don’t need the latest tech, but you will need more network devices and will have to manage them. The good thing about this though, once it is setup, it should not need to be fiddled with. If you can get network devices that use DD-WRT, then the networking world is at your feet but it is a little more effort to become more familiar with it. Finally, based on my experience, DLink products may not be ideal for this.
Cisco E4200 Comparison to DLink 855/655/4500/825A
Just purchased the Cisco E4200 today as there was a 30% off all Network Equipment at a store in the local mall.
The 2.4GHz performance wasn’t that much more better than my DIR-855 but the 5.2GHz band was absolutely amazing. I cannot believe how much more better it is for performance and range.
The 855 much like the 655/825A/4500 have a very week 5GHz transmitter that really defeats the value of having a simultaneous dual band wireless router.
On the DLink DIR-855, i use to get between 2 and 16 mbs and lots of drop out in my lounge room, however, the Cisco E4200 delivers 100 mbs without drop outs in the lounge. That is a huge improvement and well worth the upgrade in my opinion as I can finally move all my N devices over to the other band and leave the 2.4 band for g devices. It was a pain in the backside when my squeezebox or iPhone where using the network at the same time as my notebook.
What is more impressive is that when I am sitting in the next room from the office where the router sits, I get between 405 and 450 mbs with my Intel 6300 wireless card in the notebook. How impressive is that
The cisco firmware doesn’t have as many networking options in the admin pages like the DLink 855/655/825a/4500 but it does have multimedia features unlike the DLink products. Personally, the CPU is too slow for descent file serving performance and so I figure why do they bother? I have an Intel atom QNAP for all of that.
If you are interested in Dd-WRT for this baby, then you need to be patient as it is still WIP and there appears to be obe final bug that is stopping the 5,2 GHz band from using the WAN. Stay tuned as this should be fixed soon.
So I am now going to move the 855 onto my secondary network and let it sit there.
Recent Comments