clock is lost when router is reloaded despite saving config
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 405
- Forks
- 99
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
From @swils024 on May 21, 2017 20:29
While doing the Cisco CCNA (200-125) - Pass with GNS3 course on GNS3 Academy, I noticed that a user had commented on one of the NTP videos saying that the clock setting is lost when a router is reloaded. I have replicated the issue and despite saving the config before the reload, the config was lost. All comments welcome.
Copied from original issue: GNS3/gns3-gui#2075
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reproducing the router reload after saving the configuration, then trace the reload and clock-state handling in the emulator. Done means the configured clock remains after reload, with a regression test if the existing test structure can be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100