It's like that because TX has allocated/filled the available mbufs,
but the TX doesn't restart when the link comes up.
Adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail t
I tried many SOCKS4 proxies from
http://sockslist.net/proxy/server-socks-hide-ip-address and mostly I am
getting this error:
Error 120 (net::ERR_SOCKS_CONNECTION_FAILED): Unknown error.
Only one of them succeeded.
SOCKS5 however works ok.
On firefox I am getting similar symptoms, it can't conne
On 25.12.2012 07:01, Ryan Stone wrote:
I don't believe that this is fixed in later versions of the driver.
The problem is that when the interface loses link the transmit queue
can fill up. Once that happens the driver never gets any more calls
from the network stack to make it send packets. P
On 24 December 2012 17:59, Mike Karels wrote:
>> [adrian]
>> I think we may need another if_* method which specifically attempts to
>> service the TX queue again; versus just waiting for if_transmit() to
>> make some progress.
> In my opinion, it is wrong of the drivers to queue packets while li
> On 24 December 2012 17:01, Ryan Stone wrote:
> > I don't believe that this is fixed in later versions of the driver. The
> > problem is that when the interface loses link the transmit queue can fill
> > up. Once that happens the driver never gets any more calls from the network
> > stack to make
On 24 December 2012 17:01, Ryan Stone wrote:
> I don't believe that this is fixed in later versions of the driver. The
> problem is that when the interface loses link the transmit queue can fill
> up. Once that happens the driver never gets any more calls from the network
> stack to make it send p
I don't believe that this is fixed in later versions of the driver. The
problem is that when the interface loses link the transmit queue can fill
up. Once that happens the driver never gets any more calls from the network
stack to make it send packets. Pinging the interface fixes it because the
dri
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
