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
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: de
Hi,
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..
Thanks for the
Hi,
> 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
Hi all,
If you used wi(4) or en(4) wavelan cards and you had problems with dhclient,
you should try this patch, which treats interfaces with media settings
differently.
http://people.freebsd.org/~mbr/patches/dhclient-interfacepolling-fixup.diff
I'll produce a more clean patch this evening, and
