GNS3 / GNS3/dynamips

Short lived MAC Address Table in NM-16ESW

Open
#39 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
405
Forks
99
Avg merge
3m
Merged PRs (30d)
1

Description

Quote rednectar.chris:

I'm not sure if it has anything to do with the way the IOS code does timing
- if it times 300 seconds by way of a system clock then I guess dynamips is
not emulating that clock well enough.  If it is some other arbitrary timing
measure then it would be a difficult job to trace.

Related topics

http://forum.gns3.net/topic6794.html

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the related forum topic and the NM-16ESW MAC address table behavior. Investigate whether the 300-second aging period depends on Dynamips' system clock or another timing mechanism. Done means the MAC address table retains entries for the expected lifetime and ages them consistently.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.