[dbus]How to verify the capability of dbus IPC between machines

[yinxb]

Hi Pavel Strashkin

    It seems that dbus-monitor did not connect the specified host & port.

    When execute the  command in remotePC or lolcaPC:
    dbus-monitor --address tcp:host=xx.xxx.xx.116,port=12434
     only get the register failed message
========
Failed to register connection to bus at
tcp:host=10.239.58.116,port=12434: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
========
   I even turned off the firewall on both remotePC and localPC and
still get the same result.

在 2011年11月30日 上午3:34，Pavel Strashkin <pavel.strashkin at gmail.com> 写道：
> Does dbus-monitor successfully connect to dbus-daemon on specified host & port?
>
> 2011/11/28 yinxb <yinxiaobiao at gmail.com>:
>> In addition,dbus-monitor in the remote PC cannot find any info related
>> the dbus-send.
>>
>> 在 2011年11月29日 上午10:38，yinxb <yinxiaobiao at gmail.com> 写道：
>>> Hi  Thiago Macieira and Pavel
>>>
>>>     Thanks for your reply.
>>>
>>>     As metioned in your mail,I did the following steps:
>>> 1.Romote PC:
>>>   Config /etc/dbus-1/system.conf.
>>>   Add listen tcp:host=0.0.0.0,port=12434
>>>
>>> 2.Local PC:
>>>   dbus-send --address=tcp:host=xx.xxx.xx.116,port=12434 --print-reply
>>>  --dest=org.gnome.PowerManager
>>> /org/ayatana/NotificationItem/gnome_power_manager/Menu
>>> org.freedesktop.Dbus.Introspectable.Introspect
>>>
>>> after that,I got the following message:
>>> Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
>>> Possible causes include: the remote application did not send a reply,
>>> the message bus security policy blocked the reply, the reply timeout
>>> expired, or the network connection was broken.
>>>
>>> Can you figure out what is missing or wrong with my steps?
>>>
>>> ps:
>>> telnet can connect the remote PC (xx.xxx.xx.116).
>>>
>>> 2011/11/29 Thiago Macieira <thiago at kde.org>:
>>>> On Monday, 28 de November de 2011 15.59.42, 尹YinXiaobiao wrote:
>>>>> Hi all
>>>>>      I am a newbie at Dbus and this is my first mail in this maillist.
>>>>>     By some investigate and look at the source code,I know that dbus
>>>>> is using socket(tcp & unix domain socket) to transfer data.
>>>>>     So it is possible for communication between two machines(or VM).
>>>>
>>>> Right, it's possible.
>>>>
>>>>>     Now my question is how to vevify this capability by dbus-send command.
>>>>>     Can anyone give me  a hint?
>>>>
>>>> Just send the message you want to send. You know the address of the bus server
>>>> to connect to, so pass it in the --address= option. You know that address
>>>> because you configured the other machine with it.
>>>>
>>>>> Someone tell me that dbus do not listen on TCP by default,how to
>>>>> enable TCP listen?
>>>>
>>>> Create your own config file and change the <listen> directive to be on TCP.
>>>>
>>>> Remember: D-Bus TCP is unauthenticated an unencrypted. It accepts connections
>>>> from anywhere and trusts it blindly.
>>>>
>>>> --
>>>> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
>>>>   Software Architect - Intel Open Source Technology Center
>>>>      PGP/GPG: 0x6EF45358; fingerprint:
>>>>      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>>>>
>>>> _______________________________________________
>>>> dbus mailing list
>>>> dbus at lists.freedesktop.org
>>>> http://lists.freedesktop.org/mailman/listinfo/dbus
>>>>
>>>>
>>>
>> _______________________________________________
>> dbus mailing list
>> dbus at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dbus
>>