>>>>> "david" == david  <[email protected]> writes:

david> On Thu, 4 Oct 2012, John Stoffel wrote:
Phil> If anyone's looking, I'm very happy with a Netgear WNDR3800
Phil> running openWRT; the vendor uses open Linux firmwares by default
Phil> and make it easy to replace the firmware entirely, the unit
Phil> chosen has plenty of RAM, is simultaneous dual-band with
Phil> multiple GigE ports, and generally just works.  With openWRT,
Phil> I've got an IPv6 SixXS heart-beat tunnel running and Unbound as
Phil> the DNS resolver, so I have a DNSSEC validating resolver between
Phil> my home network and the world.
>> 
>> I've got a slightly older WNDR3700v2 which I used to have DD-WRT
>> running on, which I liked because it gave me the dual band, plus it
>> replacement my ancient Wrap board running m0n0wall as the Firewall.
>> 
>> But I *hated* how DNS for internal hosts was handled.  I tried
>> ungrading to a newer version of DD-WRT which was a disaster.  It
>> bricked the damn thing and since I was in a rush, I put the m0n0wall
>> back in place, and hey, my performance was better!
>> 
>> Just trying to figure out which version of DD-WRT, and where to find
>> it, and how to upgrade it was a damn pain too.  And looking through
>> the TomatoUSB stuff doesn't make me any happier.
>> 
>> So I've been looking at OpenWRT, but it too is so badly organized that
>> it's hard to find out which version is supported (or even just
>> available!) for which hardware and what the gotchas are.  We all do
>> stuff like this for a living, but there are times when I do want to
>> have something simpler to setup and which won't impact my family when
>> I'm screwing around.  Work writ small I guess.  I can burn my own
>> house down and fix it, but when I burn down the house while the wife
>> is working on her stuff, it's a five alarm blaze!
>> 
>> Sorry, just had to get this all off my chest.

david> The good news is that OpenWRT is nearing making a formal
david> release after far, far too much time where the old release just
david> isn't able to run on most devices. They are planning to make
david> much more frequent releases after this to avoid this problem in
david> the future.

This will be nice to see.

david> I use the WNDR3700v2 and WNDR3800 routers to run the wireless
david> at SCaLE with OpenWRT and they work very well for me. I tested
david> with the 'trunk' nightly build and ended up compiling and
david> building my own image.

Care to share your image?  I mostly just want:

   - firewall
   - wireless
   - internal DHCP/DNS where I can add in a host name and have it be
     found using 'nslookup hostname' or 'nslookup hostname.stoffel.home'
     (my internal DNS domain name).  It was just such a pain getting
     DD-WRT to do this...
   - IPv6 for playing/testing
   - DMZ if I so choose

I do NOT need:

   - USB support
   - file sharing
   - printer daemon
   - other home server stuff, I've got a dedicated server for that. 

david> I ran DD-WRT on the access points a couple of years ago and
david> wasn't really happy with it. If you want to do things the way
david> DD-WRT decided makes sense, it's easy to do things. If you want
david> to do anything a little different it's rather hard.

Yeah, that's mostly my experience.  But the performance just seemed
to not be there too, but I honestly can't say I've got any hard
numbers to back things up.  Netflix traffic at night throws off all
kinds of measurements I suspect.  

david> OpwnWRT by comparison is like a linux distro, they set things
david> up by default, but if you want to do something different you
david> just edit the config files, or install a different package.

Nice, I really need to go take a look at them and figure out if I can
have it do what I want without too much hassle.  My time is in short
supply and better spent on other stuff right now.  

John

_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to