This week (unless supplies run out, which happens) NCIX has this wireless router for $99.49 with free shipping. This is one that Scott has and recommends for OpenWRT. He says that you should go for Version 2.0 and that the box will say if it is a Version 2.0 router. For that reason it may be better to buy it in one of their stores. It has been cheaper (briefly $70 and Future Shop and Best Buy) but not often recently. <http://www.ncix.com/detail/tp-link-archer-c7-ac1750-dual-1c-91525-1251.htm> <http://wiki.openwrt.org/toh/tp-link/tl-wdr7500>
On 12 February 2015 at 00:11, D. Hugh Redelmeier <hugh@mimosa.com> wrote:
This week (unless supplies run out, which happens) NCIX has this wireless router for $99.49 with free shipping.
This is one that Scott has and recommends for OpenWRT. He says that you should go for Version 2.0 and that the box will say if it is a Version 2.0 router. For that reason it may be better to buy it in one of their stores.
It has been cheaper (briefly $70 and Future Shop and Best Buy) but not often recently.
<http://www.ncix.com/detail/tp-link-archer-c7-ac1750-dual-1c-91525-1251.htm>
I purchased one of these fairly recently. Installing OpenWRT was as easy as I've ever seen it be, and the amount of memory available seems absolutely immense compared to the WRT-54Gs I'd been working with previously. I would love to tell you it's been great, but I haven't actually used it enough to say that honestly. So all I can say is that it's looking good in the little use I've had from it. If you do buy one and want to use the USB ports (which are 2.0 ... I wish they were USB3), my stumbling adventures getting the ports to work may be educational: http://gilesorr.com/blog/archerc7-openwrt.html -- Giles http://www.gilesorr.com/ gilesorr@gmail.com
I picked up one of these at NCIX on Saturday... - Installed it Saturday evening, getting it working as a backup wireless router; - Upgraded the firmware from TP-Link, which required redoing that configuration effort :-( - Pulled the OpenWRT binaries (per Giles' link), and installed, which was, modulo a wee bit of "wait afterwards hoping it worked", about as easy as he suggested - Introduced configuration to have it take over my WAN link, which worked, but then didn't seem friendly to needs for incoming connections (torrents^H^H^H^H^H^H^H^H and ssh), so plugged the old router back into place I poked at sundry sources of docs concerning the differences between firewall rules and firewall routes, which didn't really tell me anything I didn't already know or hadn't already done. Yesterday, I wrote up a script to pull config tarballs off the router and throw it, version-controlled, into a favorite Git repo, so I have backups. In keeping with the strategy I described a bit at the last meeting; anyone interested can review the GTALUG "backups" repository at GitHub for the broad approach... See http://github.com/gtalug/backups That repo doesn't include this, as my router's config isn't GTALUG business, but the approach in the scripts in the "scripts" directory should be suggestive. I wee while ago, I retried the WAN link, basically moving the plug from one router to the other, and, a mod to gateway addresses in /etc/network/interfaces later, all now seems copacetic, with no particularly interesting changes made to explain why incoming traffic wasn't happening Saturday but is working now. At any rate, my old Cisco/Linksys WRT310Nv2 will be retiring as consequence. The one interesting area that I probably need to poke at more is that of IPv6 support. The old router didn't have any (evident) support. OpenWRT seems to. I haven't fiddled with the configuration, as I could readily see that breaking things. I had been suppressing IPv6 activity (e.g. - my internal Bind9 /usr/sbin/named instances being run with the "-4" option that suppresses IPv6 usage); perhaps that ought to change now? I'm not quite sure.
On 02/16/2015 02:24 PM, Christopher Browne wrote:
The one interesting area that I probably need to poke at more is that of IPv6 support. The old router didn't have any (evident) support. OpenWRT seems to. I haven't fiddled with the configuration, as I could readily see that breaking things.
Does your ISP provide IPv6? If not, you'll need to use some sort of tunnelling to get it.
On 16 February 2015 at 14:29, James Knott <james.knott@rogers.com> wrote:
On 02/16/2015 02:24 PM, Christopher Browne wrote:
The one interesting area that I probably need to poke at more is that of IPv6 support. The old router didn't have any (evident) support. OpenWRT seems to. I haven't fiddled with the configuration, as I could readily see that breaking things.
Does your ISP provide IPv6? If not, you'll need to use some sort of tunnelling to get it.
Nope, but it is a step up to have a router that can recognize the traffic. And presumably I could run a tunnel atop OpenWRT. "Doing more with IPv6" is probably a talk of interest to more than just me, if we have folk that have fought thru that. -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?"
On 02/16/2015 08:50 PM, Christopher Browne wrote:
"Doing more with IPv6" is probably a talk of interest to more than just me, if we have folk that have fought thru that.
I have been running IPv6 on my network for almost 5 years. I get it through a tunnel from gogo6. I believe OpenWRT can be configured to use it. If you set it up for a subnet, you'll get a /56 prefix, which will provide 2^72 addresses or about a trillion times the entire IPv4 address space. http://www.gogo6.com/
participants (4)
-
Christopher Browne -
D. Hugh Redelmeier -
Giles Orr -
James Knott