On 10/27/10 17:21, frantisek holop wrote: > hmm, on Wed, Oct 27, 2010 at 07:39:06AM +0100, Jason McIntyre said that >> On Wed, Oct 27, 2010 at 12:23:41AM +0200, frantisek holop wrote: >>> >>> ifconfig(9) says about debug: >>> >>> debug Enable driver-dependent debugging code; usually, this >>> turns on extra console error logging. >>> >>> -debug Disable driver-dependent debugging code. >>> >>> but it seems like debug actually takes a debug mask parameter. >> >> are you sure that's the case? i can only see that it sets IFF_DEBUG. >> then various drivers do stuff if that is set. > > hm. my source of confusion could be that i ran > > $ sudo ifconfig iwn0 debug > $ dmesg > <nothing new> > <playing around> > $ dmesg > <nothing new> > > $ sudo ifconfig iwn0 debug 255
This will change your ip address to 0.0.0.255, causing all sorts of related traffic. /Alexander > $ sudo sh /etc/netstart > $ dmesg > <lots of handshake info from iwn0> > > so i thought it was because of the mask... > but actually 'debug' produced messages only > during the handshake, my traffic generating > attempts did not hit on any other iwn debug > functionality. > > i will check again when i get home, but it's > now quite likely that the handshake messages > will show up after just turning on debug. > > sorry about the noise. > > anything else i could do to try and track down > the high number of IErrs on this interface (my previous thread) > otherwise i am just going to submit a bug.. > > -f
