diff options
author | Joel Stanley <joel@jms.id.au> | 2021-07-12 07:21:15 +0300 |
---|---|---|
committer | Joel Stanley <joel@jms.id.au> | 2021-07-13 02:40:28 +0300 |
commit | ace36475bb13bbafae0a9dda128b943ff216832c (patch) | |
tree | eb96ac94eb9277c8833e1004b059867e188bd3aa /meta-hpe/conf/layer.conf | |
parent | cb35b2b8b5d71a08e951848ceb4984129bcfac93 (diff) | |
download | openbmc-ace36475bb13bbafae0a9dda128b943ff216832c.tar.xz |
linux-aspeed: Disable IPV6 SIT device
No one is using this device on OpenBMC systems, and there is no
code to manage it in phosphor-networkd as of March 2021:
> [...] if you don't add IPv6 addresses to the sit interface
> it doesn't do anything. The defacto way to do that on an interface in
> OpenBMC is to have it managed by phosphor-networkd. On top of this, to
> support sit you would need a way to configure the local / remote IPv4
> addresses used to back it. You can configure the linux kernel to build
> sit functionality but not create sit devices by default (I don't know
> how they haven't changed this yet in default kconfigs...) and it will
> still let you make them on the fly.
Facebook and Google systems force this option off already:
meta-facebook/meta-tiogapass/recipes-kernel/linux/linux-aspeed/tiogapass.cfg:CONFIG_IPV6_SIT=n
meta-google/recipes-kernel/linux/files/gbmc.cfg:CONFIG_IPV6_SIT=n
Change-Id: I9df02c761e82eeb2cca562bf68b9b755bc6feeb9
Signed-off-by: Joel Stanley <joel@jms.id.au>
Diffstat (limited to 'meta-hpe/conf/layer.conf')
0 files changed, 0 insertions, 0 deletions