cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1493
Views
0
Helpful
1
Replies

RV220W - Frag of Proto 17

aebleaeble
Level 1
Level 1

Hello

My RV220W (Firmware 1.0.2.1 Beta) is spamming my syslog with this error:

10.0.0.1 08/13/11 09:02:27 08/13/11 11:02:56  kernel Warning  rv220w "KERNEL [Kernel] printk: 2 messages suppressed."

10.0.0.1 08/13/11 09:02:27 08/13/11 11:02:56  kernel Error  rv220w "KERNEL [Kernel] ip_conntrack_in: Frag of proto 17 (hook=0)"

10.0.0.1 08/13/11 09:02:22 08/13/11 11:02:51  kernel Warning  rv220w "KERNEL [Kernel] printk: 1 messages suppressed."

10.0.0.1 08/13/11 09:02:22 08/13/11 11:02:51  kernel Warning  rv220w "KERNEL [Kernel] printk: 2 messages suppressed."

10.0.0.1 08/13/11 09:02:22 08/13/11 11:02:51  kernel Error  rv220w "KERNEL [Kernel] ip_conntrack_in: Frag of proto 17 (hook=0)"

10.0.0.1 08/13/11 09:02:22 08/13/11 11:02:51  kernel Error  rv220w "KERNEL [Kernel] ip_conntrack_in: Frag of proto 17 (hook=0)"

It comes in series of 1 or up to 10 a second, with a random interval of ~1minute or more. Can some one tell me what this is, so I can eliminate it? Google hasn't been helpful.

I installed the beta firmware yesterday, although I have seen this particular error before. Unfortunately I couldn't import my settings from the previous firmware (1.0.1.0), so I had to redo everything manually.

The firmware was given to me, because of the hair-pinning problem (NAT loopback or whatever you wanna call it), which is resolved in this beta release. But the above kernel error must be something in my setup, since it is consistent with the current and the previous firmware.

At the moment I have 1 server attached via cable, a client computer also via cable and an Android phone via wireless.

Any help is appreciated, and if you need further information, just let me know.

Thanks in advance,

Henrik

1 Reply 1

aebleaeble
Level 1
Level 1

After searching some more on google, I figured out what it means.

Proto 17 is the UDP protocol, and "Frag" is short for fragment.

Once I disabled the "Block Fragmented Packets:" function in the firewall, the errors stopped. Why it lists a feature as an error in the logs, is still a mystery for me.. =)

Have a nice weekend all