> ok, just solved my problem. sorry, i was mistaking. i found some bugfixes, thats right, but they didnt fix this bug BUT brought several other bugs into my kernel. i still have the problem that usage of firewall marks as routing key doesnt work. kernel: 2.4.20-22 (all tried) iptables: 1.2.9 iproute: ss010824 in addition with kernels 2.4.23 and 2.4.24 routing table selection doesnt seem to work at all for me. if you have ANY hints, i would be really grateful. maybe you can name me a configuration of kernel, kernelpatches, iptables and iproute with which advanced routing, firewalling and QoS are working fine. to be more precise, i need a full functional netfilter with the usual matching rules and targets, esp. marks and masquerading, advanced routing that allows routing selection upon netfilter marks and qos with the htb queueing disciplin. thank you.
