Convert FastEthernet/Serial to Ethernet in gns3vault-archive configs#27
Draft
Convert FastEthernet/Serial to Ethernet in gns3vault-archive configs#27
Conversation
Co-authored-by: renemolenaar82 <6650207+renemolenaar82@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Verify correctness of gns3vault-archive topologies
Convert FastEthernet/Serial to Ethernet in gns3vault-archive configs
Dec 14, 2025
renemolenaar82
requested changes
Feb 18, 2026
Collaborator
renemolenaar82
left a comment
There was a problem hiding this comment.
Recheck this because files might have been updated.
Co-authored-by: renemolenaar82 <6650207+renemolenaar82@users.noreply.github.com>
Contributor
Author
Rechecked all gns3vault-archive configs. Found and fixed 943 additional config files in final-configs directories that still had FastEthernet/Serial interfaces. All 1910 router configs now use Ethernet interfaces with proper +1 offset mapping (topology Ethernet0/1 → config Ethernet0/0). Commit: b7eea2e |
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
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.
Router configs used legacy FastEthernet and Serial interfaces incompatible with Cisco IOL containerlab deployments. All 1910 config files (both startup-configs and final-configs) required Ethernet interfaces to match the topology files' addressing scheme with proper +1 offset mapping.
Changes
Interface Type Conversion
FastEthernet0/0→Ethernet0/0,FastEthernet1/0→Ethernet0/1,FastEthernet2/0→Ethernet0/2Serial0/0→Ethernet0/0,Serial1/0→Ethernet0/1,Serial2/0→Ethernet0/2,Serial2/1→Ethernet0/3Offset Mapping
Topology files enumerate interfaces starting at
Ethernet0/1. Containerlab maps these to router physical ports with -1 offset:Ethernet0/1→ ConfigEthernet0/0(physical port 0)Ethernet0/2→ ConfigEthernet0/1(physical port 1)Example
Scope
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.