[SOLVED] Windows: netsh and QProcess

helthans

Thanks a lot for the reply, SGaist.
I have tried to use exitCode() as shown below, but this just gives me zero regardless if I have an IP conflict or not.

@
QProcess process;
QString cmd;
cmd = QString("netsh interface ip set address name="%1" static %2 %3 %4 1").arg(m_adapter).arg(m_ip).arg(m_netmask).arg(m_gateway);

process.start(cmd);
process.waitForFinished();
qDebug() << process.exitCode();
@

I have tried to run the netsh command manually in a command prompt. And it does not give any output either if I trigger an IP conflict (other than the pop-up window). Any ideas how to extract this information from netsh?

TioRoy

netsh is returning 0 because it changed the IP successfully.

The conflict notification occurs later.

helthans

Ahh.. Good to know :) Do you know if it is possible to get the notification of the conflict other than a pop-up window?

SGaist

Isn't that popup coming from your OS ?

helthans

Yes that is coming from the OS

TioRoy

I don't know if it's possible.

The popup is displayed when a network packet arrives at the NIC. This can happen immediately or take minutes, depending on network traffic.

jafarabadi.qt

Hi, helthans
i think that below code can be useful for you... change for yourself and try it:
@
QProcess pingProcess;
QString exec = "ping";
QStringList params;
params << "-c" << "1" << IP;
pingProcess.start(exec,params,QIODevice::ReadOnly);
pingProcess.waitForFinished(-1);
QString p_stdout = pingProcess.readAllStandardOutput();
QString p_stderr = pingProcess.readAllStandardError();
@

SGaist

@ a.jafarabadi QProcess is not the problem here, the impact of the call to netsh is completely outside of QProcess.

TioRoy

The code from a.jafarabadi can be usefull: Test the IP (with ping) before invoke the netsh. Maybe you need to decode the results.

If your code will run on Windows only, you can call IcmpSendEcho:http://msdn.microsoft.com/en-us/library/windows/desktop/aa366050(v=vs.85).aspx instead invoke PING.EXE, .

helthans

@ a.jafarabadi and TiRoy: Yes I agree, testing the IP before netsh is the way to go.
Thanks a lot for the solutions suggested. For the network issue my code is split up in a Windows and Linux part (no way around this :)). For Windows I will look into lcmpSendEcho, but for Linux I need to use the ping command - I was hoping I could use another metric, instead of having to do some pattern matching of the output of the ping command, but I guess there is no way around this either.

jafarabadi.qt

Thanks from every one who help to solve it :)