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.

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

Honor NDN_CLIENT_TRANSPORT environment variable #85

Open
yoursunny opened this issue Dec 27, 2024 · 2 comments
Open

Honor NDN_CLIENT_TRANSPORT environment variable #85

yoursunny opened this issue Dec 27, 2024 · 2 comments
Labels
std go-ndn issues

Comments

@yoursunny
Copy link
Member

Currently, NDNd applications are hard-coded to connect to /var/run/nfd/nfd.sock only.
They should be updated to honor NDN_CLIENT_TRANSPORT environment variable.

Benefits include:

  • The applications can be configured to connect to an alternate forwarder instance.
  • The applications can be configured to connect to NFD via localhost TCP, so that the traffic may be captured with tcpdump for debugging purposes.
@pulsejet pulsejet added the std go-ndn issues label Dec 27, 2024
@zjkmxy
Copy link
Member

zjkmxy commented Dec 27, 2024

Doesn't the forwarder read unix.socket_path in the yaml file?

@pulsejet
Copy link
Collaborator

Forwarder we can leave as-is. For other apps a MakeDefaultFace function would do the trick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
std go-ndn issues
Projects
None yet
Development

No branches or pull requests

3 participants