Re: debian network/interfaces vs wlan.conf &c
<[email protected]> Mon, 10 Oct 2005 10:24:30 +0100
| Newsgroups | gmane.linux.linux-wlan.user |
|---|---|
| Message-ID | <20051010092430.CCLI24460.aamta12-winn.ispmail.ntl.com@smtp.ntlworld.com> |
> From: James Hughes <[email protected]> > > Hi, > > I use debian unstable and have always used the /etc/network/interfaces > file to set wireless options, eg. 'wireless_essid myssid', and that > has always worked fine. > > In googling around for solutions to my current difficulties (more on > that in a subsequent post, probably) I have become aware of the files > /etc/wlan.conf and wlanctl-DEFAULT. Do I need to worry about these if > I'm setting things in the interfaces file and doing ifup/ifdown? > Not really. The way debian seems to package up the stuff from the wlan-ng project is to cut out these kind of files and work things into using /etc/network/interfaces as you describe - in other words they 'debian-ise' the control & options related files. Presumably you have a script in /etc/network/if-pre-up.d which has the wlan-ng control nitty-gritty stuff in. If you wanted any more sophisticated control you would have to edit that. Note also that the last time I checked, this debian-isation dropped the firmware files as well. Operation can often be improved by using the ram firmware uploads at runtime - I had to script this up myself (on my Ubuntu box, which of course is based on Debian). Karl ----------------------------------------- Email sent from www.ntlworld.com Virus-checked using McAfee(R) Software Visit www.ntlworld.com/security for more information