Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
Kel Modderman wrote: > Indeed, Matt's statements were about madwifi-ng, I think. And it is good > he brought it up, as the madwifi-ng codebase could be entering debian > any time soon. Yes, sorry for the confusion. I didn't realise madwifi-ng wasn't in the archive yet and this bug is present in the madwifi-ng packages. Cheers -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz signature.asc Description: OpenPGP digital signature
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
Celejar wrote: On Wed, 26 Apr 2006 23:39:46 +1000 Kel Modderman <[EMAIL PROTECTED]> wrote: Are you using madwifi-ng from upstream trunk? Or the version provided by the debian package? Kel. Hi, Thanks for the responses. I'm using the Debian package (as stated in the original bug report) which uses the old codebase. Thanks, for clarifying. For a brief moment I suspected you may have been using upstream madwifi-ng :-) Matt Brown's comment that The message is caused by /etc/network/if-post-down.d/wireless-tools attempting to run iwconfig "$IFACE" mode auto which of course fails on madwifi as it does not allow interface mode changes. The best solution imo would be to fix madwifi so that it did allow mode changes, but I can't see that happening anytime soon as I understand it would involve rewriting half the driver. is not correct for the old codebase; issuing 'mode master' followed by 'mode managed', for example, works fine. His point may be true for the new codebase, though; I think I remember seeing something to that effect on madwifi.org. Indeed, Matt's statements were about madwifi-ng, I think. And it is good he brought it up, as the madwifi-ng codebase could be entering debian any time soon. I'll make a suggestion for the docs within a day or so. Thanks! Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
On Wed, 26 Apr 2006 23:39:46 +1000 Kel Modderman <[EMAIL PROTECTED]> wrote: > Are you using madwifi-ng from upstream trunk? Or the version provided by > the debian package? > > Kel. Hi, Thanks for the responses. I'm using the Debian package (as stated in the original bug report) which uses the old codebase. Matt Brown's comment that > The message is caused by /etc/network/if-post-down.d/wireless-tools > attempting to run iwconfig "$IFACE" mode auto which of course fails on > madwifi as it does not allow interface mode changes. > > The best solution imo would be to fix madwifi so that it did allow mode > changes, but I can't see that happening anytime soon as I understand it > would involve rewriting half the driver. is not correct for the old codebase; issuing 'mode master' followed by 'mode managed', for example, works fine. His point may be true for the new codebase, though; I think I remember seeing something to that effect on madwifi.org. I'll make a suggestion for the docs within a day or so. Thanks, Celejar -- ssuds.sourceforge.net - Home of Ssuds and Ssudg, a Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
celejar wrote: Package: madwifi-source Version: 0.svn20060207-4 Severity: normal I am using madwifi with an Atheros AR5212 802.11abg (rev 01). 'ifdown ath0' gives the following error: Error for wireless request "Set Mode" (8B06) : SET failed on device ath0 ; Invalid argument. The same error occurs when issuing 'iwconfig ath0 mode auto', so I assume that ifdown is also doing 'mode auto' or something similar. This is only a minor quibble with no effect on usability (AFAICT the driver works flawlessly) but perhaps the documentation should include a note acknowledging this. Are you using madwifi-ng from upstream trunk? Or the version provided by the debian package? Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
Kel Modderman wrote: > Ok, thanks for reporting this issue (and sorry for a late reply!). > > Could you please suggest some text for inclusion in the docs? (if not I > guess I could think of something :-) ) I did look into this the other day just to verify that it wasn't anything critical. I haven't responded yet because I'm not sure whose fault the problem is and hence how to fix it. The message is caused by /etc/network/if-post-down.d/wireless-tools attempting to run iwconfig "$IFACE" mode auto which of course fails on madwifi as it does not allow interface mode changes. The best solution imo would be to fix madwifi so that it did allow mode changes, but I can't see that happening anytime soon as I understand it would involve rewriting half the driver. I think the best compromise would be for wireless-tools to silently hide (or redirect to syslog) any errors that occur when "deconfiguring" an interface. I've copied the wireless-tools maintainers on this mail to see if they have any thoughts on this approach. Cheers -- Matt Brown [EMAIL PROTECTED] Mob +64 21 611 544 www.mattb.net.nz signature.asc Description: OpenPGP digital signature
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
Matt Brown wrote: Kel Modderman wrote: Ok, thanks for reporting this issue (and sorry for a late reply!). Could you please suggest some text for inclusion in the docs? (if not I guess I could think of something :-) ) I did look into this the other day just to verify that it wasn't anything critical. I haven't responded yet because I'm not sure whose fault the problem is and hence how to fix it. The message is caused by /etc/network/if-post-down.d/wireless-tools attempting to run iwconfig "$IFACE" mode auto which of course fails on madwifi as it does not allow interface mode changes. The best solution imo would be to fix madwifi so that it did allow mode changes, but I can't see that happening anytime soon as I understand it would involve rewriting half the driver. I think the best compromise would be for wireless-tools to silently hide (or redirect to syslog) any errors that occur when "deconfiguring" an interface. I've copied the wireless-tools maintainers on this mail to see if they have any thoughts on this approach. Are you referring to the "madwifi-old" or "madwifi-ng" codebase? Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
celejar wrote: Package: madwifi-source Version: 0.svn20060207-4 Severity: normal I am using madwifi with an Atheros AR5212 802.11abg (rev 01). 'ifdown ath0' gives the following error: Error for wireless request "Set Mode" (8B06) : SET failed on device ath0 ; Invalid argument. The same error occurs when issuing 'iwconfig ath0 mode auto', so I assume that ifdown is also doing 'mode auto' or something similar. This is only a minor quibble with no effect on usability (AFAICT the driver works flawlessly) but perhaps the documentation should include a note acknowledging this. Ok, thanks for reporting this issue (and sorry for a late reply!). Could you please suggest some text for inclusion in the docs? (if not I guess I could think of something :-) ) Thanks, kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#364458: madwifi-source: Error on 'ifdown' and 'iwconfig mode auto'
Package: madwifi-source Version: 0.svn20060207-4 Severity: normal I am using madwifi with an Atheros AR5212 802.11abg (rev 01). 'ifdown ath0' gives the following error: Error for wireless request "Set Mode" (8B06) : SET failed on device ath0 ; Invalid argument. The same error occurs when issuing 'iwconfig ath0 mode auto', so I assume that ifdown is also doing 'mode auto' or something similar. This is only a minor quibble with no effect on usability (AFAICT the driver works flawlessly) but perhaps the documentation should include a note acknowledging this. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages madwifi-source depends on: ii build-essential 11.2 informational list of build-essent ii bzip2 1.0.2-7high-quality block-sorting file co ii debhelper 4.2.36 helper programs for debian/rules ii module-assistant 0.10.3 tool to make module package creati ii sharutils 1:4.2.1-13 shar, unshar, uuencode, uudecode Versions of packages madwifi-source recommends: ii kernel-package9.008 A utility for building Linux kerne -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
