On Mon, May 12, 2014 at 10:39:52PM +0200, Manuel Bouyer wrote:
On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote:
[...]
traceroute packets from outside look like the are anwsered, but ICMP ECHO is
not answered.
The interface recovers with an ifconfig wmX down/up.
While
Hi,
I have two observations on 6.99.44 (amd64/evbarm) where a wm-interface
send-queue is filled to the max. sendto()-calls terminate with ENOBUFS.
net.interfaces.wm3.sndq.len = 256
net.interfaces.wm3.sndq.maxlen = 256
net.interfaces.wm3.sndq.drops = 20007
the interface status is:
wm3:
Hi, Frank.
(2014/05/13 4:56), Frank Kardel wrote:
Hi,
I have two observations on 6.99.44 (amd64/evbarm) where a wm-interface
send-queue is filled to the max. sendto()-calls terminate with ENOBUFS.
net.interfaces.wm3.sndq.len = 256
net.interfaces.wm3.sndq.maxlen = 256
On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote:
[...]
traceroute packets from outside look like the are anwsered, but ICMP ECHO is
not answered.
The interface recovers with an ifconfig wmX down/up.
While I do not know how to provoke this on wm (just happens once a week). I
On 05/12/14 22:39, Manuel Bouyer wrote:
On Mon, May 12, 2014 at 09:56:30PM +0200, Frank Kardel wrote:
[...]
traceroute packets from outside look like the are anwsered, but ICMP ECHO is
not answered.
The interface recovers with an ifconfig wmX down/up.
While I do not know how to provoke this