Kernel: NET: messages suppressed (I am sure it has been covered before)

Kernel: NET: messages suppressed (I am sure it has been covered before)

[Frischknecht Peter]

I need to know WHAT MESSAGE WAS SUPPRESSED.

I am getting slammed.  My server will display anywhere from a few
hundred to 50K messages suppressed.

Previous posters have suggested that if I go early enough in my logs,
that I will find the original suppressed message.
NOT TRUE.

I am desperate.  These messages are an indication of a larger problem,
but I am unable to diagnose what.
My network is fairly small (650 nodes), and I have been receiving these
messages time and again.  Sometimes every 3 hours, sometimes every 3
days.  

Network analizers (Ntop, iptraf) have been unable to identify the source
of the traffic.  If I run these utilities on the server, they freeze
(while a flood is going on).  If I run the utilities on a different
computer on a port of the switch, they don't see the traffic intended
for the server (obviously).  If I configure the switch for a "monitor"
port (one that sees all traffic) and plug a different computer on that
port, then that computer freezes too, along with the server.

The few times that we cought a machine WHILE it was generating the
traffic, we could not find any evidence of wrongdoing.  No viruses, no
trojan horses, no smoking gun.  The ONLY mechanism that stops the
traffic is blocking ARPs at the switch.  But I feel that ARP is another
symptom, not the actual problem (like an ICMP flood).

The switches used are 12x HP J4121A (Procurve 4000M) and one HP5308XL
(fiber cross-connect).

Once the Linux router gets slammed, it is a matter of time before it
freezes and dies.

ANY help would be appreciated.

Here is a sample:
****
[root@ess-uvce root]# grep "kernel: NET" /var/log/messages;
Oct 21 15:34:00 ess-uvce kernel: NET: 205 messages suppressed.
Oct 21 15:34:05 ess-uvce kernel: NET: 33484 messages suppressed.
Oct 21 15:34:10 ess-uvce kernel: NET: 33264 messages suppressed.
Oct 21 15:34:15 ess-uvce kernel: NET: 31204 messages suppressed.
Oct 21 15:34:20 ess-uvce kernel: NET: 33229 messages suppressed.
Oct 21 15:34:25 ess-uvce kernel: NET: 30596 messages suppressed.
Oct 21 15:34:30 ess-uvce kernel: NET: 33175 messages suppressed.
Oct 21 15:34:35 ess-uvce kernel: NET: 31174 messages suppressed.
Oct 21 15:34:40 ess-uvce kernel: NET: 33076 messages suppressed.
Oct 21 15:34:45 ess-uvce kernel: NET: 30534 messages suppressed.
Oct 21 15:34:50 ess-uvce kernel: NET: 32551 messages suppressed.
Oct 21 15:34:55 ess-uvce kernel: NET: 31169 messages suppressed.
Oct 21 15:35:00 ess-uvce kernel: NET: 33317 messages suppressed.
Oct 21 15:35:05 ess-uvce kernel: NET: 31162 messages suppressed.
Oct 22 01:09:44 ess-uvce kernel: NET: 26196 messages suppressed.
Oct 22 06:35:33 ess-uvce kernel: NET: 35332 messages suppressed.
Oct 22 06:35:38 ess-uvce kernel: NET: 35040 messages suppressed.
Oct 22 06:35:43 ess-uvce kernel: NET: 27654 messages suppressed.
Oct 22 06:35:48 ess-uvce kernel: NET: 27208 messages suppressed.
Oct 22 06:35:53 ess-uvce kernel: NET: 33073 messages suppressed.
Oct 22 06:35:58 ess-uvce kernel: NET: 36642 messages suppressed.
Oct 22 06:36:03 ess-uvce kernel: NET: 28798 messages suppressed.
Oct 22 06:36:08 ess-uvce kernel: NET: 21928 messages suppressed.
Oct 22 06:36:13 ess-uvce kernel: NET: 25631 messages suppressed.
Oct 22 06:36:18 ess-uvce kernel: NET: 30442 messages suppressed.
Oct 22 06:36:23 ess-uvce kernel: NET: 30225 messages suppressed.
Oct 22 06:36:28 ess-uvce kernel: NET: 28005 messages suppressed.
Oct 22 06:36:33 ess-uvce kernel: NET: 21884 messages suppressed.
Oct 22 06:36:38 ess-uvce kernel: NET: 23300 messages suppressed.
Oct 22 06:36:43 ess-uvce kernel: NET: 30853 messages suppressed.
Oct 22 06:36:48 ess-uvce kernel: NET: 27821 messages suppressed.
Oct 22 06:36:53 ess-uvce kernel: NET: 29570 messages suppressed.
Oct 22 06:36:58 ess-uvce kernel: NET: 22651 messages suppressed.
Oct 22 06:37:03 ess-uvce kernel: NET: 28761 messages suppressed.
Oct 22 06:37:08 ess-uvce kernel: NET: 32997 messages suppressed.
Oct 22 06:37:13 ess-uvce kernel: NET: 31389 messages suppressed.
Oct 22 06:37:18 ess-uvce kernel: NET: 24475 messages suppressed.
Oct 22 06:37:23 ess-uvce kernel: NET: 30712 messages suppressed.
Oct 22 06:37:28 ess-uvce kernel: NET: 34532 messages suppressed.
Oct 22 06:37:33 ess-uvce kernel: NET: 29573 messages suppressed.
Oct 22 06:37:38 ess-uvce kernel: NET: 25571 messages suppressed.
Oct 22 06:37:43 ess-uvce kernel: NET: 26330 messages suppressed.
Oct 22 06:37:48 ess-uvce kernel: NET: 30778 messages suppressed.
********

Kernel: NET: messages suppressed (I am sure it has been covered before)

[Frischknecht Peter]

I need to know WHAT MESSAGE WAS SUPPRESSED.

I am getting slammed.  My server will display anywhere from a few
hundred to 50K messages suppressed.

Previous posters have suggested that if I go early enough in my logs,
that I will find the original suppressed message. NOT TRUE.

I am desperate.  These messages are an indication of a larger problem,
but I am unable to diagnose what. My network is fairly small (650
nodes), and I have been receiving these messages time and again.
Sometimes every 3 hours, sometimes every 3 days.  

Network analizers (Ntop, iptraf) have been unable to identify the source
of the traffic.  If I run these utilities on the server, they freeze
(while a flood is going on).  If I run the utilities on a different
computer on a port of the switch, they don't see the traffic intended
for the server (obviously).  If I configure the switch for a "monitor"
port (one that sees all traffic) and plug a different computer on that
port, then that computer freezes too, along with the server.

The few times that we cought a machine WHILE it was generating the
traffic, we could not find any evidence of wrongdoing.  No viruses, no
trojan horses, no smoking gun.  The ONLY mechanism that stops the
traffic is blocking ARPs at the switch.  But I feel that ARP is another
symptom, not the actual problem (like an ICMP flood).

The switches used are 12x HP J4121A (Procurve 4000M) and one HP5308XL
(fiber cross-connect).

Once the Linux router gets slammed, it is a matter of time before it
freezes and dies.

ANY help would be appreciated.

Here is a sample:
****
[root@ess-uvce root]# grep "kernel: NET" /var/log/messages
Oct 21 15:34:00 ess-uvce kernel: NET: 205 messages suppressed.
Oct 21 15:34:05 ess-uvce kernel: NET: 33484 messages suppressed.
Oct 21 15:34:10 ess-uvce kernel: NET: 33264 messages suppressed.
Oct 21 15:34:15 ess-uvce kernel: NET: 31204 messages suppressed.
Oct 21 15:34:20 ess-uvce kernel: NET: 33229 messages suppressed.
Oct 21 15:34:25 ess-uvce kernel: NET: 30596 messages suppressed.
Oct 21 15:34:30 ess-uvce kernel: NET: 33175 messages suppressed.
Oct 21 15:34:35 ess-uvce kernel: NET: 31174 messages suppressed.
Oct 21 15:34:40 ess-uvce kernel: NET: 33076 messages suppressed.
Oct 21 15:34:45 ess-uvce kernel: NET: 30534 messages suppressed.
Oct 21 15:34:50 ess-uvce kernel: NET: 32551 messages suppressed.
Oct 21 15:34:55 ess-uvce kernel: NET: 31169 messages suppressed.
Oct 21 15:35:00 ess-uvce kernel: NET: 33317 messages suppressed.
Oct 21 15:35:05 ess-uvce kernel: NET: 31162 messages suppressed.
Oct 22 01:09:44 ess-uvce kernel: NET: 26196 messages suppressed.
Oct 22 06:35:33 ess-uvce kernel: NET: 35332 messages suppressed.
Oct 22 06:35:38 ess-uvce kernel: NET: 35040 messages suppressed.
Oct 22 06:35:43 ess-uvce kernel: NET: 27654 messages suppressed.
Oct 22 06:35:48 ess-uvce kernel: NET: 27208 messages suppressed.
Oct 22 06:35:53 ess-uvce kernel: NET: 33073 messages suppressed.
Oct 22 06:35:58 ess-uvce kernel: NET: 36642 messages suppressed.
Oct 22 06:36:03 ess-uvce kernel: NET: 28798 messages suppressed.
Oct 22 06:36:08 ess-uvce kernel: NET: 21928 messages suppressed.
Oct 22 06:36:13 ess-uvce kernel: NET: 25631 messages suppressed.
Oct 22 06:36:18 ess-uvce kernel: NET: 30442 messages suppressed.
Oct 22 06:36:23 ess-uvce kernel: NET: 30225 messages suppressed.
Oct 22 06:36:28 ess-uvce kernel: NET: 28005 messages suppressed.
Oct 22 06:36:33 ess-uvce kernel: NET: 21884 messages suppressed.
Oct 22 06:36:38 ess-uvce kernel: NET: 23300 messages suppressed.
Oct 22 06:36:43 ess-uvce kernel: NET: 30853 messages suppressed.
Oct 22 06:36:48 ess-uvce kernel: NET: 27821 messages suppressed.
Oct 22 06:36:53 ess-uvce kernel: NET: 29570 messages suppressed.
Oct 22 06:36:58 ess-uvce kernel: NET: 22651 messages suppressed.
Oct 22 06:37:03 ess-uvce kernel: NET: 28761 messages suppressed.
Oct 22 06:37:08 ess-uvce kernel: NET: 32997 messages suppressed.
Oct 22 06:37:13 ess-uvce kernel: NET: 31389 messages suppressed.
********

Kernel: NET: messages suppressed (I am sure it has been covered before)

[Frischknecht Peter]

I need to know WHAT MESSAGE WAS SUPPRESSED.

I am getting slammed.  My server will display anywhere from a few
hundred to 50K messages suppressed.

Previous posters have suggested that if I go early enough in my logs,
that I will find the original suppressed message. NOT TRUE.

I am desperate.  These messages are an indication of a larger problem,
but I am unable to diagnose what. My network is fairly small (650
nodes), and I have been receiving these messages time and again.
Sometimes every 3 hours, sometimes every 3 days.  

Network analizers (Ntop, iptraf) have been unable to identify the source
of the traffic.  If I run these utilities on the server, they freeze
(while a flood is going on).  If I run the utilities on a different
computer on a port of the switch, they don't see the traffic intended
for the server (obviously).  If I configure the switch for a "monitor"
port (one that sees all traffic) and plug a different computer on that
port, then that computer freezes too, along with the server.

The few times that we cought a machine WHILE it was generating the
traffic, we could not find any evidence of wrongdoing.  No viruses, no
trojan horses, no smoking gun.  The ONLY mechanism that stops the
traffic is blocking ARPs at the switch.  But I feel that ARP is another
symptom, not the actual problem (like an ICMP flood).

The switches used are 12x HP J4121A (Procurve 4000M) and one HP5308XL
(fiber cross-connect).

Once the Linux router gets slammed, it is a matter of time before it
freezes and dies.

ANY help would be appreciated.

Here is a sample:
****
[root@ess-uvce root]# grep "kernel: NET" /var/log/messages
Oct 21 15:34:00 ess-uvce kernel: NET: 205 messages suppressed.
Oct 21 15:34:05 ess-uvce kernel: NET: 33484 messages suppressed.
Oct 21 15:34:10 ess-uvce kernel: NET: 33264 messages suppressed.
Oct 21 15:34:15 ess-uvce kernel: NET: 31204 messages suppressed.
Oct 21 15:34:20 ess-uvce kernel: NET: 33229 messages suppressed.
Oct 21 15:34:25 ess-uvce kernel: NET: 30596 messages suppressed.
Oct 21 15:34:30 ess-uvce kernel: NET: 33175 messages suppressed.
Oct 21 15:34:35 ess-uvce kernel: NET: 31174 messages suppressed.
Oct 21 15:34:40 ess-uvce kernel: NET: 33076 messages suppressed.
Oct 21 15:34:45 ess-uvce kernel: NET: 30534 messages suppressed.
Oct 21 15:34:50 ess-uvce kernel: NET: 32551 messages suppressed.
Oct 21 15:34:55 ess-uvce kernel: NET: 31169 messages suppressed.
Oct 21 15:35:00 ess-uvce kernel: NET: 33317 messages suppressed.
Oct 21 15:35:05 ess-uvce kernel: NET: 31162 messages suppressed.
Oct 22 01:09:44 ess-uvce kernel: NET: 26196 messages suppressed.
Oct 22 06:35:33 ess-uvce kernel: NET: 35332 messages suppressed.
Oct 22 06:35:38 ess-uvce kernel: NET: 35040 messages suppressed.
Oct 22 06:35:43 ess-uvce kernel: NET: 27654 messages suppressed.
Oct 22 06:35:48 ess-uvce kernel: NET: 27208 messages suppressed.
Oct 22 06:35:53 ess-uvce kernel: NET: 33073 messages suppressed.
Oct 22 06:35:58 ess-uvce kernel: NET: 36642 messages suppressed.
Oct 22 06:36:03 ess-uvce kernel: NET: 28798 messages suppressed.
Oct 22 06:36:08 ess-uvce kernel: NET: 21928 messages suppressed.
Oct 22 06:36:13 ess-uvce kernel: NET: 25631 messages suppressed.
Oct 22 06:36:18 ess-uvce kernel: NET: 30442 messages suppressed.
Oct 22 06:36:23 ess-uvce kernel: NET: 30225 messages suppressed.
Oct 22 06:36:28 ess-uvce kernel: NET: 28005 messages suppressed.
Oct 22 06:36:33 ess-uvce kernel: NET: 21884 messages suppressed.
Oct 22 06:36:38 ess-uvce kernel: NET: 23300 messages suppressed.
Oct 22 06:36:43 ess-uvce kernel: NET: 30853 messages suppressed.
Oct 22 06:36:48 ess-uvce kernel: NET: 27821 messages suppressed.
Oct 22 06:36:53 ess-uvce kernel: NET: 29570 messages suppressed.
Oct 22 06:36:58 ess-uvce kernel: NET: 22651 messages suppressed.
Oct 22 06:37:03 ess-uvce kernel: NET: 28761 messages suppressed.
Oct 22 06:37:08 ess-uvce kernel: NET: 32997 messages suppressed.
Oct 22 06:37:13 ess-uvce kernel: NET: 31389 messages suppressed.
********

Re: Kernel: NET: messages suppressed (I am sure it has been covered before)

[Antony Stone]

On Thursday 23 October 2003 4:47 pm, Frischknecht Peter wrote:

> I am getting slammed.  My server will display anywhere from a few
> hundred to 50K messages suppressed.
>
> Network analizers (Ntop, iptraf) have been unable to identify the source
> of the traffic.  If I run these utilities on the server, they freeze
> (while a flood is going on).  If I run the utilities on a different
> computer on a port of the switch, they don't see the traffic intended
> for the server (obviously).  If I configure the switch for a "monitor"
> port (one that sees all traffic) and plug a different computer on that
> port, then that computer freezes too, along with the server.

Try connecting a hub between your switch and the server which is being 
affected, then plug a machine running a protocol analyser such as ethereal 
into the hub, without assigning a network-valid IP address to the analysis 
machine.   If you're worried about the analysis machine being affected by the 
flood of traffic, just plug it in for a couple of seconds and then unplug it, 
and then see what the analyser caught during that time.

If you've found some network attack which blows away the Linux network stack, 
causing the 'freezing', try using a machine running BSD (or maybe even 
Windows!?) for doing the analysis - they're unlikely to be vulnerable to the 
same sort of attack.

You say you have managed to identify some of the machines causing the traffic 
floods - what operating system/s do they run, and what happens if you plug 
the network protocol analyser into a hub connected to these machines?

Antony.

-- 

Normal people think "if it ain't broke, don't fix it".
Engineers think "if it ain't broke, it doesn't have enough features yet".

Re: Kernel: NET: messages suppressed (I am sure it has been covered before)

[Arnt Karlsen]

On Thu, 23 Oct 2003 17:03:57 +0100, 
Antony Stone <Antony@Soft-Solutions.co.uk> wrote in message 
<200310231603.h9NG3x702705@onyx.rockstone.co.uk>:
>
> Try connecting a hub between your switch and the server which is being
> affected, then plug a machine running a protocol analyser such as
> ethereal into the hub, without assigning a network-valid IP address to
> the analysis machine.   
>

..another option is set up a box as an ip-less sniff bridge.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.

Kernel: NET: messages suppressed (I am sure it has been covered before)

[Frischknecht Peter]

I appreciate the suggestions for using a network analizer...I will be
implementing them as soon as I get on-site.
In the mean time, it would be very helpful if I had an answer to the
first question:  
"What message is being suppressed?"

Again, thank you for any help you may give me.

Re: Kernel: NET: messages suppressed (I am sure it has been covered before)

[Philip Craig]

Frischknecht Peter wrote:
> I need to know WHAT MESSAGE WAS SUPPRESSED.
> 
> I am getting slammed.  My server will display anywhere from a few
> hundred to 50K messages suppressed.
> 
> Previous posters have suggested that if I go early enough in my logs,
> that I will find the original suppressed message. NOT TRUE.

You should have one successful log message for every log message
indicating the number of suppressed log messages.  Since your
/var/log/messages does not contain the successful log messages,
your syslogd must be configured to send them elsewhere.

Note that the number of suppressed log messages is always logged
at KERN_WARNING, but the actual message could be anything.  I
would suspect that the actual log messages are KERN_DEBUG, and
your syslogd is configured to ignore them

-- 
Philip Craig - philipc@snapgear.com - http://www.SnapGear.com
SnapGear - Custom Embedded Solutions and Security Appliances

Re: Kernel: NET: messages suppressed (I am sure it has been covered before)

[Peteris Krumins]

Hello Frischknecht,

Friday, October 24, 2003, 5:35:05 AM, you wrote:

FP> I appreciate the suggestions for using a network analizer...I will be
FP> implementing them as soon as I get on-site.
FP> In the mean time, it would be very helpful if I had an answer to the
FP> first question:  
FP> "What message is being suppressed?"

<N> Messages suppressed, it means the messages are repeating.
So not to print them N times, a single message is printed telling
that the last N messages were the same.


P.Krumins

Kernel: NET: messages suppressed (I am sure it has been covered before)

[Gaby Schilders]

As has been pointed out before in one of the replies to your question:
please take a very close look at your logging settings. It is quite
likely that the original message is logged at a level that you don't
catch in your syslog, you would then _only_ see these "Message
suppressed" items since they have a default log value of 'warn' I
believe. The missing message may have gone to the console only but
that seems unlikely.

However, if all else fails, there is a mention of such a case in the
netfilter mailing list, january 2001:
http://lists.netfilter.org/pipermail/netfilter/2001-January/006513.html
plus the following thread that come to two conclusions that you may be
able to use:
- Use the drop-table patch from pom to centralize all drops. If this is
an issue of frames dropped by netfilter you may be able to at least
regain a sane environment to work in.
- If the frames are being killed due to them being multicast (and hence
untrackable), drop those seperatly.

Gaby Schilders
IBFD network admin

-----Original Message-----
From: Frischknecht Peter [mailto:peter@empoweringsolutions.com]
Sent: donderdag 23 oktober 2003 16:34
To: netfilter@lists.netfilter.org
Subject: Kernel: NET: messages suppressed (I am sure it has been covered
before)


I need to know WHAT MESSAGE WAS SUPPRESSED.

I am getting slammed.  My server will display anywhere from a few
hundred to 50K messages suppressed.

Previous posters have suggested that if I go early enough in my logs,
that I will find the original suppressed message.
NOT TRUE.

I am desperate.  These messages are an indication of a larger problem,
but I am unable to diagnose what.
My network is fairly small (650 nodes), and I have been receiving these
messages time and again.  Sometimes every 3 hours, sometimes every 3
days.  

Network analizers (Ntop, iptraf) have been unable to identify the source
of the traffic.  If I run these utilities on the server, they freeze
(while a flood is going on).  If I run the utilities on a different
computer on a port of the switch, they don't see the traffic intended
for the server (obviously).  If I configure the switch for a "monitor"
port (one that sees all traffic) and plug a different computer on that
port, then that computer freezes too, along with the server.

The few times that we cought a machine WHILE it was generating the
traffic, we could not find any evidence of wrongdoing.  No viruses, no
trojan horses, no smoking gun.  The ONLY mechanism that stops the
traffic is blocking ARPs at the switch.  But I feel that ARP is another
symptom, not the actual problem (like an ICMP flood).

The switches used are 12x HP J4121A (Procurve 4000M) and one HP5308XL
(fiber cross-connect).

Once the Linux router gets slammed, it is a matter of time before it
freezes and dies.

ANY help would be appreciated.

Here is a sample:
****
[root@ess-uvce root]# grep "kernel: NET" /var/log/messages;
Oct 21 15:34:00 ess-uvce kernel: NET: 205 messages suppressed.
Oct 21 15:34:05 ess-uvce kernel: NET: 33484 messages suppressed.
Oct 21 15:34:10 ess-uvce kernel: NET: 33264 messages suppressed.
Oct 21 15:34:15 ess-uvce kernel: NET: 31204 messages suppressed.
Oct 21 15:34:20 ess-uvce kernel: NET: 33229 messages suppressed.
Oct 21 15:34:25 ess-uvce kernel: NET: 30596 messages suppressed.
Oct 21 15:34:30 ess-uvce kernel: NET: 33175 messages suppressed.
Oct 21 15:34:35 ess-uvce kernel: NET: 31174 messages suppressed.
Oct 21 15:34:40 ess-uvce kernel: NET: 33076 messages suppressed.
Oct 21 15:34:45 ess-uvce kernel: NET: 30534 messages suppressed.
Oct 21 15:34:50 ess-uvce kernel: NET: 32551 messages suppressed.
Oct 21 15:34:55 ess-uvce kernel: NET: 31169 messages suppressed.
Oct 21 15:35:00 ess-uvce kernel: NET: 33317 messages suppressed.
Oct 21 15:35:05 ess-uvce kernel: NET: 31162 messages suppressed.
Oct 22 01:09:44 ess-uvce kernel: NET: 26196 messages suppressed.
Oct 22 06:35:33 ess-uvce kernel: NET: 35332 messages suppressed.
Oct 22 06:35:38 ess-uvce kernel: NET: 35040 messages suppressed.
Oct 22 06:35:43 ess-uvce kernel: NET: 27654 messages suppressed.
Oct 22 06:35:48 ess-uvce kernel: NET: 27208 messages suppressed.
Oct 22 06:35:53 ess-uvce kernel: NET: 33073 messages suppressed.
Oct 22 06:35:58 ess-uvce kernel: NET: 36642 messages suppressed.
Oct 22 06:36:03 ess-uvce kernel: NET: 28798 messages suppressed.
Oct 22 06:36:08 ess-uvce kernel: NET: 21928 messages suppressed.
Oct 22 06:36:13 ess-uvce kernel: NET: 25631 messages suppressed.
Oct 22 06:36:18 ess-uvce kernel: NET: 30442 messages suppressed.
Oct 22 06:36:23 ess-uvce kernel: NET: 30225 messages suppressed.
Oct 22 06:36:28 ess-uvce kernel: NET: 28005 messages suppressed.
Oct 22 06:36:33 ess-uvce kernel: NET: 21884 messages suppressed.
Oct 22 06:36:38 ess-uvce kernel: NET: 23300 messages suppressed.
Oct 22 06:36:43 ess-uvce kernel: NET: 30853 messages suppressed.
Oct 22 06:36:48 ess-uvce kernel: NET: 27821 messages suppressed.
Oct 22 06:36:53 ess-uvce kernel: NET: 29570 messages suppressed.
Oct 22 06:36:58 ess-uvce kernel: NET: 22651 messages suppressed.
Oct 22 06:37:03 ess-uvce kernel: NET: 28761 messages suppressed.
Oct 22 06:37:08 ess-uvce kernel: NET: 32997 messages suppressed.
Oct 22 06:37:13 ess-uvce kernel: NET: 31389 messages suppressed.
Oct 22 06:37:18 ess-uvce kernel: NET: 24475 messages suppressed.
Oct 22 06:37:23 ess-uvce kernel: NET: 30712 messages suppressed.
Oct 22 06:37:28 ess-uvce kernel: NET: 34532 messages suppressed.
Oct 22 06:37:33 ess-uvce kernel: NET: 29573 messages suppressed.
Oct 22 06:37:38 ess-uvce kernel: NET: 25571 messages suppressed.
Oct 22 06:37:43 ess-uvce kernel: NET: 26330 messages suppressed.
Oct 22 06:37:48 ess-uvce kernel: NET: 30778 messages suppressed.
********