default tcp host

Simon McVittie simon.mcvittie at
Fri Jun 15 04:33:19 PDT 2007

Hash: SHA1

On Thu, 14 Jun 2007 at 10:05:03 -0400, Havoc Pennington wrote:
> That will work on the local machine, but presumably connecting via TCP 
> to the local machine is basically a weird case.

... unless you're running Windows, in which case it's all you can do!
(At least until we have a shared-memory transport or something...)

> Somewhat different: for what I am doing right now, I'm essentially 
> telling Avahi to advertise a D-Bus server on all interfaces on the 
> machine; Avahi figures out and tells the remote system the 
> hostname/address/port of each D-Bus server socket, so in this case the 
> D-Bus server itself does not really need to be able to report a valid 
> remote hostname. The D-Bus server itself does need to be able to listen 
> on all interfaces, though.

The remote client should be able to construct a D-Bus address from the
information available from Avahi, for instance a sensible format might

_dbus._tcp.local. PTR Havoc._dbus._tcp.local.
Havoc._dbus._tcp.local. SRV 0 0 4444 havocs-box.local.
Havoc._dbus._tcp.local. TXT "txtver=1" "dbus-uuid=hexhexhexhex"     ####
havocs-box.local. A

which gives you:


(Syntax may be wrong, I haven't been paying attention to the precise
details, but you get the idea.)

The TXT record marked #### is the only one you need to define a format for -
the rest are provided more or less automatically by DNS-SD. So it's entirely
possible that you're solving a problem that you don't need to.
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: or


More information about the dbus mailing list