https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232016-01-04T19:26:52ZNDN project issue tracking systemNFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=140532016-01-04T19:26:52ZJunxiao Shi
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/3353">Feature #3353</a>: NetworkMonitor: emit fine-grained signals when the state of a network interface changes</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=140542016-01-04T19:29:24ZJunxiao Shi
<ul></ul><p>Question: how to determine which UDP faces are on <code>wlan0</code>?</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=140552016-01-04T19:29:36ZJunxiao Shi
<ul><li><strong>Category</strong> set to <i>Faces</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=140582016-01-05T05:54:21ZDavide Pesavento
<ul></ul><p>Junxiao Shi wrote:</p>
<blockquote>
<p>Question: how to determine which UDP faces are on <code>wlan0</code>?</p>
</blockquote>
<p>We're still working out the details of that mechanism, but the idea is that <code>FaceManager</code> maintains a mapping from NICs to faces. Andrea will post a more detailed design once we get there.</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=142322016-01-19T15:49:18ZDavide Pesavento
<ul><li><strong>Subject</strong> changed from <i>Setting transport state UP/DOWN based on the state of the underlying network interface</i> to <i>Set transport state UP/DOWN based on the state of the underlying network interface</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=144002016-02-09T11:08:21ZAndrea TosattoAndrea.Tosatto@lip6.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=145122016-02-25T11:41:17ZAndrea TosattoAndrea.Tosatto@lip6.fr
<ul></ul><p>We've some design questions regarding permanent unicast faces, in particular how they behave when their face local address is removed from the interface. For example, when the permanent face local address is removed from the interface there could be the possibility to communicate with the face remote endpoint using a different local address. Is it the behavior we want for a permanent face?</p>
<p>Our proposed solution, that fits well our scenario, is to choose an address from the same interface when the face local address has been removed. If no other address is available the face will stick around until an address becomes available on that interface. Is this a good behavior for a permanent face? It could be strange if a user specify a local address when creating the permanent face(<a class="issue tracker-2 status-6 priority-2 priority-default closed" title="Feature: nfdc create: allow specifying local URI (Rejected)" href="https://redmine.named-data.net/issues/3471">#3471</a>).</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=149022016-03-08T15:09:20ZDavide Pesavento
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-2 priority-2 priority-default" href="/issues/3521">Feature #3521</a>: Netdev-bound faces</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=157452016-05-31T11:04:34ZDavide Pesavento
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>Assignee</strong> deleted (<del><i>Andrea Tosatto</i></del>)</li></ul><p>Andrea's internship with us is over. He already wrote most of the implementation of this feature in a local branch. I will polish the code and submit it for merging when/if time allows, most likely after the summer.</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=172872016-10-16T15:57:41ZDavide Pesavento
<ul><li><strong>Target version</strong> changed from <i>v0.5</i> to <i>v0.6</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=197472017-07-07T01:39:50ZJunxiao Shi
<ul><li><strong>Blocked by</strong> <i><a class="issue tracker-2 status-5 priority-2 priority-default closed" href="/issues/4021">Feature #4021</a>: FaceSystem: use NetworkMonitor::listNetworkInterfaces()</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=197482017-07-07T01:40:13ZJunxiao Shi
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-2 status-1 priority-2 priority-default" href="/issues/3420">Feature #3420</a>: best-route: return Nack if nexthops are DOWN</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=205112017-09-11T13:23:36ZDavide Pesavento
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/20511/diff?detail_id=18094">diff</a>)</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=208412017-10-17T13:18:33ZDavide Pesavento
<ul><li><strong>Target version</strong> changed from <i>v0.6</i> to <i>v0.7</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=232972018-05-21T11:53:00ZAshlesh Gawande
<ul><li><strong>Blocks</strong> <i><a class="issue tracker-3 status-1 priority-2 priority-default" href="/issues/3937">Task #3937</a>: NLSR should react to Face event notifications</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=243562018-11-23T10:14:44ZJunxiao Shi
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>Junxiao Shi</i></li><li><strong>Estimated time</strong> set to <i>12.00 h</i></li></ul><p>I'll work on state transition of Ethernet faces. I do not see a clear implementation path to other unicast faces.</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=243572018-11-23T11:27:20ZJunxiao Shi
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>Ethernet multicast <a href="https://gerrit.named-data.net/#/c/NFD/+/5042">https://gerrit.named-data.net/#/c/NFD/+/5042</a></p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=245512019-01-14T16:33:12ZJunxiao Shi
<ul><li><strong>Blocks</strong> deleted (<i><a class="issue tracker-2 status-1 priority-2 priority-default" href="/issues/3420">Feature #3420</a>: best-route: return Nack if nexthops are DOWN</i>)</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=245532019-01-14T16:33:23ZJunxiao Shi
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-2 priority-default" href="/issues/3420">Feature #3420</a>: best-route: return Nack if nexthops are DOWN</i> added</li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=245552019-01-14T16:35:01ZJunxiao Shi
<ul><li><strong>Assignee</strong> deleted (<del><i>Junxiao Shi</i></del>)</li></ul><p>As I indicated, I don't know how to implement for non-Ethernet faces, so I'm releasing this issue to whoever interested.</p>
<p><a class="issue tracker-2 status-1 priority-2 priority-default" title="Feature: best-route: return Nack if nexthops are DOWN (New)" href="https://redmine.named-data.net/issues/3420">#3420</a> can now proceed. Strategy can return Nack to a point-to-point downstream when upstream is Ethernet that is DOWN.<br>
<a class="issue tracker-3 status-1 priority-2 priority-default" title="Task: NLSR should react to Face event notifications (New)" href="https://redmine.named-data.net/issues/3937">#3937</a> is still blocked because NLSR mainly uses UDP unicast faces.</p>
NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=257322019-08-27T20:40:52ZDavide Pesavento
<ul><li><strong>Target version</strong> changed from <i>v0.7</i> to <i>22.02</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=272942021-05-28T17:16:30ZDavide Pesavento
<ul><li><strong>Target version</strong> changed from <i>22.02</i> to <i>22.12</i></li></ul> NFD - Feature #3352: Set transport state UP/DOWN based on the state of the underlying network interfacehttps://redmine.named-data.net/issues/3352?journal_id=277312022-09-07T09:10:18ZDavide Pesavento
<ul><li><strong>Target version</strong> deleted (<del><i>22.12</i></del>)</li></ul>