Binding a QTcpSocket to a specific enternet interface

[wysota]

Have you tried using QAbstractSocket::setLocalAddress()?

[Banfa]

Hmmmm, I had considered that function but the help says

void QAbstractSocket::setLocalAddress ( const QHostAddress & address ) [protected]

Sets the address on the local side of a connection to address.

You can call this function in a subclass of QAbstractSocket to change the return value of the localAddress() function after a connection has been established. This feature is commonly used by proxy connections for virtual connection settings.

Note that this function does not bind the local address of the socket prior to a connection (e.g., QUdpSocket::bind()).

This function was introduced in Qt 4.1.

Which suggested to me that this didn't effect the socket binding. I may try giving it a whirl see what happens.

Like I say once the network architecture is fixed the issue may not be relevant as the routing tables would take care of it all. After posting yesterday I did manage to persuade my colleagues that the planned network architecture wouldn't work.

[rickrvo]

I'm having the same problem too. I'm trying to make sure that the tcpsocket uses my wireless connection by setting the setLocalAddress() with my wireless ip and still it sends by the ethernet connection... If i disconnect the ehternet connection it sends on wireless...

I had to change the function setLocalAddress() in QAbstractSocket.h from protected to public otherwise using QTcpSocket wouldn't let me use the protected function, as it is not declared on QTcpSocket...

Have you found a solution to this problem?