Project

General

Profile

Actions

Bug #1406

closed

udp4 tunnel does not work

Added by Yi Huang over 10 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Faces
Target version:
Start date:
03/25/2014
Due date:
% Done:

0%

Estimated time:

Description

NFD commit e17349ac009d30ab5d0d39173b408e33621fab7e

ndn-cpp-dev commit 37e317f78931f5a1f01e2e82bf1d2ae13b6a2f74

ndn-traffic-generator commit fda32a3f278d81fb5c6920b91d655fbffcdd52e2

Platform: Ubuntu 12.04

Topology: Two hosts connected as A-B.

  • A: 10.0.0.1
  • B: 10.0.0.2

Steps to reproduce:

  1. On A and B, make sure the config file "~/.ndn/client.conf" has the line "prefix=nfd-0.1" and start NFD (sudo env NFD_LOG=all nfd)
  2. On A, use nfdc to create new udp face. I've tested both faces does not work.(nfdc create udp4://10.0.0.2)

    Face creation succeeded: ControlParameters(FaceId: 7, Uri: udp4://10.0.0.2, )

  3. On A, use nfdc to add a nexthop record to the tunnel, so that Interests under a certain prefix go to B. (nfdc add-nexthop ndn:/example 7 0)

  4. On B, start ndn-traffic-server using the attached server config (ndn-traffic-server NDNTrafficServer.conf)

  5. On A, start ndn-traffic client using the attached client config (ndn-traffic NDNTrafficClient.conf)

  6. When the client generates enough interests, kill the client. The client log indicates that all interests are lost.

Expected result:

All interests get data back.

Additional information:

I tried to tcpdump on B and see packets from 10.0.0.1.


Files

NDNTrafficServer.conf (963 Bytes) NDNTrafficServer.conf Yi Huang, 03/25/2014 12:13 PM
NDNTrafficClient.conf (1.44 KB) NDNTrafficClient.conf Yi Huang, 03/25/2014 12:13 PM
Actions #1

Updated by Junxiao Shi over 10 years ago

  • Category set to Faces
  • Assignee set to Giulio Grassi

I cannot reproduce this issue with "tcp4" scheme.

This bug with "udp4" scheme is confirmed.

Sending side seems to work fine, and tcpdump on host B shows UDP packets from A to B:6363.

nfd-status does not show any accepted UDP face, which indicates UdpChannel does not correctly register newly accepted face into FaceTable.

Actions #2

Updated by Yi Huang over 10 years ago

  • Subject changed from tcp4/udp4 tunnel does not work to udp4 tunnel does not work
  • Description updated (diff)

Hmm I can no longer reproduce this issue with tcp4 either. Anyways tcp4 works now. I am going to change the description to udp4 only.

Actions #3

Updated by Alex Afanasyev over 10 years ago

  • Assignee changed from Giulio Grassi to Anonymous

This is a small bug in FaceManager. We didn't actually started listening on any of the created udp channels. Actually, we do not even have "listen" option defined in "udp" section.

I have reassigned task to Steve.

Actions #4

Updated by Anonymous over 10 years ago

  • Status changed from New to In Progress
Actions #5

Updated by Anonymous over 10 years ago

  • Status changed from In Progress to Code review
Actions #6

Updated by Anonymous over 10 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF