Bridging vs Nat

James Harper james.harper
Sat Feb 22 14:33:17 PST 2003

I get that error and I'm not doing any form of bridging. I just posted
something about this yesterday, is your card sharing interrupts with
anything? Mine is sharing with my soundcard, and when I use the
soundcard whilst there is hostap traffic, I get that error and total

I'm guessing here, but maybe your wireless card is sharing an interrupt
with something that gets used when your ap's website is accessed
(harddisk controller is the only thing I can think of)... Is this the
case? Most likely your hostap machine sit's idle otherwise yes?


> -----Original Message-----
> From: hostap-admin at [mailto:hostap-admin at] 
> On Behalf Of Mojo B. Nichols
> Sent: Sunday, 23 February 2003 13:01
> To: hostap at
> Subject: Bridging vs Nat 
> I have a problem with a card causing my system to lock up 
> (see previous subject freeze).  I am using bridging.  I can 
> reproduce a lock up simply by pointing my wirless client at 
> my access point's website.  the error that I get is:
> Feb 22 04:10:51 localhost kernel: wlan0: Rx: len(16384) > 
> MAX(2304) Feb 22 09:32:40 localhost kernel: wlan0: Interrupt, 
> but SWSUPPORT0 does not match: 8A32 != 8A32 - card removed?
> Anyway, I'm wondering if using NAT and giving wlan0 it's own 
> address would make this more reliable?
> I come to this hypothesis, because it is so easy recreate the 
> problem (point the client at ap's website) but it seems to 
> fairly reliable for surfing the web.  BTW the network 
> topology is firewall ---wired---> hostap -----wireless-----> laptop.
> Thanks in advance
> _______________________________________________
> HostAP mailing list
> HostAP at

More information about the Hostap mailing list