Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • D dbus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 266
    • Issues 266
    • List
    • Boards
    • Service Desk
    • Milestones
  • Custom issue tracker
    • Custom issue tracker
  • Merge requests 37
    • Merge requests 37
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dbusdbus
  • dbus
  • Issues
  • #28
Closed
Open
Issue created Jul 09, 2010 by Bugzilla Migration User@bugzilla-migration

dbus-daemon doesn't work when listen on TCP and system has no configured interfaces

Submitted by Pavel Strashkin

Assigned to D-Bus Maintainers

Link to original bug (#28979)

Description

I'm on OpenSolaris, but sure 100% that it can be reproduced on any OS.

If you don't have configured network interfaces in the system (i.e. interfaces without IP address, except loopback) and want run dbus-daemon in TCP mode (tcp:host=*,port=3000) - it will exit with error "Failed to lookup host/port: node name or service name not known".

The reason is AI_ADDRCONFIG flag. If it set, then getaddrinfo returns E_NONAME because when that flag is set - loopback interfaces wil not be in result list I think it's bug in dbus and that flag should be removed from dbus_listen_tcp_socket code. AI_ADDRCONFIG described in http://www.faqs.org/rfcs/rfc3493.html That flag make sence (but i'm not sure) only in _dbus_connect_tcp_socket, but not in _dbus_listen_tcp_socket.

Version: 1.5

Assignee
Assign to
Time tracking