pe wrote:
>> Maybe, but do not believe it, because when you turn it on, the counter
>
>
> Turn what on, exactly?
>
>
>> "dropped due to the socket" has gradually increased, this machine acts
>
>
> Please provide the exact output from the "netsta
On Mon, Oct 27, 2014 at 09:31:04AM -0200, Tiago Felipe wrote:
> Maybe, but do not believe it, because when you turn it on, the counter
Turn what on, exactly?
> "dropped due to the socket" has gradually increased, this machine acts
Please provide the exact output from th
Maybe, but do not believe it, because when you turn it on, the counter
"dropped due to the socket" has gradually increased, this machine acts
as pppoe concentrator, mpd5 and netgraph ..
I have clients with public IP and nat44.
I'm doing tests yet, but I've read a lot about an
I assume you mean "dropped due to *no *socket" which means your seeing
requests to a port which isn't open, possibly due to being port scanned?
On 27/10/2014 11:00, Tiago Felipe wrote:
Good afternoon!
I have seen "dropped due to the socket" on multiple servers wit
Good afternoon!
I have seen "dropped due to the socket" on multiple servers with
Freebsd, this case is a Release 10.
# Netstat -s -s
...
4614884 dropped due to the socket
...
In this case the current flow is 700mbits download and 80mbits upload,
averaging 130kpps.
I've done
Good afternoon!
I have seen "dropped due to the socket" on multiple servers with
Freebsd, this case is a Release 10.
# Netstat -s -s
...
4614884 dropped due to the socket
...
In this case the current flow is 700mbits download and 80mbits upload,
averaging 130kpps.
I've done
