o Macieira" , interest@qt-project.org
> Subject: Re: [Interest] QUdpSocket, QNetworkDatagram and QNetworkInterface
>
> I think you're running into a NAT router (network address translation)
> You can configure your router to not do this, but that requires you to have
> a
pplications can tell routers what they
need (popular with games).
You might be able to fix the issue just by including the source IP in the UDP
packet though.
> Sent: Wednesday, October 30, 2019 at 4:42 AM
> From: "Nuno Santos"
> To: "Thiago Macieira"
> Cc: i
Il 30/10/19 10:42, Nuno Santos ha scritto:
My local network has the main modem, which is connected to the internet. Then,
there is an older wifi router from linksys only serving as a cable lan switch.
Do you have a clue why is this happening? This is completely ruining the
previsibility I was
Thiago,
>> You cannot infer which interface a packet was sent on from the IP address it
>> included in the sender. It's entirely possible to use one interface's IP
>> address while sending on another.
I was trying to take advantage of this but I’m having an unpleasant surprise.
Even after sett
Thiago,
Thanks so much for this super detailed and informative reply. All my questions
are clarified now.
Thank you!
Best regards,
Nuno
> On 29 Oct 2019, at 22:06, Thiago Macieira wrote:
>
> On Tuesday, 29 October 2019 12:12:37 PDT Nuno Santos wrote:
>> Hi,
>>
>> I’m trying to understand h
On Tuesday, 29 October 2019 12:12:37 PDT Nuno Santos wrote:
> Hi,
>
> I’m trying to understand how does Qt decides which QNetworkInterface will be
> used when a writeDatagram is called.
The one you passed. Otherwise, it doesn't decide.
> I’m currently on a system that has both cable and wifi con
ober 29, 2019 at 2:12 PM
> From: "Nuno Santos"
> To: "interestqt-project.org"
> Subject: [Interest] QUdpSocket, QNetworkDatagram and QNetworkInterface
>
> Hi,
>
> I’m trying to understand how does Qt decides which QNetworkInterface will be
> used when
Hi,
I’m trying to understand how does Qt decides which QNetworkInterface will be
used when a writeDatagram is called.
I’m currently on a system that has both cable and wifi connections available,
however, when doing a QUdpSocket writeDatagram the packets are being sent from
the wifi adaptor, a
On Tuesday, 27 February 2018 10:47:12 PST Igor Mironchik wrote:
> Hi. What I afraid that happened.
>
> Is situation possible that QUdpSocket in bound state can be somehow
> disconnected (not from app's code) for any reason?
Yes. If you don't connect, it's disconnected. But disconnected UDP socket
2018-02-28 14:16 GMT+01:00 Igor Mironchik :
> Hi,
>
> Sure, I check codes. My IPC works. I just want to know should I care about
> something with UDP or I can just do bind() and process pending datagrams,
> and don't worry about something additional in my code?! Thanks.
>
> QUdpSocket inherits "*e
Hi,
On Wed, February 28, 2018 14:16, Igor Mironchik wrote:
> On 28.02.2018 15:49, Konrad Rosenbaum wrote:
>> Your above code means that the socket will listen on somePort of every
>> open interface and may share this with other programs listening on the
>> same port.
>>
>> I hope you are checking
Hi,
On 28.02.2018 15:49, Konrad Rosenbaum wrote:
First off: UDP sockets are not connected - it is a connectionless protocol
in which every data packet is routed on its own.
Sure, I know it, thanks.
Your above code means that the socket will listen on somePort of every
open interface and may
hi,
On Tue, February 27, 2018 19:47, Igor Mironchik wrote:
> Is situation possible that QUdpSocket in bound state can be somehow
> disconnected (not from app's code) for any reason? I.e. something wrong
> on the network, UDP socket can't work properly, something wrong in the
> OS that leads to tha
Hi. What I afraid that happened.
Is situation possible that QUdpSocket in bound state can be somehow
disconnected (not from app's code) for any reason? I.e. something wrong
on the network, UDP socket can't work properly, something wrong in the
OS that leads to that UDP socket will not receive
On terça-feira, 27 de fevereiro de 2018 01:40:11 PST Igor Mironchik wrote:
> Hello,
>
> Could anybody tell me if QUdpSocket after
>
> QUdpSocket::bind( somePort, QUdpSocket::ShareAddress );
>
> can be closed for some reasons and stopped for receiving new datagrams
> (not from the application sid
Hello,
Could anybody tell me if QUdpSocket after
QUdpSocket::bind( somePort, QUdpSocket::ShareAddress );
can be closed for some reasons and stopped for receiving new datagrams
(not from the application side, not from my code...)?
What can be the reason of such behavior (disconnection of boun
On Wednesday, 4 October 2017 08:39:43 PDT Richard Öhlinger wrote:
> On 10/04/2017 05:29 PM, Thiago Macieira wrote:
> > If you want to file a bug report too, I'd appreciate it.
>
> Done QTBUG-63605.
>
> Thank you for looking into it.
My pleasure. When it is my own code, I know exactly how to fix
On 10/04/2017 05:29 PM, Thiago Macieira wrote:
If you want to file a bug report too, I'd appreciate it.
Done QTBUG-63605.
Thank you for looking into it.
Regards,
Richard
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org
On Wednesday, 4 October 2017 02:38:31 PDT Richard Öhlinger wrote:
> On 10/04/2017 10:13 AM, Richard Öhlinger wrote:
> > I do bind to QHostAddress::AnyIPv4 and I get all the messages, but
> > just not destinationAddress/Port.
>
> After looking at the implementation in qnativesocketengine_win.cpp i
On 10/04/2017 10:13 AM, Richard Öhlinger wrote:
I do bind to QHostAddress::AnyIPv4 and I get all the messages, but
just not destinationAddress/Port.
After looking at the implementation in qnativesocketengine_win.cpp i see
that QNativeSocketEnginePrivate::nativeReceiveDatagram does not set
On 10/03/2017 04:52 PM, Thiago Macieira wrote:
If that doesn't fix the issue, can you make a simple example for what fails for
you? I need to test what's wrong.
I do bind to QHostAddress::AnyIPv4 and I get all the messages, but just
not destinationAddress/Port.
I've attached a minimal exampl
On terça-feira, 3 de outubro de 2017 07:28:15 PDT Richard Öhlinger wrote:
> Hi,
>
> I'm using QUdpSocket on Windows 10 to receive Multicast messages. Since
> Windows does not allow for binding directly to the multicast address
> I've to bind to the AnyIP and filter for destination address.
>
> Th
Hi,
I'm using QUdpSocket on Windows 10 to receive Multicast messages. Since
Windows does not allow for binding directly to the multicast address
I've to bind to the AnyIP and filter for destination address.
Therefore I use QUdpSocket::receiveDatagram to get a QNetworkDatagram.
But its destin
Hi,
I have exactly the same issue .. I have update my application to Qt5.4.2
and sometimes, the application no more received readyRead from QUdpSocket
(Windows x64 Seven).
2015-06-30 11:11 GMT+02:00 Mark Gaiser :
> On Mon, Jun 29, 2015 at 8:08 PM, Thiago Macieira <
> thiago.macie...@intel.com> w
Hi,
I ha
2015-06-30 11:11 GMT+02:00 Mark Gaiser :
> On Mon, Jun 29, 2015 at 8:08 PM, Thiago Macieira <
> thiago.macie...@intel.com> wrote:
>
>> On Monday 29 June 2015 11:30:44 Robert Daniels wrote:
>> > I've been testing with the new Qt 5.5 release candidate and have had
>> > issues with our app
On Mon, Jun 29, 2015 at 8:08 PM, Thiago Macieira
wrote:
> On Monday 29 June 2015 11:30:44 Robert Daniels wrote:
> > I've been testing with the new Qt 5.5 release candidate and have had
> > issues with our application ceasing to get notified of new datagrams.
>
> https://bugreports.qt.io/browse/QT
On Monday 29 June 2015 11:30:44 Robert Daniels wrote:
> I've been testing with the new Qt 5.5 release candidate and have had
> issues with our application ceasing to get notified of new datagrams.
https://bugreports.qt.io/browse/QTBUG-46552
--
Thiago Macieira - thiago.macieira (AT) intel.com
So
I've been testing with the new Qt 5.5 release candidate and have had
issues with our application ceasing to get notified of new datagrams.
We have a simple signal handler that follows the example given in the
documentation that loops while the socket indicates that there are
still datagrams availa
Ok, I was wrong in my approach of the problem.
I had to use the MulticastInterface to solve my trouble: for UDP
processing, QHostAddress::AnyIPv4 only to bind.
The correct code is (maybe for the next one...) :
QUdpSocket* socket = new QUdpSocket(this);
// Use a regular expression to par
On Thursday 30 October 2014 15:43:23 Jean-Nicolas Artaud wrote:
> I've got a trouble I don't understand : the bind on the QUdpSocket doesn't
> conplains but I don't receive anything if I put my IP Address in
> _bindAddress. So the binding on AnyIPv4 works but not for adresses.
>
> (the soft I'm wo
Hello folk !
I've got a trouble I don't understand : the bind on the QUdpSocket doesn't
conplains but I don't receive anything if I put my IP Address in
_bindAddress. So the binding on AnyIPv4 works but not for adresses.
(the soft I'm working on is multi OS (Linux/Windows) I develop and test on
L
On 3/21/2014 9:33 AM, Thiago Macieira wrote:
> QUdpSocket works in IPv6 mode.
>
> The question is whether your code is IPv6-compatible or whether you've made
> assumption about IPv4 that don't hold in an IPv6 network. So you'll have to
> test to be sure.
That's kind of what I expected, so no sur
Em sex 21 mar 2014, às 09:20:36, Bob Hood escreveu:
> Hey, all. This is just a quick question about IPv4 and IPv6 support in
> QUdpSocket.
>
> I've written a datagram-based client/server application using QUdpSocket,
> and it functions perfectly well on my IPv4-based internal network. The
> clie
Hey, all. This is just a quick question about IPv4 and IPv6 support in
QUdpSocket.
I've written a datagram-based client/server application using QUdpSocket, and
it functions perfectly well on my IPv4-based internal network. The client
uses IPv4 datagram broadcasting to discover the server on the
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-lead
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 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
>> 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);
Em qua 19 fev 2014, às 23:27:38, Tom Isaacson escreveu:
> 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.toAsc
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
On 12 sept. 2013, at 04:01, Thiago Macieira wrote:
> All that worked in Qt 4 continues to work in Qt 5. GPS wasn't part of Qt 4
> (that was Mobility and most of it only supported the Nokia platforms); 3D
> wasn't part of Qt 4 either (Mobility again). Qt Quick 1 continues to work
> exactly like
On quarta-feira, 11 de setembro de 2013 21:41:45, Karl Ruetz wrote:
> We had no problems with the addon until 5.1.1. Hopefully Digia will figure
> out what the deal is soon so I don't have to revert.
That said, we do need to make a release of those solutions. I've built them,
so I know they work
One of our most popular products uses FTP. Yes, it's old (in the field since
1998), but still making us money. We added the portion written in Qt in 2004.
The fragility has never been an issue for us. We haven't seen the problems.
Our product has been stable.
We have a commercial license with
On quarta-feira, 11 de setembro de 2013 10:37:29, Karl Ruetz wrote:
> My main complaint remains the removal of QFtp without providing equivalent
> replacement features in QNAM.
>
> Now, under 5.1.1, I have yet to get the QFtp addon to work.
>
> So it looks like I have to stop using Qt 5 for Andro
On quarta-feira, 11 de setembro de 2013 08:22:19, Jason H wrote:
> Yeah, I knew Qt5 was going to take Qt in a direction that was not going to
> be a good one. We've got too many projects and not enough people to support
> them. Yes, QML is cool but it shouldn't be done at the expense of things
> li
On quarta-feira, 11 de setembro de 2013 17:09:18, Guido Seifert wrote:
> > All QUdpSocket tests are currently being ignored. They have been ignored
> > for the past 2 years. In other words, we have no idea whether QUdpSocket
> > has ever worked for Qt 5.
>
> Wow, this is hardly believable. This ti
they are re-doing the QML
>rendering mainloop. It's not working equivalently on all platforms yet.
>
>Qt4 forever! The thing I liked about Qt4 is it all just works,
>consistently and well.
>
>
>
>
>
> From: Guido Seifert
>To: i
;
> >
> > ____
> > From: Guido Seifert
> > To: interest@qt-project.org
> > Sent: Wednesday, September 11, 2013 11:09 AM
> > Subject: Re: [Interest] QUdpSocket broken?
> >
> >
> >
> > > All QUdpSock
> All QUdpSocket tests are currently being ignored. They have been ignored for
> the past 2 years. In other words, we have no idea whether QUdpSocket has ever
> worked for Qt 5.
Wow, this is hardly believable. This time it isn't about multicast. It is the
normal send/receive between two QUdpS
On quarta-feira, 11 de setembro de 2013 14:54:07, Guido Seifert wrote:
> Hi,
> my QUdpSocket problems got worse. It is so broken that I don't believe that
> it's Qt code. But on the other hand, my code is too simple not to work.
Hi Guido
All QUdpSocket tests are currently being ignored. They have
Am Wed, 11 Sep 2013 07:59:51 -0700
schrieb Thiago Macieira :
> All QUdpSocket tests are currently being ignored. They have been ignored for
> the past 2 years. In other words, we have no idea whether QUdpSocket has ever
> worked for Qt 5.
remembering a great song - strange enough:
"we don't nee
tly on all platforms yet.
Qt4 forever! The thing I liked about Qt4 is it all just works, consistently and
well.
From: Guido Seifert
To: interest@qt-project.org
Sent: Wednesday, September 11, 2013 11:09 AM
Subject: Re: [Interest] QUdpSocket broken?
> A
hing I liked about Qt4 is it all just works, consistently
> and well.
>
>
>
>
>
> From: Guido Seifert
> To: interest@qt-project.org
> Sent: Wednesday, September 11, 2013 11:09 AM
> Subject: Re: [Interest] QUdpSocket broken?
>
>
>
> > All QUdpS
Hi,
my QUdpSocket problems got worse. It is so broken that I don't believe that
it's Qt code. But on the other hand, my code is too simple not to work.
I send a datagram from program 1:
qudpsocket->writeDatagram(,QHostAdress(127.0.0.1),5);
In the other program I connected a qudpsocket:
con
54 matches
Mail list logo
