tched to 12.1-RELEASE.
> Both versions have same symptoms.
>
> I get "dhclient: send_packet: No buffer space available" to console and then
> I frequently lose connection after seeing it.
> After taking the wlan down and re-connect it with wpa_supplicant, I usually
> ge
acket: No buffer space available" to console and then I
frequently lose connection after seeing it.
After taking the wlan down and re-connect it with wpa_supplicant, I usually get
a connection back.
On the side note, I also see these outputs to console and syslog:
ath0: bb hang detected (0x4),
Chuck Swiger wrote:
Does the problem go away if you use a trivial permit all PF ruleset?
When i took off scrub altq No buffer space available messages were
gone, but dhclient did still renew the same address.
Does the problem go away if you use a trivial IPFW permit all
instead of PF?
Chuck Swiger wrote:
Typically, that sort of message indicates that the firewall rules are
preventing traffic from going out, or packets are getting stuck in a
queue until it fills up, or maybe even a bug somewhere in the
particular combination of kernel firewall options enabled, high
Pertti Kosunen wrote:
What could cause dhclient sometimes to fail renew the lease? I updated
world and moved to pf from ipfw same time so i don't know which to blame.
This happens from twice a day to every few days.
Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available
: No buffer space available
Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available
Jul 21 03:45:02 myserver dhclient: New IP Address (xl0): x.x.x.x
Jul 21 03:45:02 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0
Jul 21 03:45:02 myserver dhclient: New Broadcast Address (xl0
What could cause dhclient sometimes to fail renew the lease? I updated
world and moved to pf from ipfw same time so i don't know which to blame.
This happens from twice a day to every few days.
Jul 21 03:44:55 myserver dhclient: send_packet: No buffer space available
Jul 21 03:44:55 myserver
