I'm basically able to get the cards to work without locking up with
the lastest version of the 5.x driver along with a hacked up 4.x
driver by doing this:

both> /usr/sbin/wicontrol -i wi0 -n "FreeBSD IBSS"
both> /usr/sbin/wicontrol -i wi0 -p 1
both> /usr/sbin/wicontrol -i wi0 -c 1
both> /usr/sbin/wicontrol -i wi0 -f 10
both> /usr/sbin/wicontrol -i wi0 -t 3

router(pci)> /usr/sbin/wicontrol -i wi0 -s "router"
router(pci)> /sbin/ifconfig wi0 inet 10.0.0.1 netmask 0xff000000

laptop(pcmcia)> /usr/sbin/wicontrol -i wi0 -s "router"
laptop(pcmcia)> /sbin/ifconfig wi0 inet 10.0.0.5 netmask 0xff000000

The problem is that if I unload/reload a driver the card doesn't seem
to want to xmit or something (sorry :) ), the way that I fix this is
to ping the card from the host that didn't reset, that gets it working
right away:

/usr/local/etc # ping 10.0.0.5
PING 10.0.0.5 (10.0.0.5): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
64 bytes from 10.0.0.5: icmp_seq=5 ttl=64 time=11680.270 ms
64 bytes from 10.0.0.5: icmp_seq=17 ttl=64 time=5.407 ms
64 bytes from 10.0.0.5: icmp_seq=18 ttl=64 time=4.730 ms
64 bytes from 10.0.0.5: icmp_seq=19 ttl=64 time=5.394 ms
64 bytes from 10.0.0.5: icmp_seq=20 ttl=64 time=5.364 ms

I started pinging from 10.0.0.1 right before seeing the '5' pop up.

I also noticed that:

a) wi card doesn't show itself in the local arp table
   (arp -na doesn't list itself)
b) there's no call to ifmedia_init() in the wi driver, but I don't
   think that matters.

Any hints?

The hacked up wi driver is here:
http://people.freebsd.org/~alfred/wi/

thanks,
-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Represent yourself, show up at BABUG http://www.babug.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to