Hello,
> It is too hard to fix for 2.2 release. The rule therefore is: TOS
> rewriting is only reliably supported for packet forwarding.
>
> 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?
Have a nice fortnight
--
Martin `MJ' Mares <[EMAIL PROTECTED]> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
"System going down at 1:45 for disk crashing."
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
- route based on source address and/or destination port tzanger
- Re: route based on source address and/or destination... Andi Kleen
- Re: route based on source address and/or destina... tzanger
- Re: route based on source address and/or des... Andi Kleen
- Re: route based on source address and/or... Martin Mares
- Re: route based on source address a... kuznet
- Re: route based on source addre... Martin Mares
- Re: route based on source a... kuznet
- Re: route based on source a... Andi Kleen
- Re: route based on source address and/or des... Alexey Kuznetsov
- Re: route based on source address and/or... Martin Mares
- Re: route based on source address a... kuznet
- Re: route based on source addre... Martin Mares
- Re: route based on source address a... Andi Kleen
