Am Dienstag, 16. September 2003 18:06 schrieb FACORAT Fabrice: > This may seems early to talk about that, but some ideas come to me > this morning in the bus and I'd rather write them down when there are > clear. Many people complain about the fact that drakconnect is mostly > buggy and not convenient ( config lose, difficulties to set some > settings, config mix up, bad profiles management, ... ). I think this > is due to the fact how drakconnect represent himself the network and > internet connection. > > So here are my thoughts : > We should separate system settings and device specific settings. > > System settings are : hostname > > For device specific settings, we should act like this : > We should follow the Object Oriented approach. The base is the > NetDevice and this interface have some attributes. > > NetDevicee : IP netmask gw type > > From interface you can derived ( this exist in English ? ... ) from > the type if you have an pci/usb/pcmcia/serial/parallel with some > attributes > [ ... a lot .. ;)]
> ************************* USB Modem case **************************** > > show info, select protocol + settings ( username, password, ... ). > For driver if you need the firmware in driver say "need to select > firmware" and give the ability for the user to select firmware unless > drakconnect manage to take the firmware himself ( windows partition > scan + firmware file copy ) so them show the path to the firmware > file ( for example /usr/share/sagem800/firmware/myfirmware.bin ) I add possibility for different ISP here. > - The user need to explicitly delete a NetDevice to free the > associated interface. So I can unplug my USB modem, and 2 months > later plug it and see it take the same settings as I don't delete it. Yep > I think I forgot many things, some things could be incorrect or > impossible ( kernel/software limitation but this could be changed ), > but this is how I see the perfect config tool. In this situation, > drakconnect will completely abstract the network layer. If the user > want to do things himself, it's just a matter of disabling > drakconnect ( a special service maybe will be necessary in order to > test/modify/... the settings of NetDevice ) At least it sounds interesting. I think too drakconnect needs a major change in concept. I add some things i think that would usefull: For all that are not allways on the net: - dialup for user. This may be accomplished by a special dial-tool or having existing dial tools for each connection and preconfigure that tools, so that they are usable (Q: which users should be able to dial out ?=> List of users on the system) Your concept would need a unified dial tool, so that the right one is triggered . Parts of your concept is possible i guess trough netprofile, parts of it are possible with linecontrol/mserver(?) parts of it sounds like SuSEs meta-pppd (smpppd). I think drakconnect should be splitted up in LAN and internet, since these both are different. Maybe this should go in the wiki instead of discussing it here ? Steffen
