netdev - MULTIPLE_TABLES and IP_ADVANCED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdXZpxnrU=FfFcf3sgX+Ym3RCVLA7dn_8mgUBpby18uDzw@mail.gmail.com>
Date:	Sun, 22 Nov 2015 11:03:18 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: MULTIPLE_TABLES and IP_ADVANCED_ROUTER

        Hi,

Is there a reason why IP_MULTIPLE_TABLES and IP_MROUTE_MULTIPLE_TABLES
depend on IP_ADVANCED_ROUTER, while their IPV6 counterparts don't?

net/ipv4/Kconfig:

    config IP_MULTIPLE_TABLES
            bool "IP: policy routing"
            depends on IP_ADVANCED_ROUTER
            select FIB_RULES

    config IP_MROUTE_MULTIPLE_TABLES
            bool "IP: multicast policy routing"
            depends on IP_MROUTE && IP_ADVANCED_ROUTER
            select FIB_RULES


net/ipv6/Kconfig:

    config IPV6_MULTIPLE_TABLES
            bool "IPv6: Multiple Routing Tables"
            select FIB_RULES

    config IPV6_MROUTE_MULTIPLE_TABLES
            bool "IPv6: multicast policy routing"
            depends on IPV6_MROUTE
            select FIB_RULES

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html