sysctl.conf: set rp_filter=0 |
||||
Issue descriptioncame across this tidbit: https://lwn.net/Articles/578621/ basically the Linux network maintainer points out that rp_filter makes no sense on leaf devices and just adds overhead. since CrOS is never in a routing position (or at least one where this setting would matter, e.g. routing between VMs/containers), we should turn this off. need to double check with jetstream & lakitu to see if they want to turn it back on for their boards.
,
Jun 17 2016
i assumed we just copied it from Gentoo which has been setting it this way for a while (longer than CrOS has existed). the history of the file shows that much as well. if there's any bugs/docs to link to, that'd be great.
,
Jun 17 2016
mike - thanks for the heads up! I'm inclined to believe jetstream will want rp_filter on for both whirlwind and arkham builds. Gale is still using it's own config (but I'll get to that soon). But I'm not the TL here and don't understand the guts of networking stack well enough. Adding some folks who do.
,
Jun 17 2016
Note that rp_filter is actively manipulated by shill during the connection and portal detection process to enable / disable simultaneous probing using multiple default routes.
,
May 24 2017
So should this bug be closed WontFix?
,
May 24 2017
Grant is correct that Jetstream devices does still want to use rp_filter. I would either support closing as WontFix or separating it into a config which does not apply to Jetstream devices.
,
Jun 1 2017
OK, let's close it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by pstew@chromium.org
, Jun 17 2016