Bug 276197 - bsdconfig - network interfaces not set up correctly, eventhough "active" is shown by ifconfig
Summary: bsdconfig - network interfaces not set up correctly, eventhough "active" is s...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 13.2-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-08 11:03 UTC by Chen Wei Chung
Modified: 2024-01-12 18:44 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chen Wei Chung 2024-01-08 11:03:28 UTC
Environment:
  FreeBSD version: 13.2-RELEASE
  hardware: Raspberry Pi 400
  ethernet cable: cat 5e

Bug Description:
  In ifconfig(8), the "status" shows the current status of a link. However, it is possible that the status shows "active" but the link is not working (can't ping ip address) after setting up network interface using bsdconfig(8).

Steps to Reproduce Bug:
  1. In bsdconfig(8) > Networking Management > Network Interfaces > <link_name> > options 
  2. Select "media 1000baseT mediaopt full-duplex,master instance 1" and bring up interface during confirmation. This option is not supported by Raspberry Pi 400, so when you exit the bsdconfig(8) and type ifconfig(8), the status of <link_name> shows "no carrier".
  3. Repeat step 1 but choose "media 100baseTX" option and bring up interface during confirmation.
  4. Exit the bsdconfig(8) and use ifconfig(8) to show network interface info, the status of <link_name> becomes "active". However, when you try to ping other IP addresses (such as 192.168.0.1), it shows "no route to host".
  5. Use service(8) with command "#service netif restart" to restart netif, the ifconfig(8) shows the link as "active", now you are able to ping other ip addresses and connect to other hosts.

Expected Result:
  The network interface should be set up correctly by bsdconfig(8). I'm not sure if the "active" status by ifconfig(8) is shown correctly or not, but the inconsistency makes network debugging quite painful.
Comment 1 Mark Johnston freebsd_committer freebsd_triage 2024-01-12 18:44:30 UTC
Are you able to test 14.0 and see whether the bug is still present there?