search for: gc_elasticity

Hello, I hope i wont make it too complicated and sorry for my englihs... The company has multiple connections to the internet ADSL + CABLE + XDSL... and i only want to use two for load balancing for now. I have read the HOWTO and i got it up and working it works great but i still have a few questions if anyone could help! the setup is: ADSL on ETH0 and CABLE on ETH1 When i load balance on

...kernel: dst cache overflow) and crash of a firewall under Linux 2.6.17 and the route patch from Julian Anastasov. With rtstat I see that the route cache size increases regularly without never decreasing. I have this parameters: fw:/proc/sys/net/ipv4/route# grep . * error_burst:1250 error_cost:250 gc_elasticity:15 gc_interval:60 gc_min_interval:0 gc_min_interval_ms:500 gc_thresh:4096 gc_timeout:300 max_delay:10 max_size:65536 min_adv_mss:256 min_delay:2 min_pmtu:552 mtu_expires:600 redirect_load:5 redirect_number:9 redirect_silence:5120 secret_interval:600 I can increase the maximum size of the cache, bu...

...0=eth1 IP0=10.0.1.1 IF1=eth0 IP1=xxx.xxx.xxx.7 P1_NET=xxx.xxx.xxx.0/24 P1=xxx.xxx.xxx.1 IF2=eth2 IP2=yyy.yyy.yyy.21 P2_NET=yyy.yyy.yyy.0/24 P2=yyy.yyy.yyy.1 echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter echo 3 > /proc/sys/net/ipv4/route/gc_elasticity echo 1 > /proc/sys/net/ipv4/route/gc_interval echo 0 > /proc/sys/net/ipv4/route/gc_timeout ip route flush cache ip route flush all ip route flush table modem0 ip route flush table modem1 ip rule add from $IP1 lookup modem0 ip rule add from $IP2 lookup modem1 ip route add $P1_NET dev $IF1 s...

...an0 weight 1 nexthop via GW_PUB2 dev wan0 weight 1 ROUTING parameters configuration: # grep . /proc/sys/net/ipv4/route/* /proc/sys/net/ipv4/route/error_burst:5000 /proc/sys/net/ipv4/route/error_cost:1000 grep: /proc/sys/net/ipv4/route/flush: Operación no permitida /proc/sys/net/ipv4/route/gc_elasticity:8 /proc/sys/net/ipv4/route/gc_interval:60 /proc/sys/net/ipv4/route/gc_min_interval:0 /proc/sys/net/ipv4/route/gc_min_interval_ms:500 /proc/sys/net/ipv4/route/gc_thresh:32768 /proc/sys/net/ipv4/route/gc_timeout:300 /proc/sys/net/ipv4/route/max_delay:10 /proc/sys/net/ipv4/route/max_size:524288 /proc/...

...ser drops the connection. At which time if the connection is re-established by the user the linux router then could use a different interface but it should only use the interface that the connection was established under. I have made some progress playing around with the gc_interval gc_timeout and gc_elasticity. I also started looking at the code behind the routing and gc logic in the route.c file in the linux kernel source. It appears that the gc does not compare which routes to keep or which routes to drop. It just does sort of a first come first out sweep. Also it is my assumption from the code and...

Hi, I have a P4 @ 3Ghz router running Debian. It shapes traffic ( about 500-600 classes ), about 1000 iptables rules, and it does BGP too, so i get about 1300+ routes in the routing table. The problem is the load is too high on this system. I found a solution to my problem, turning off the route cache, but i dont know how to implement it, I was wondering if anyone found a way to disable the

...0=eth1 IP0=10.0.1.1 IF1=eth0 IP1=xxx.xxx.xxx.7 P1_NET=xxx.xxx.xxx.0/24 P1=xxx.xxx.xxx.1 IF2=eth2 IP2=yyy.yyy.yyy.21 P2_NET=yyy.yyy.yyy.0/24 P2=yyy.yyy.yyy.1 echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter echo 3 > /proc/sys/net/ipv4/route/gc_elasticity echo 1 > /proc/sys/net/ipv4/route/gc_interval echo 0 > /proc/sys/net/ipv4/route/gc_timeout ip route flush cache ip route flush all ip route flush table modem0 ip route flush table modem1 ip rule add from $IP1 lookup modem0 ip rule add from $IP2 lookup modem1 ip route add $P1_NET dev $IF1 s...

...0=eth1 IP0=10.0.1.1 IF1=eth0 IP1=xxx.xxx.xxx.7 P1_NET=xxx.xxx.xxx.0/24 P1=xxx.xxx.xxx.1 IF2=eth2 IP2=yyy.yyy.yyy.21 P2_NET=yyy.yyy.yyy.0/24 P2=yyy.yyy.yyy.1 echo 0 > /proc/sys/net/ipv4/conf/eth0/rp_filter echo 0 > /proc/sys/net/ipv4/conf/eth2/rp_filter echo 3 > /proc/sys/net/ipv4/route/gc_elasticity echo 1 > /proc/sys/net/ipv4/route/gc_interval echo 0 > /proc/sys/net/ipv4/route/gc_timeout ip route flush cache ip route flush all ip route flush table modem0 ip route flush table modem1 ip rule add from $IP1 lookup modem0 ip rule add from $IP2 lookup modem1 ip route add $P1_NET dev $IF1 s...

Configuration: (2) Dual Core Opterons 8GB RAM Apache used to balance 40 mongrel instances We receive Application 500 Errors. Nothing suspect appears in the log, so we are at a lost as to what to do next. Any advice would be welcome and/or an explanation of what types of things cause Application 500 Errors in mongrel. Thanks! - Jared Brown -------------- next part -------------- An HTML

..._time = 60 net.ipv4.neigh.default.gc_thresh3 = 1024 net.ipv4.neigh.default.gc_thresh2 = 512 net.ipv4.neigh.default.gc_thresh1 = 128 net.ipv4.neigh.default.gc_interval = 30 net.ipv4.neigh.default.gc_stale_time = 60 net.ipv4.inet_peer_gc_maxtime = 120 net.ipv4.inet_peer_gc_mintime = 10 net.ipv4.route.gc_elasticity = 1 net.ipv4.route.gc_interval = 1 net.ipv4.route.gc_timeout = 0 net.ipv4.route.gc_min_interval = 0 net.ipv4.route.gc_thresh = 2048 The tcpdump traffic goes like this: From the gateway: 19:08:37.404963 praia1.praiacamboriu.com.br.ftp-data > 141.porttal.com.br.1412: . 11025485:11026945(1460) ac...

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=40 laforge@netfilter.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From laforge@netfilter.org 2003-02-03 16:49 ------- We haven't seen this

The LARTC howto correctly describes load balancing and split access for traffic from a machine with multiple ISP connections (http://www.lartc.org/lartc.html#LARTC.RPDB.MULTIPLE-LINKS) -- *provided* the traffic originates from the machine itself (i.e. traffic regularly handled by the INPUT and OUTPUT chains of iptables). When forwarding traffic from an attached local network, the following