Re: joining the wi lockup bandwagon...

Andrew Thomson <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
Last night I disabled the WEP, the first suggestion I received and the
wireless network ran perfectly all night.

However I understand it's not so good running without any encryption. 

How's everyone else doing it?

I did the following last night which seemed to work.

Install racoon on my firewall and laptop.

run this with setkey -f on the laptop.

spdadd 192.168.14.2/32 0.0.0.0/0 any -P out ipsec
   esp/tunnel/192.168.14.2-192.168.14.1/require;
spdadd 0.0.0.0/0 192.168.14.2/32 any -P in ipsec
   esp/tunnel/192.168.14.1-192.168.14.2/require;

Then the same thing on the firewall with out/in switched around.

Startup racoon and I was away. A tcpdump on wi0 showed only ESP packets
being transmitted.

So is this all I need to do to secure my wireless link??

cheers,

ajt.

On Thu, 2002-10-31 at 12:04, Ian Dowse wrote:
> In message <[email protected]>, Wesley Morgan
>  writes:
> >On 30 Oct 2002, Andrew Thomson wrote:
> 
> >Oct 30 01:34:41 mulla /kernel: wi0: timeout in wi_cmd 0x0002; event
> >status 0x8000
> >Oct 30 01:34:41 mulla /kernel: wi0: timeout in wi_cmd 0x0000; event
> >status 0x8000
> 
> >> wicontrol -e 1
> >> wicontrol -k passw
> >
> >Turn off the WEP by removing the last two lines. It works for my orinocco
> >cards, and I think it helps for the prism. I haven't seen Warner chime
> >in with his words of wisdom on the real problem here, although I did see
> >some references to missed interrupts or something.
> 
> Try adding a "DELAY(50000);" just before the "return;" at the end
> of wi_init(). I've found that this helps a lot with the above errors,
> though I don't know why.
> 
> Ian
> 
> To Unsubscribe: send mail to [email protected]
> with "unsubscribe freebsd-mobile" in the body of the message




To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.