Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#6271 - Consider enabling the "Advanced Router" features on the packaged kernels
Attached to Project:
Arch Linux
Opened by Apollon Oikonomopoulos (apoikos) - Wednesday, 24 January 2007, 16:56 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 24 January 2007, 20:56 GMT
Opened by Apollon Oikonomopoulos (apoikos) - Wednesday, 24 January 2007, 16:56 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 24 January 2007, 20:56 GMT
|
DetailsAfter having worked quite a bit with Linux as a network router OS, I have come to appreciating the advanced routing features the linux kernel has to offer. However, today I found out that these features are disabled in the stock and -beyond kernels, thus preventing the average user from using the "advanced" features of policy routing iproute2 has to offer, without recompiling the kernel. Since these features do not break anything and do not incur any kernel overhead (at least AFAIK), would it be perhaps possible to enable them in the precompiled kernel packages? The respective kernel-configuration entries I'm talking about are:
IP:Advanced Router IP:Policy Routing IP:Use netfilter MARK value as routing key |
This task depends upon
i cannot find in the kernel could you tell me which option matche this?
Prompt: IP: use netfilter MARK value as routing key
Defined at net/ipv4/Kconfig:107
Depends on: NET && INET && IP_MULTIPLE_TABLES && NETFILTER
Location:
-> Networking
-> Networking support (NET [=y])
-> Networking options
-> TCP/IP networking (INET [=y])
-> IP: policy routing (IP_MULTIPLE_TABLES [=y])
Thanks for taking this into account :-)
As for the Firewall Mark as Routing Key stuff, it seems support for it has been hardcoded in net/ipv4/route.c on 2.6.20, so there's no need to bother with that anymore.
Thanks once again!