Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No IPv4 address/route after link re-connect #332

Closed
ManiAm opened this issue May 19, 2018 · 4 comments
Closed

No IPv4 address/route after link re-connect #332

ManiAm opened this issue May 19, 2018 · 4 comments
Assignees
@ZoltanBojthe
Labels
Bug Fixed
Milestone
INET 4.2

Comments

@ManiAm
Copy link
Contributor

ManiAm commented May 19, 2018

Consider a scenario where a link between two network nodes gets disconnected (using the scenario manager module) and then it is re-connected as shown below.

2018-05-18_23-46-47

issue 1: the IP address is not shown by the visualizer.
issue 2: Router2 does not add a new route (DIRECT IFACENETMASK) corresponding to the re-connected link into the routing table:

2018-05-18_23-50-14
@levy
Copy link
Contributor

levy commented May 22, 2018

Thanks for the bug report!

@levy levy added the Bug label May 22, 2018
@levy levy self-assigned this Nov 5, 2019
@levy levy assigned ZoltanBojthe and unassigned levy Nov 13, 2019
@levy levy added this to the INET 4.2 milestone Nov 13, 2019
@ZoltanBojthe
Copy link
Contributor

issue1 fixed

@ZoltanBojthe
Copy link
Contributor

issue2 also fixed

@ZoltanBojthe
Copy link
Contributor

issue2 also fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ZoltanBojthe ZoltanBojthe

Labels
Bug Fixed
Projects
None yet
Milestone
INET 4.2
Development

No branches or pull requests
3 participants
@levy @ZoltanBojthe @ManiAm