Opened 2 years ago

Closed 21 months ago

Last modified 5 months ago

#14626 closed bug (invalid)

network device config misalignment

Reported by: kallisti5 Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Kits/Network Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


The coupling of /boot/system/settings/network/interfaces is too loose to the network card.


interface    /dev/net/emulex_oce/0 {
    address inet {

Reboot with only one network card (blacklist emulex_oce for example): /dev/net/rtl81xx/0

The device /dev/net/rtl81xx/0 is configured with instead of being unconfigured.

Change History (5)

comment:1 by kallisti5, 2 years ago

Component: Drivers/Network/emulex_oceKits/Network Kit
Owner: changed from waddlesplash to nobody

comment:3 by kallisti5, 22 months ago

I'm not 100% sure that something doesn't come in later and call SetName, but the NULL check at means it's a big unknown.

I think the NULL check is there as a generic "if no NIC name, apply static IP to the first nic", however that creates a lot of unknown behavior.

If someone swaps a NIC, we really should start ignoring the configuration for it since with multiple NIC's things get a bit complex.

Maybe that NULL check should be returned as B_ENTRY_NOT_FOUND?

comment:4 by axeld, 21 months ago

Resolution: invalid
Status: newclosed

That's actually intended behavior. There is no problem in NetworkSettings, the logic for this sits in the net_server, it's even documented now :-)

I don't really see a reason to change this, but if you see one, please elaborate.

Version 0, edited 21 months ago by axeld (next)

comment:5 by nielx, 5 months ago

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.