Lemme put a plug in for coova ( <a href="http://coova.org">http://coova.org</a>) here. Based on openwrt, optimized for hotspot use. <br><br>Be sure to explicitly tell your tftp client that you're transferring a binary file when you flash your router. Otherwise you'll have much fun and hilarity (thanks Jim K for fixing this).<br>
<br>-- CHS<br><br><br><div class="gmail_quote">On Fri, Jul 24, 2009 at 8:20 PM, Matt Rideout <span dir="ltr"><<a href="mailto:mrideout@windserve.com">mrideout@windserve.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That's a good assessment. Either would be a large improvement any stock<br>
firmware. To me, it's like asking if you should replace a Windows<br>
installation with CentOS (DD-WRT) or Debian (OpenWRT).<br>
<br>
A deciding factor many cases will be which *wrt supports your AP. I<br>
haven't seen any stability problems, or noticed a performance difference<br>
between the two.<br>
<br>
Tim Watts wrote, On 07/24/2009 07:45 PM:<br>
<div><div></div><div class="h5">> Cool. So now, shifting the discussion a little:<br>
><br>
> How do folks weigh in on linux-based router firmware distros? From my *very*<br>
> preliminary investigation, openwrt looks to have more flexible packaging but<br>
> perhaps at the cost of ease-of-use? DD-wrt might be easier to get my feet wet<br>
> with but locks out some features (which I may never need) until I pay. But<br>
> what about:<br>
><br>
> - Stability?<br>
> - Memory requirements?<br>
> - Quality of wireless support?<br>
> - Active community?<br>
><br>
> Any other good linux-based options out there?<br>
><br>
><br>
><br>
> On Friday 24 July 2009 5:23:14 pm Jason Fritcher wrote:<br>
><br>
>> I'm not sure about the GUI tools, but I had to ssh into the router to<br>
>> set everything up. If you go the DD-WRT route, try this page, it is<br>
>> what I used for my initial setup.<br>
>><br>
>> <a href="https://www.dd-wrt.com/wiki/index.php/Access_To_Modem_Configuration" target="_blank">https://www.dd-wrt.com/wiki/index.php/Access_To_Modem_Configuration</a><br>
>><br>
>> On Jul 24, 2009, at 3:18 PM, Tim Watts wrote:<br>
>><br>
>>> OK, so on JK's reasonable theory that my linksys is stuck on serving<br>
>>> 192.168.1.0 to lan clients, I reconfigured the modem as 192.168.3.1.<br>
>>> Still no<br>
>>> go. Tried pinging it from the router and workstation -- not<br>
>>> reachable. Tried<br>
>>> adding a static route to that net on the router -- not reachable. It<br>
>>> seems<br>
>>> that any route I try to add on the router that goes thru the WAN<br>
>>> interface<br>
>>> gets silently rejected. So I think what Jason mentions is what I'll<br>
>>> have to<br>
>>> do. I'm going to explore dd-wrt vs openwrt.<br>
>>><br>
>>> Thanks folks!<br>
>>><br>
>>> On Friday 24 July 2009 1:28:32 pm Jason Fritcher wrote:<br>
>>><br>
>>>> I set this up on my wrt54gs a while ago. With the stock firmware, I<br>
>>>> could not find a way to do this. I changed the router to DD-WRT,<br>
>>>> and I<br>
>>>> was able to put a 192.168.1.x address on the WAN port, add a route on<br>
>>>> the router so that 192.168.1.x bypassed the pppoe tunnel and was<br>
>>>> routed directly out the WAN port, and add a static router to the<br>
>>>> modem<br>
>>>> so that it could communicate back. My internal LAN is on the<br>
>>>> 192.168.0.x subnet.<br>
>>>><br>
>>>> I don't have that modem any more, so I can't offer up my config as an<br>
>>>> example.<br>
>>>><br>
>>>> On Jul 24, 2009, at 1:03 PM, Tim Watts wrote:<br>
>>>><br>
>>>>> On Friday 24 July 2009 12:31:47 pm JK wrote:<br>
>>>>><br>
>>>>>> However, I find that even when in bridge mode, my ATT DSL modem<br>
>>>>>> (just<br>
>>>>>> a modem, not a router) still serves up its admin interface on<br>
>>>>>> 192.168.1.254<br>
>>>>>> (or maybe 192.168.1.1, can't remember). And since the default<br>
>>>>>> route from<br>
>>>>>> my router (a Buffalo Airstation running Tomato, but that's not<br>
>>>>>> relevant)<br>
>>>>>> goes through the modem, and since my LAN is on a distinct subnet<br>
>>>>>> from<br>
>>>>>> the modem (<a href="http://192.168.80.0/24" target="_blank">192.168.80.0/24</a>), I have no problem hitting the modem's<br>
>>>>>> admin interface from machines on my LAN.<br>
>>>>>><br>
>>>>> OK, so sounds like you're saying I might be able to reach it if I<br>
>>>>> put the<br>
>>>>> modem and lan on distinct subnets? So if my lan is 192.168.2.0 (it<br>
>>>>> is) and I<br>
>>>>> put the modem on 192.168.1.0, then would I need to add a static<br>
>>>>> route to it on<br>
>>>>> the router? And/Or on all my lan nodes?<br>
>>>>><br>
>>>>><br>
>>>>>> Tim's problem may lie in the fact that practically everything in<br>
>>>>>> the<br>
>>>>>> consumer-router world comes pre-configured to serve 192.168.1.0<br>
>>>>>> addresses to LAN clients. Changing the LAN subnet in the router<br>
>>>>>> config might be all that's necessary.<br>
>>>>>><br>
>>>>>> -- JK<br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Ale mailing list<br>
>>>>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>>>>>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>><br>
>>>>> --<br>
>>>>> Illusion is the first of all pleasures.<br>
>>>>> -- Oscar Wilde<br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Ale mailing list<br>
>>>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>>>>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>><br>
>>>> _______________________________________________<br>
>>>> Ale mailing list<br>
>>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>>>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>>><br>
>>> --<br>
>>> Sometime they'll give a war and nobody will come.<br>
>>> -- Carl Sandburg<br>
>>><br>
>>> _______________________________________________<br>
>>> Ale mailing list<br>
>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>>><br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
>> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>><br>
><br>
><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div><br>