Project

General

Profile

Feature #4303

Optionally write prefixes to configuration file that were advertised in NLSR

Added by Ashlesh Gawande over 1 year ago. Updated 28 days ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
01/28/2019
Due date:
% Done:

100%

Estimated time:

Description

Suggested in ICN. So if NLSR does down and recover then it can load all the prefixes that are supposed to be advertised.


Related issues

Related to NLSR - Task #4823: nlsr.conf file should not be modified during the runtimeClosed2019-01-28

History

#1 Updated by Ashlesh Gawande about 1 year ago

  • Assignee set to Saurab Dulal
  • Target version set to v0.5.0

#2 Updated by Ashlesh Gawande about 1 year ago

This should be a command line option to nlsrc advertise/withdraw as to whether to save/remove from nlsr.conf advertising section.

#3 Updated by Saurab Dulal about 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

#4 Updated by Saurab Dulal about 1 year ago

  • % Done changed from 10 to 50

#5 Updated by Saurab Dulal about 1 year ago

Some limitations with this patch.
1. It removes all the comments from the conf file. It's because I am using BOOST to read and write to the conf file, BOOST removes the comments in that process.
2. Once a prefix is advertised without a save command, it cannot be saved later.
3. Once a prefix is withdrawn without a delete command, it will not be deleted from the conf file.

Above limitations has been resolved.

Additionally,

few StatusCodes are introduced in NLSR.

406: Prefix is already saved or deleted from the configuration file.

205: Saving or deleting a prefix from the configuration file. This also includes saving or deleting an already advertised or withdrawn prefix from the configuration file.

StatusCode loosely follows the HTTP semantics described in RFC2616 section 10 (RFC2616)

#6 Updated by Ashlesh Gawande 2 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

#7 Updated by Ashlesh Gawande about 2 months ago

  • Status changed from Closed to Feedback

Davide reports that changing /etc files during runtime is not a good idea as they are supposed to be static.

#8 Updated by Alex Afanasyev about 2 months ago

Ehm... Yes, config files should be static and it is quite unexpected if they are modified... If you need modifiable state, it should go under /var area. On some systems, this /var area can be different and is managed by the system appropriately.

#9 Updated by Saurab Dulal about 2 months ago

  • Related to Task #4823: nlsr.conf file should not be modified during the runtime added

#10 Updated by Saurab Dulal 28 days ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF