This whole discussion seems off-topic to me, but I'll try to clear this up.
Daniel, I believe you are seeing a syslog tag called '[INVALID in] ' or
'[INVALID out] ', nothing more. See the LOG target in the iptables man page
(eg, -j LOG --log-prefix '[INVALID in] ').
On 2013-04-09, at 3:51 PM
Hi Daniel,
On 09/04/13 21:05 +0200, Daniel Curtis wrote:
Hi andika.
Another INVALID packet description. I read a lot of
information and I don't know what is the truth. Frankly,
the first time I see a description, which concerns RAM memory.
So, I have a 1 GB of RAM memory. Just for example; fre
Hi andika.
Another INVALID packet description. I read a lot of
information and I don't know what is the truth. Frankly,
the first time I see a description, which concerns RAM memory.
So, I have a 1 GB of RAM memory. Just for example; free -m
command result;
used: 640, free: 230
and top command;
On Tue, Apr 9, 2013 at 11:18 PM, Daniel Curtis wrote:
> Hi
>
> As we know iptables INVALID state means, that
> the packet is associated with no known connection,
> right? So, if I have a lot of INVALID entries in my
> log files, does it means, that something is wrong?
> Hidden process etc.?
>
>
Ju
Hi
As we know iptables INVALID state means, that
the packet is associated with no known connection,
right? So, if I have a lot of INVALID entries in my
log files, does it means, that something is wrong?
Hidden process etc.?
An example of logged entries;
t4 kernel: [18776.221378] [INVALID in] IN=
5 matches
Mail list logo