Re: "dhclient: send_packet: No buffer space available"
On Tue, Dec 3, 2019 at 8:39 PM Yoshihiro Ota wrote: > > Hi, > > I recently switched internet service provider and got much faster connection. > However, I started seeing some unstable connections between the WiFi router > and FreeBSD. > I was on FreeBSD 12.0-RELEASE and switched 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 > get a connection back. > > On the side note, I also see these outputs to console and syslog: > ath0: bb hang detected (0x4), resetting > ath0: ath_legacy_rx_tasklet: sc_inreset_cnt > 0; skipping > > Does anyone have any advice how to fix/work-around or where to start looking: > ath driver, dhclinet, kernel, wlan, and/or wpa_supplicant? > > Thanks, > Hiro > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" IIRC, that means that you are running out of mbufs. There are two ways to fix it, increase the number of mbufs (kern.ipc.nmbufs or kern.ipc.nmbclusters), or increase the aggressiveness of closing old network connections (I do this from a menu in pfSense, so I don't remember the command line setting name off hand). Searching for the error online suggests that this error can also be caused if the layer 2 network connection failed, such as a wlan association failure. Or that there is a network filter somewhere that is sinking/blocking packets and that this is causing the mbuf queue to fill up (every network request requires an mbuf). In the past, people have also fixed this by swapping the network hardware. Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: dhclient: send_packet: No buffer space available
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? Old ipfw rules seem to be working ok. So it's probably something in my pf-rules, have to rewrite and test again. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient: send_packet: No buffer space available
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 optimization or CPUTYPE settings, and your particular hardware, depending on how lucky you are. :-) Does the problem go away if you use a trivial permit all PF ruleset? Does the problem go away if you use a trivial IPFW permit all instead of PF? Does the problem go away if you use a stock 5.4 release kernel? The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or the 918/920's are pretty decent, but anyway-- ...does the problem go away if you switch to another (known good) NIC? System was ok with 5.3-RELEASE custom kernel with ipfw. PF logs all block rules and nothing gets to pflog on those dhclient errors. I try those tips you gave, thanks. Stuck in a queue sounds most likely to be the case. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient: send_packet: No buffer space available
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 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): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x Pf.conf dmesg: http://www.saunalahti.fi/~pkosunen/pf.conf http://www.saunalahti.fi/~pkosunen/dmesg Anyone know what what could be the problem with dhclient? Some buffer is full but what? Nic is 3Com 3c905B-TX, FreeBSD 5.4-STABLE PF. vmstat -m output: http://www.saunalahti.fi/~pkosunen/vmstat.txt # grep dhclient /var/log/messages: Jul 25 20:46:55 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:46:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:46:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:46:56 myserver dhclient: New Routers: 62.142.70.1 Jul 25 20:51:28 myserver dhclient: New IP Address (xl0): 62.142.70.119 Jul 25 20:51:28 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 25 20:51:28 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 25 20:51:28 myserver dhclient: New Routers: 62.142.70.1 Jul 26 21:59:20 myserver dhclient: send_packet: No buffer space available Jul 26 21:59:51 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 26 21:59:51 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 26 21:59:51 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 26 21:59:51 myserver dhclient: New Routers: 62.142.70.1 Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:05 myserver dhclient: send_packet: No buffer space available Jul 30 23:34:13 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 30 23:34:13 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 30 23:34:13 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 30 23:34:13 myserver dhclient: New Routers: 62.142.70.1 Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:06 myserver dhclient: send_packet: No buffer space available Jul 31 02:09:10 myserver dhclient: New IP Address (xl0): 62.142.70.200 Jul 31 02:09:10 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Jul 31 02:09:10 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Jul 31 02:09:10 myserver dhclient: New Routers: 62.142.70.1 Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:26 myserver dhclient: send_packet: No buffer space available Aug 1 20:11:31 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 1 20:11:31 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 1 20:11:31 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 1 20:11:31 myserver dhclient: New Routers: 62.142.70.1 Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:11 myserver dhclient: send_packet: No buffer space available Aug 2 23:03:19 myserver dhclient: New IP Address (xl0): 62.142.70.200 Aug 2 23:03:19 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 2 23:03:19 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 2 23:03:19 myserver dhclient: New Routers: 62.142.70.1 Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:12 myserver dhclient: send_packet: No buffer space available Aug 3 22:29:21 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 3 22:29:21 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 3 22:29:21 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 3 22:29:21 myserver dhclient: New Routers: 62.142.70.1 Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:46 myserver dhclient: send_packet: No buffer space available Aug 4 01:05:55 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 4 01:05:55 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 4 01:05:55 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 4 01:05:55 myserver dhclient: New Routers: 62.142.70.1 Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:32 myserver dhclient: send_packet: No buffer space available Aug 6 16:53:37 myserver dhclient: New IP Address (xl0): 62.142.70.113 Aug 6 16:53:37 myserver dhclient: New Subnet Mask (xl0): 255.255.254.0 Aug 6 16:53:37 myserver dhclient: New Broadcast Address (xl0): 62.142.71.255 Aug 6 16:53:37 myserver dhclient: New Routers: 62.142.70.1 Aug 7 06:49:07 myserver dhclient: send_packet: No buffer space available Aug
Re: dhclient: send_packet: No buffer space available
Pertti Kosunen wrote: 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 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): x.x.x.x Jul 21 03:45:02 myserver dhclient: New Routers: x.x.x.x Pf.conf dmesg: http://www.saunalahti.fi/~pkosunen/pf.conf http://www.saunalahti.fi/~pkosunen/dmesg Anyone know what what could be the problem with dhclient? Some buffer is full but what? Nic is 3Com 3c905B-TX, FreeBSD 5.4-STABLE PF. 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 optimization or CPUTYPE settings, and your particular hardware, depending on how lucky you are. :-) Does the problem go away if you use a trivial permit all PF ruleset? Does the problem go away if you use a trivial IPFW permit all instead of PF? Does the problem go away if you use a stock 5.4 release kernel? The 3Com 3c905B-TX is an OK NIC, apparently the later C revision or the 918/920's are pretty decent, but anyway-- ...does the problem go away if you switch to another (known good) NIC? -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
