[Ewrt-devel] development status update

Fri May 7 12:51:53 PDT 2004

IP tables also needs to be set up such that http(s) requests sent to the 
linksys on the internal LAN will respond to the "remote management 
port", and not just port 80/443.

I have hit a bug where when changing information on the main admin page 
you will get an error saying your values are incorrect, but everything 
you changed was written out to NVRAM.  Do not have enough detail on it yet.

NoCat should be set to:
    allow you to set the allowed dst IPs via the web/nvram
    allow you to specify an image to pull and be used for the splash page

-b

Irving Popovetsky wrote:

> Okay, so we have quite a bit of exposure for this project now.  Here's
> whats been going on in the last week:
> 
> *  Announced Ewrt at Personaltelco.  Many other news sites, discussion
> forums and blogs quickly picked up the news.
> *  Put up the slides from my Personaltelco presentation
> *  got anonymous CVS working
> *  Got GNU mailman working.  moved ewrt-devel and ewrt-cvs over to
> Mailman
> *  Put up the source tarball for Ewrt 0.2 beta1
> 
> We now have approximately 1000 visitors per day to the website,
> according to awstats.  There have been about 150 downloads of the binary
> and about 12 full CVS checkouts.  not bad!
> 
> There are a number of bugs we are currently investigating:
> *  ssh is just a symlink to scp.  Dropbear's scp doesn't seem to support
> ssh client functionality
> *  Nocat seems to blow over the iptables rules for port forwarding. 
> Don't know what else it breaks.  This needs further investigation
> *  When nocat is first enabled in the web interface, the web interface
> can go unresponsive.  rebooting the box fixes this.
> *  Nocat makes you auth to get to the WRT54G web interface, it should
> probably allow its own IP by default
> *  Nocat does not clean up all of its TIME_WAIT sockets when it exits. 
> You cannot restart the daemon until all of those sockets time out
> *  Brandy believes that there is a way to wedge a Nocat thread with a
> malformed request.  it never unwedges.  so if you wedge all 10 threads
> then Nocat won't respond until its restarted
> *  Remote syslogging doesn't always start reliably, especially if your
> WAN interface gets its address from DHCP
> *  As we just discovered, rc/firewall.c doesn't clamp the TCP MSS to the
> PMTU of the WAN interface, even though the comment says it does.  This
> was breaking a user who had PPPoE over ADSL
> *  The name of this project kinda sucks.  we need a new name. 
> suggestions?
> *  the webpage for this project sucks too.  anyone care to contribute a
> better design?
> 
> My goal is to have many of these fixed for Ewrt 0.2-rc1.   Anyone else
> find anything wrong?
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ewrt-devel mailing list
> Ewrt-devel at portless.net
> http://strongbad.prostructure.com/mailman/listinfo/ewrt-devel

-- 
-A. Brandon Psmythe
ProStructure Consulting             http://www.prostructure.com
Network and Security Consulting           phone: (503) 288-1566
                "Crafting Connectivity that Matters"