Ok, perhaps we should collect what features we need and how it could look
like.
in general:
* wired and wireless-networked should be configured the same way
* a readable config-file (I like the one Aaron Griffin has posted)
* parameters not needed should be optinal
* optional commands which can be called after connecting and before
disconnecting are usefull for VPN or what ever you want
* Daemon shouldn`t fail if not all devices are up
* What about hotplug?
* Is it possible to setup the network when connecting a cable or pressing
the wlan-button?
especially for wireless setup:
* WPA-Encryption must be supported out-of-the-box; WEP is know to be useless
* What should we do if we still have a connection (a wired for example)?
packages we need:
* ndiswrapper
* wpa_supplicant
In future we could think about integrating this feature into the setup-iso, so
one will be able to install Arch over wlan :-)
Have I forgotten something important?
Pierre
Am Donnerstag, 5. Mai 2005 04:46 schrieb Philip Dillon-Thiselton:
> OK, Judd's looks a bit complex to me - not too transparent but I like
> phrak's simplification
>
> FYI I already had a crack at using scanning, you can see my stuff in the
> thread
> http://bbs.archlinux.org/viewtopic.php?t=10707&postdays=0&postorder=asc&sta
>rt=0
>
> It can detect the strongest AP and connect to it - at least I think it
> can, my card don%u2019t scan in linux. I totally agree with Phrak re: I
> like readable names for config variables
>
> I used a "case in" system for my profiles and given the simplification
> that phrak has suggested you can see how easily that profile system would
> lend itself to the case approach I implemented.
>
> I also prefer the one file approach as I feel it is more "Arch"
>
> However, I also feel that wireless="eth0 mode managed essid mylan" may
> still be a bit limited. I also feel that between the 4 of us (Phrak,
> Pierre, Judd and myself) we can knock up some of the best network
> initscripts around, and certainly some of the best wireless initscripts.
>
> Judd, can you provide some diffs for your proposed initscripts, please?
> All my diffs are linked in the forum thread :)
>
> Phil
>
>
>
>
>
> ----- Original Message -----
>
> On Wednesday 04 May 2005 01.14, Aaron Griffin wrote:
> > > Ok, my input...Judd, I actually like your implementation slightly
> > > better than mine (and Pierre's)
> > >
> > > Let me suggest something:
> > > -----------------------------------------------------------------------
> > >---- ---------------- /etc/conf.d/net_profiles
> > > lo:
> > > config="lo 127.0.0.1"
> > > home:
> > > wireless="eth0 mode managed essid mylan"
> > > config="eth0 192.168.1.2 netmask 255.255.255.0"
> > > route="default gw 192.168.1.1"
> > > on_connect="echo connected @ home"
> > > school:
> > > wireless="eth0 mode managed essid school"
> > > config="eth0 dhcp"
> > > on_disconnect="echo disconnect from school"
> > > wired:
> > > config="eth1 192.168.0.2 netmask 255.255.255.0"
> > > route="default gw 192.168.0.1"
> > > -----------------------------------------------------------------------
> > >---- ---------------- /etc/rc.conf:
> > > NET_PROFILES=(lo home !school !wired)
> > > -----------------------------------------------------------------------
> > >---- ----------------
> > >
> > > This is some random conglomaration... I like readable names for config
> > > variables... I've come to like the way you setup the whole options
> > > line as one thing instead of individual parameters... it vastly
> > > simplifies these things.
> > >
> > > source the profile's file... if "wireless" exists, do that stuff
> > > first, then do ifconfig $config... same with route (if exists)...
> > > on_connect and on_disconnect are kinda obvious.
> > >
> > > another stray idea I've been tossing around is the ability to create a
> > > profile named "scan" (let's say) which uses iwlist to match the
> > > strongest AP+ESSID with a profile and connect - it shouldn't require
> > > any changes to the main network script, though (that implies that each
> > > profile shouldn't have varying variable names...)
> > > run the scan, source the proper profile, and the network script does
> > > it's job
> > >
> > > as a disclaimer, these are just random musings... and may not be very
> > > thought out right now...
> >
> > Very nice construction. It would be nice to have an icon on the desktop
>
> that
>
> > does a rescan when a notebook is reopened at a new place.
> >
> > regards
> > guran
> > --
> > Arch Linux 0.7 Wombat
> >
> > Only in a society that has 'a priori' defined what is the truth
> > can the result from the evolution of life be defined false.
> >
> > _______________________________________________
> > arch mailing list
> > [email protected]
> > http://www.archlinux.org/mailman/listinfo/arch
>
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
--
Pierre Schmitz
http://archlinux.laber-land.de
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
