Project

General

Profile

Actions

Bug #2719

closed

Site name is set incorrectly by NlsrConfigGenerator

Added by Vince Lehman about 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
04/01/2015
Due date:
% Done:

100%

Estimated time:

Description

Currently, NlsrConfigGenerator sets NLSR's site name to the same site for all routers:

general += "  site /edu\n"

Instead, the site name should be set based on the node's name:

general += "  site /{}-site\n".format(self.node.name)
Actions #1

Updated by Vince Lehman almost 9 years ago

  • Tracker changed from Task to Bug
  • Subject changed from Site name set incorrectly by NlsrConfigGenerator to Site name is set incorrectly by NlsrConfigGenerator
  • Target version set to v0.1.0
Actions #2

Updated by Vince Lehman almost 9 years ago

  • Target version changed from v0.1.0 to v0.1.1
Actions #3

Updated by Ashlesh Gawande over 8 years ago

  • Target version changed from v0.1.1 to v0.2.0
Actions #4

Updated by Vince Lehman about 8 years ago

  • Description updated (diff)
Actions #5

Updated by Ashlesh Gawande over 7 years ago

  • Target version changed from v0.2.0 to v0.3.0

Would also need to change:
a) Neighbor generation section
b) advertised prefix
c) convergence test
d) Any internal scripts we use for parsing logs etc.

Actions #6

Updated by Ashlesh Gawande over 7 years ago

Actually advertised prefix need not be updated to save making a lot of changes.

Better to change it to reflect testbed more closely.

Actions #7

Updated by Ashlesh Gawande about 7 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF