Re: [leaf-user] syslog message: firewall kernel: ip_conntrack: table full, dropping packet.

Hello Eric, Thanks for you reply. After increasing the ip_conntrack_max value to 4096 I did find a curious entry in my messages log file : firewall kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) This happened twice about a day ago. According to the bucu-conntrack guide the

Re: [leaf-user] syslog message: firewall kernel: ip_conntrack: table full, dropping packet.

Hello Chera, Hello Eric, Thanks for you reply. After increasing the ip_conntrack_max value to 4096 I did find a curious entry in my messages log file : firewall kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0) This happened twice about a day ago. I don't know what this

[leaf-user] syslog message: firewall kernel: ip_conntrack: table full, dropping packet.

Hello List, I have noticed that when running a p2p client behind my Bering firewall my syslog gets flooded with the message: |firewall kernel: ip_conntrack: table full, dropping packet.| || Allmost all entries in /proc/net/ip_conntrack pointed to the internal machine running the client. |I

Re: [leaf-user] syslog message: firewall kernel: ip_conntrack: table full, dropping packet.

Hello Chera, There is some information about this setting in the following Bering-uClibc guide and the links section in this guide. http://leaf.sourceforge.net/doc/guide/bucu-conntrack.html Eric Hello List, I have noticed that when running a p2p client behind my Bering firewall my syslog