similar to: filter problem with htb + sfq

hello list (and martin) ;x i have now composed my final(?) policy routing design. the goals i had when beginning with this, for you that have not follow mine and martins thread, was to 1) only let 192.168.1/24 to see all routes, 2) not route between defined networks, except to and from 192.168.1/24 and 3) not defined networks should only be able to reach 192.168.1/24. this might sound simple.

<div style='background-color:'><DIV><FONT size=2> Hi</P> This is a sample that has possible pre-echo problems (around 6 seconds)</P> with -q 6 and higher bitrates too. I posted it to 2 sites.. hope</P> you can check it:</P> <A

Hello all, Tomas Bonnedahl and I recently corresponded about a rather odd behaviour with routes in ancillary routing tables. We both receive a "Network is unreachable" error when we try to add gatewayed routes to ancillary tables and the main routing table does not contain an entry for the gateway IP. It seems that unless a route to the gateway IP exists in the main routing table, I

Apparently any (?) call of the form cut(date,"weeks") where the date *begins the week*, gives the error Error in 1:(1 + max(which(breaks < maxx))) : result would be too long a vector In addition: Warning message: In max(which(breaks < maxx)) : no non-missing arguments to max; returning -Inf To my surprise, this was first reported as a problem in 2006 (!) (version 2.3.1

as you can see in the topic there is a problem with iproute2. ''ip rule show'' returns RTNETLINK answers: Invalid argument Dump terminated while ''ip route show'' for example returns the right output, what can possible be the problem here? the kernel is 2.4.18 and im not really sure with the version of iproute2. thanks for your help, tomas