Feature: <Ethernet> Ethernet config rework (#12)#39
Draft
mcbridematt wants to merge 12 commits intordkcentral:developfrom
Draft
Feature: <Ethernet> Ethernet config rework (#12)#39mcbridematt wants to merge 12 commits intordkcentral:developfrom
mcbridematt wants to merge 12 commits intordkcentral:developfrom
Conversation
torrentius
changed the title
This config is for a simple, two interface setup (eth0 LAN, eth1 WAN), well suited for use in QEMU.
This should be controlled by PSM / TR-181 settings instead.
…faces WAN Manager may not consider devices as available unless the interface has been brought up.
The required steps are now performed by pre-start steps for PsmSsp and CcspEthAgent
This is to avoid any hardcoded interface references. The Ethernet agent calls this function to determine if an Ethernet interface in Device.Ethernet.Interface.X is the WAN facing one. Originally developed by mahanteshchitt <mahantesh_chittapur@comcast.com>. in rdkcentral@6d451ef
This invocation (mkdir -p /rdklogs/logs) will fail under a read-only rootfs environment. We already create and mount this folder earlier in the boot process.
This uses: SFP1 (eth5) as 1st priority WAN LAN4 (eth2) as 2nd priority WAN + cellular
mcbridematt
force-pushed
the
ethernet-config-rework
branch
from
973dac7 to
4c1818b
Compare
…s when erouter0 compatibility enabled
…atibility enabled
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements #12
Until now, meta-rdk-bsp-arm has used a PSM config file for the full (8+2) Ten64 board. Boards that are not Ten64's had their Ethernet interfaces adjusted to look like one (Highest priority WAN -> eth8, second highest eth6).
We now try to do this in a more RDK way by shipping PSM configs for each supported machine, with a fallback "default" suitable for machines with only two interfaces (LAN + WAN).
The appropriate PSM default config is copied on first boot before PsmSsp starts, avoiding the need to manipulate PSM config from bitbake recipes and/or bake separate rootfs images for each development board.
We also want to support variations of configurations for certain use cases (like erouter0 backwards compatibility)
As part of this, any hard coding of WAN interfaces (be it eth6, eth8 or erouter0) should be avoided.
Implemented so far:
Still to be done:
erouter0 compatibility
Adding the DISTRO_FEATURE keyword
erouter0_compatibilitywill modify the initial PSM config to seterouter0as the WAN interface name: