On 2/19/2014 10:30 PM, Thiago Macieira wrote:
Let me answer by pasting this:
$ date -u
Thu Feb 20 05:29:41 UTC 2014
Let me retort by pasting this:
http://www.theonion.com/articles/report-stating-current-year-still-leading-argument,35288/
;)
___
Em qui 20 fev 2014, às 05:47:13, Bob Hood escreveu:
On 2/19/2014 10:30 PM, Thiago Macieira wrote:
Let me answer by pasting this:
$ date -u
Thu Feb 20 05:29:41 UTC 2014
Let me retort by pasting this:
http://www.theonion.com/articles/report-stating-current-year-still-leading-a
We're using Qt 4.8.2 on an embedded Linux device. We've always had Ethernet
(eth0) and we use QUdpSocket to send a multicast message on the network:
m_pUdpSocket = new QUdpSocket(this);
m_pUdpSocket-writeDatagram(json.toAscii(), m_cMulticastAddr,
m_cMulticastPort);
This works fine, but
We're using Qt 4.8.2 on an embedded Linux device. We've always had
Ethernet
(eth0) and we use QUdpSocket to send a multicast message on the network:
m_pUdpSocket = new QUdpSocket(this);
m_pUdpSocket-writeDatagram(json.toAscii(), m_cMulticastAddr,
m_cMulticastPort);
It's working
Em qui 20 fev 2014, às 04:54:57, Tom Isaacson escreveu:
But if the Ethernet and Wifi are bridged shouldn't Qt multicast to both?
Depends on how that bridge works. If you have a bridge device, bind to it, not
to eth0 or wlan0.
But given the fact that you said you can bind to the IP assigned to
