09.08.2010 21:28, KP Kirchdoerfer пишет: > Am Montag, 9. August 2010, 19:44:56 schrieb Andrew: > >> 09.08.2010 20:31, KP Kirchdoerfer пишет: >> >>> Am Montag, 9. August 2010, 19:17:24 schrieb Andrew: >>> >>>> 09.08.2010 19:40, KP Kirchdoerfer пишет: >>>> >>>>> SOHO applications and routers don't bother me. >>>>> A possible solution is to enhance ipv6 where possible (we do it today >>>>> with ipv6 enabled packages like dnsmasq) and where itwon't raise pb's >>>>> if no ipv6 is available: For example a merged shorewall package with >>>>> shorewall and shorewall6 is no pb without having ipv6 , cause you can >>>>> disable shorewall6 in shorewall6.config (which is the default setting >>>>> anyway). Similar moddb and moddb6 can be merged, its just about having >>>>> the modules in one lrp, one can decide about modules to load in >>>>> modules.conf - a usual task. >>>>> I guess ip6tables will not cause harm on ipv4-only system, at least it >>>>> was installed on my desktop without asking me if I do have ipv6 :) >>>>> >>>>> Looking through the package directory in buildenv, these are the three >>>>> packages I have in mind. >>>>> >>>>> kp >>>>> >>>> For therse packages, that will not cause any troubles when IPv6 is >>>> disabled, it's possible to include IPv6 functionality into base >>>> packages. But IMHO it'll be good to make global IPv6 flag somewhere in >>>> config files - this will make future IPv4/IPv6 package merging easier >>>> for end users. >>>> >>> Sorry; I don't the idea, where a global flag can be useful. Maybe you can >>> explain it more? >>> >>> I'm afraid that such a flag raises the users expectation that WE take >>> care of enabling ipv6 whereever possible like module loading, enabling >>> shorewall6, or other strange ideas.... >>> >>> kp >>> >> For ex., if merged ospfd v4 and v6, bgpd v4 and v6, and if will be >> iptables init script for loading settings - it'll be good to make one >> script for all of there tasks. >> About module loading& etc - it isn't too hard to make 2 different >> modprobe.conf files, one - generic and one for IPv6 modules. >> Another solution - to really make daemon config for each package that >> supports IPv6, with flag for enable/disable IPv6 daemon.. >> > Understand. > What I've been asking for was to merge three packages, so a user just have to > enable ipv6 the usual way (loading module, enabling fw) without the need to > load additional packages (or to be aware that moddb_ipv6.lrp has to be renamed > to moddb.lrp). > > I even don't believe that seperate modprobe.conf (modules.conf) is necessary - > we also don't provide seperate configurations for NICs. It might be possible > to load demanded modules automatically, but thats a different story. > > daemon config files which are aware of enabling ipv6 (sourcing > /etc/default/packagename) sounds good to me. But currently I'm talking just > about the three packages mentioned above. These are the low hanging fruits > though they'll be a welcome improvement for the users - and also for those who > build the packages :) > > kp > kp > Yes, it's possible to imerge at this time these 3 packages - it won't cause now any troubles.
P.S. I still can't run hostapd with new kernel - it reports that it fail to set channel for wireless card. I've removed all potential trouble sources: updated hostapd to 0.7.2 - one user reports that ath5k with this hostapd works fine on Gentoo (I still not tested my WiFi card on Gentoo box, I'll put it back into Gentoo box tomorrow and look on it); I've removed old kernel headers that were provided by unknown reason with libnl - but no luck. I'll try to update libnl from GIT - possible it'll solve troubles. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
