Hello!
> Only tos set by input chain is taken into account,
> when selecting route. tos mangled by output chain can affect
> only queuing.
>
> If you want to route smartly packets, originated by your host,
> you have only two choices:
>
> 1. Fiddle with IP_TOS in applications.
> 2. Move all this smartness to router.
> The last variant is the only reasonable, because host must have
> routing table consisting only of one default route.
Another one: Introduce a "local input" fw chain.
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
"Disc space, the final frontier!"
-
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
- Re: route based on source address and/or... tzanger
