Hello!
> > It is too hard to fix for 2.2 release. The rule therefore is: TOS
> > rewriting is only reliably supported for packet forwarding.
... and only by input firewall chain.
> > I'll note it, maybe it is possible to fix it in 2.3, but it is unlikely.
>
> What about implementing routing by tag set in the firewall code as we use
> for flow classification?
It will not help with locally originated packets. Actually,
for locally originated packets firewall rules are completely useless:
to apply them we need a packet, to prepare packet we need to know route:
egg and chicken problem 8)
Generally tagging is good idea, but tos tags are better for now,
because local packets still may be driven by standard api (setsockopt(IP_TOS)).
Until today (and in the closest future) tos is enough to be used as tag.
Diffserv will change it, but it is unlikely to be soon.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
