{"id":101,"date":"2006-09-05T13:59:02","date_gmt":"2006-09-05T13:59:02","guid":{"rendered":"http:\/\/blog.bananasplit.info\/?p=101"},"modified":"2006-09-05T14:01:10","modified_gmt":"2006-09-05T14:01:10","slug":"101","status":"publish","type":"post","link":"https:\/\/blog.stmellion.org\/?p=101","title":{"rendered":"More WRT54G woes"},"content":{"rendered":"

In a previous blog entry<\/a> I described Linksys<\/a> as my preferred source of SOHO router, then went on to rant about them changing specifications whilst retaining the same model number. Today I’ve uncovered yet another example of the mess they made of the WRT54G model.<\/p>\n

I’ve been suffering issues with SSH disconnects on just one of my routers, a WRT54G(v5). This is the version that was a disaster from the moment it hit the shops. Linksys<\/a> in their infinite wisdom completely changed the underlying OS on the device but kept the same (WRT54G) reference. This resulted in me having a few of them lying around in their boxes because I couldn’t flash them with the firmware I wanted to use. But I digress.<\/p>\n

After some Googling I find I’m not alone with my SSH disconnect problem. This blog<\/a> describes the problem exactly, as does this forum thread<\/a>. It turns out Linksys<\/a> claimed to fix the problem with their most recent firmware (v1.00.9) but in reality they increased the timeout from 10 to 30 minutes. Thanks Linksys<\/a>, that was truly great thinking.<\/p>\n

Once again I find myself in a position of owning a number of WRT54G model routers, all with different functionality, firmware and issues but all sold as the same product. How on earth do they get away with this shady practice? Bring out a model, let it build a solid reputation, then change (downgrade) the specification.<\/p>\n","protected":false},"excerpt":{"rendered":"

In a previous blog entry I described Linksys as my preferred source of SOHO router, then went on to rant about them changing specifications whilst retaining the same model number. Today I’ve uncovered yet another example of the mess they made of the WRT54G model. I’ve been suffering issues with SSH disconnects on just one… Continue reading More WRT54G woes<\/span><\/a><\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15,6],"tags":[],"class_list":["post-101","post","type-post","status-publish","format-standard","hentry","category-networking","category-rants","entry"],"_links":{"self":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/101","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/users\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=101"}],"version-history":[{"count":0,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=\/wp\/v2\/posts\/101\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=101"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=101"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.stmellion.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}