Hello. We have a firewall here (Checkpoint FW 1), installed on a RH 6.2 Every week or so, the FW logs this error : dst cache overflow and the routing stops. Is changing the value of /proc/sys/net/ipv
lo is up and running.... Now, I don't know if some rules by default of fw-1 make it looks like lo is down ... Yann Dupont. -- On Mon, Jul 16, 2001 at 01:59:56PM +0200, Yann Dupont wrote: Every week
lo is up and running.... so ping 127.0.0.1 works? Now, I don't know if some rules by default of fw-1 make it looks like lo is down ... I'm not sure I follow here, are you saying fw-1 makes it look li
yes. Sorry for my poor english ... fw-1 is a module that sits beetwen the IP layer & the interface (Well. I think it perform like this. Mayne I'm totally wrong here) So even if I can ping 127.0.0.1,
Sorry for my poor english ... Mine is probably worse. fw-1 is a module that sits beetwen the IP layer & the interface (Well. I think it perform like this. Mayne I'm totally wrong here) I assume it wo
You can increase the /proc/sys/net/ipv4/route/gc_thresh sysctl trying to work around it, but likely it's a bug in the FW-1 kernel module. I would talk to Checkpoint. -Andi
He might be having problems with route table not getting enough nh entries because of small neigh tables. obviously FW1 is doing something weird: Yann, try to increment the sizes of the arp tables, e
Thanks to all for all the advices. I'd like to understand the meaning of gc_thresh1,2,3 ... gc_thresh is something like garbage collection threshold ? So what's the meaning of 1,2,3 ? For the moment,
Hello. We have a firewall here (Checkpoint FW 1), installed on a RH 6.2 Every week or so, the FW logs this error : dst cache overflow and the routing stops. Is changing the value of /proc/sys/net/ipv
Hello... lo is up and running.... Now, I don't know if some rules by default of fw-1 make it looks like lo is down ... Yann Dupont. -- On Mon, Jul 16, 2001 at 01:59:56PM +0200, Yann Dupont wrote: Eve
lo is up and running.... so ping 127.0.0.1 works? Now, I don't know if some rules by default of fw-1 make it looks like lo is down ... I'm not sure I follow here, are you saying fw-1 makes it look li
yes. Sorry for my poor english ... fw-1 is a module that sits beetwen the IP layer & the interface (Well. I think it perform like this. Mayne I'm totally wrong here) So even if I can ping 127.0.0.1,
Sorry for my poor english ... Mine is probably worse. fw-1 is a module that sits beetwen the IP layer & the interface (Well. I think it perform like this. Mayne I'm totally wrong here) I assume it wo
You can increase the /proc/sys/net/ipv4/route/gc_thresh sysctl trying to work around it, but likely it's a bug in the FW-1 kernel module. I would talk to Checkpoint. -Andi
He might be having problems with route table not getting enough nh entries because of small neigh tables. obviously FW1 is doing something weird: Yann, try to increment the sizes of the arp tables, e
Thanks to all for all the advices. I'd like to understand the meaning of gc_thresh1,2,3 ... gc_thresh is something like garbage collection threshold ? So what's the meaning of 1,2,3 ? For the moment,