Hi, Then I shall provide what I possibly can.
When using dhclient to configure my wi-driven lucent card (latest firmware), it will work for a while (varying number of minutes - up to 30 or so) and then stop working, while spitting out messages like: wi0: bad alloc 55c != 2a2, cur 0 nxt 0 wi0: device timeout wi0: bad alloc 573 != 2a2, cur 0 nxt 0 wi0: device timeout and wi0: timeout in wi_seek to fc02/0 wi0: timeout in wi_seek to fc03/0 Pulling the card and re-inserting it + restarting dhclient will give me a network link again for another few minutes, then the same story happens again. I have never seen this problem when using a static IP - my uptime is currently well over a week and I haven't had to reconfigure once. Hope this helps. Best regards, /Eirik On Tue, 05 Aug 2003 08:56:38 -0600 (MDT) "M. Warner Losh" <[EMAIL PROTECTED]> wrote: > In message: <[EMAIL PROTECTED]> > Martin Blapp <[EMAIL PROTECTED]> writes: > : > Is this going to cure the cases where using DHCP results in my > network: > link going dead about ~30 minutes after getting a lease? At > that point: > it starts spitting out timeout errors and stuff, and i > have to: > unplug/replug the card and re-start dhclient to get > connectivity again..: > : Unless the lease time was ~30 minutes and you've changed networks, I > doubt it.: > : This sounds like a if_wi driver problem. Warner should be able to > tell you: more. > > I still don't have a clear problem statement. > > Warner > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "[EMAIL PROTECTED]"
pgp00000.pgp
Description: PGP signature
