Skip to content

[radvd] No longer build from source; Install vanilla Debian package once again#5242

Merged
jleveque merged 2 commits intosonic-net:masterfrom
jleveque:vanilla_radvd
Sep 1, 2020
Merged

[radvd] No longer build from source; Install vanilla Debian package once again#5242
jleveque merged 2 commits intosonic-net:masterfrom
jleveque:vanilla_radvd

Conversation

@jleveque
Copy link
Contributor

@jleveque jleveque commented Aug 24, 2020

- Why I did it

Resolves #3161

  • In PR [radvd] Build radvd from source; Patch so as not to treat out-of-range MTU as an error #2795, we started building radvd from source and patching it to prevent it from erroring out when advertising an MTU of 9100 which was greater than the MTU size configured on the bridge interface (1500), which was due to a limitation in the 4.9 Linux kernel.
  • Master branch is now using Linux kernel 4.19. As of 4.18, the kernel supports setting a bridge MTU to a value > 1500.
  • PR [vlanmgr] Support Jumbo Frame By Default sonic-swss#1393 modified vlanmgrd to take advantage of this and now configures the MTU of bridge interfaces in SONiC to the proper size of 9100. Therefore, we no longer need to patch radvd. Since we no longer need to patch radvd, we no longer need to build it from source, so we can save build time by going back to simply installing the vanilla radvd Debian package in the router-advertiser container.

- How I did it

  • Remove radvd Makefile and patch, change docker-router-advertiser Dockerfile template to simply install the vanilla radvd package using apt-get.

- How to verify it

  • Ensure that radvd starts and runs in the container and that it does not emit log messages like the following:
ERR radv#radvd[38]: AdvLinkMTU for Vlan1000 (9100) must be zero or between 1280 and 1500

- Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006

tahmed-dev
tahmed-dev previously approved these changes Aug 24, 2020
prsunny
prsunny previously approved these changes Aug 24, 2020
Copy link
Contributor

@prsunny prsunny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jleveque jleveque dismissed stale reviews from prsunny and tahmed-dev via 8e26934 August 25, 2020 01:39
@jleveque
Copy link
Contributor Author

Retest vsimage please

1 similar comment
@jleveque
Copy link
Contributor Author

Retest vsimage please

@jleveque jleveque merged commit fb8f09a into sonic-net:master Sep 1, 2020
@jleveque jleveque deleted the vanilla_radvd branch September 1, 2020 20:53
santhosh-kt pushed a commit to santhosh-kt/sonic-buildimage that referenced this pull request Feb 25, 2021
…nce again (sonic-net#5242)

Remove radvd Makefile and patch, change docker-router-advertiser Dockerfile template to simply install the vanilla radvd package using apt-get.

- In PR sonic-net#2795, we started building radvd from source and patching it to prevent it from erroring out when advertising an MTU of 9100 which was greater than the MTU size configured on the bridge interface (1500), which was due to a limitation in the 4.9 Linux kernel.
- Master branch is now using Linux kernel 4.19. As of 4.18, the kernel supports setting a bridge MTU to a value > 1500.
- PR sonic-net/sonic-swss#1393 modified vlanmgrd to take advantage of this and now configures the MTU of bridge interfaces in SONiC to the proper size of 9100. Therefore, we no longer need to patch radvd. Since we no longer need to patch radvd, we no longer need to build it from source, so we can save build time by going back to simply installing the vanilla radvd Debian package in the router-advertiser container.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

radvd out of range MTU error

4 participants