BBRv2 installation issues

[Mahdi]

Hi all,

After BBRv2 installation on my desktop computer, there are some alias interfaces such as sit0 and erspan0.

 

Could you please tell me how can I remove them all?

Cheers

Mahdi

[Neal Cardwell]

Just to understand the scenario,  what set of steps did you  use to build the kernel you booted that produced the unwanted interfaces?

To disable these interfaces, I think the technique will depend on which Linux distribution you use. You can do a web search to find the instructions for your Linux distribution, e.g.:

  https://www.google.com/search?q=how%20to%20remove%20linux%20sit0%20interface

For example, that shows some suggestions for removing the sit0 interface on Ubuntu:

  https://askubuntu.com/questions/236059/how-to-remove-the-sit0-network-interface

For context, for a personal desktop or laptop, you may not want to use the .config file generated from the gce-install.sh build script in the v2alpha branch, since that .config is only targeting a bare minimum of kernel features needed to boot a VM or barebones x86 machine with few physical hardware devices.

best,

neal

--
You received this message because you are subscribed to the Google Groups "BBR Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bbr-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bbr-dev/3bfc4d54-9958-4a04-907b-5ebbd5427257n%40googlegroups.com.

[Mahdi]

Thanks Neal,

I want to install BBRv2 on my ubuntu VM. When I compiled the kernel I missed the NAT virtual network interfaces (no Internet connection anymore).

I thought maybe it is because of IPv6 tunneling and those unwanted interfaces such as sit0.

It was not easy to remove sit0 by the typical ubuntu commands because the IPv6 module was built-in.

I commented on IPv6 in the file `config.gce` and then compiled the kernel. Now there is not any IPv6 interface anymore but I cannot see the NAT interface too.

The command lspci shows that the NAT interface is connected. So it seems that this is a kernel problem, not VirtualBox. 

Best,

Mahdi 

[Neal Cardwell]

For the last guest OS that you were able to boot inside, VirtualBox, can you please post the networking driver that was used, e.g. perhaps from:

  ethtool -i ${DEVICE_NAME}

We can try to make sure that driver is enabled in the BBRv2 default .config file.

neal

To view this discussion on the web visit https://groups.google.com/d/msgid/bbr-dev/c0b4cecc-b6a3-417f-b483-ee25542b0f6fn%40googlegroups.com.

[Mahdi]

[Neal Cardwell]

Hi Mahdi,

Thanks for the details. Looks like the working guest OS is using the e1000 driver. I have added that driver to the v2alpha branch default .config, for ease of testing in this kind of environment. Can you please refetch, rebuild, and reboot, and see if that fixes the issue?

thanks,

neal

ps: here is the only change in the v2alpha-2021-01-20 release:

$ git diff-tree -p -r v2alpha-2021-01-15 v2alpha-2021-01-20
diff --git a/config.gce b/config.gce
index 88138ef5c6fb..1538acf6818b 100644
--- a/config.gce
+++ b/config.gce
@@ -1700,7 +1700,7 @@ CONFIG_NET_VENDOR_HP=y
 # CONFIG_HP100 is not set
 CONFIG_NET_VENDOR_INTEL=y
 # CONFIG_E100 is not set
-# CONFIG_E1000 is not set
+CONFIG_E1000=y
 CONFIG_E1000E=m
 CONFIG_E1000E_HWTS=y
 # CONFIG_IGB is not set

To view this discussion on the web visit https://groups.google.com/d/msgid/bbr-dev/ff0b4518-91ba-4ddf-b1c8-510f8ec2e1d9n%40googlegroups.com.

[Mahdi]

Well done.

It works now.

Thank you Neal.

[Neal Cardwell]

Great. You are more than welcome. Thanks for raising this issue and thanks for confirming the fix!

neal

To view this discussion on the web visit https://groups.google.com/d/msgid/bbr-dev/1e7c307b-b44e-4f74-a3f3-caf81fc36763n%40googlegroups.com.