I don't know how frequently LARTC is updated, but it looks like a work in progress. Not to say it's bad, it is very good, just sometimes incomplete. I briefly looked into multicast routing to setup broadcast gre tunnels but quickly realized I was about to swim with sharks (recompile kernel or somewhere in that realm, etc). Not that I'd have a problem with that, but I've made enough changes to my leaf kernel already. I still drool over the La Brea tarpit netfilter patch, but I have to hold back. Eventually I will get that going, along with a nosey shorewall.log-snopping awk daemon that will do wonderful things to those who even dare look at my router :)
Anyway, technically it's quite possible to create a leaf upgrade tool, but practically speaking, I also think it's impossible. It would be too time consuming. Beta testing could go on forever. At the very least, something to replace the config files and a few other key considerations might be reasonable. Leaf is pretty much like the full distros where everything is afforded to you. This is why I decided to use it. Astaro, Mandrake MNF, Smoothwall et al are simply "what me the vendor thinks a firewall should be...and here is the config tool, take it or leave it". In order to upgrade a system, boundaries must be in place. But there are no boundaries here to begin with. Regardless, I'd say that at the very, very least... a CF/HDD image would make things a lot easier for a lot of people. -cpu James Neave wrote: >Hi, > >As a software developer, I know all about "finishing" software. :) > >I remember that. That stemmed from being stuck in a windows only >environment and the thought of upgrading our Bering (1.0 I believe, >maybe 1.1) router to include latest kernel and security related patches >gives me the screaming heebee jeebees. > >We're running in not broken, so don't even think about touching it mode. > >I guess it's probably not possible, but I was pondering at that time on >a way to automagically create the latest packages with old configuration >intact. Which you can't. > >Technically I'm still (STILL!) working on multi house wireless networks >with multiple shared internet connections. Although we very rarely get >any time to work on it anymore, as soon as the kitchen is refurbished we >have sworn to work on it every Wednesday evening. 8D > >Another feature we're looking at adding is multicast routing across VPN >tunnels. This will allow mDNS and other zero conf stuff to work across >our big net and switch on iTunes sharing between our subnets. I think. >:S >That all seems still very bleeding edge in Linux. Is there an >mrouted.lrp about? > >We've managed to finally connect two houses, get ADSL working in linux >(we cheated and bought Ethernet ADSL modems, no firewall, no NAT, just >single IP DHCP) as well as 802.11b (cheated again, used an AP as a >wireless Ethernet bridge) > >It's all over one ADSL line though. LARTC says how we set the rest up >although everything kinda points to none of this working very well with >such a low number of users (route caching :( ). Plus we have to patch >and recompile the kernel to get failover working for if a connection >goes down >@ > >Erik Spakman offered to do the compiling for us though, which I will >take him up on, one day... when I'm old and grey at this rate. :P > >Regards, > >Jim. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
