Failed to start filtering : failed to open device (code:1058). Make sure you run clumsy as Administrator.

[NikoMuffin]

On a fresh restart, clumsy ALWAYS works. Sometimes I have to close clumsy and open back up (for testing purposes).

Randomly (but very very frequently) I will get the following error message when starting back up.
Failed to start filtering : failed to open device (code:1058). Make sure you run clumsy as

Yes, for SURE it is being run as admin. I don't understand how to fix this! Restarting computer fixes it every time.

Please please please... how do I solve this without restarting??
See screenshot below:

See pic: http://i.imgur.com/uTZTiIq.png

[celeron533]

Have you tried to disable the antivirus?

[NikoMuffin]

There has never been any antivirus ever installed on this computer.

Also, forgive me as I forgot to list system specs (rookie mistake!)
Windows 10 64bit. I use 98% portable software that doesn't touch system drivers, registry, or any directory outside of its own.

The one thing I do need to report is use Private Internet Access client (PIA) which is widely considered to be the best VPN in US.

[celeron533]

Sorry I have no idea about the root cause of this issue...
I am also on Windows 10 x64, build 14393
I have Cisco AnyConnect and Cisco VPNClient installed on my machine and never meet this error message. Perhaps you could try release 0.3RC2?
-- OR --
Try disable and enable the VPN's virtual NIC when error occurs, this may a shortcut instead of restart the whole system.

[NikoMuffin]

I will try 0.3 RC2 right away. EDIT #2: testing now.

I'll try uninstalling the VPN at one point to see if that's the cause...

[NikoMuffin]

It looks like 0.3 RC2 has broken command line in my clumsy shortcut you helped me before?

For example:

Running "run as admin" shortcut with following command arguments:
"--filter "inbound" --lag true --lag-time 175"

does not work anymore with RC2 :(

EDIT: So it looks like "inbound" is no longer an option in RC2. It defaults back to "localhost ipv4 all" but irrespective to that LAG is not automatically checked off like it was before.

[NikoMuffin]

So far 0.3 RC2 is working. I'll do considerable testing and let you know how it goes.

Regarding RC2 Here is what I would like to do...

"--filter "inbound" --lag true --lag-time 175"
(Lag should be checked)

To the two following IPs only:
66.36.243.81
66.164.221.80

Is this possible with RC2?

EDIT: holy shit, no idea you had an RSS feed for releases! YAY! Subscribed!!

[NikoMuffin]

It seems inbound (just different name in list) still exists, but it looks like RC2 is not honoring the --lag true argument. In other words, it's not auto-checking lag, whereas 0.2 does. :(

[NikoMuffin]

OK I haven't had the code:1058 error in 22 hours. I'll consider it fixed but will report back if it happens again.

However, the RC2 problem with not honoring "--lag true" command still exists. I put notifications on to await your reply.

Thx again for this software. One of a kind and very useful :)

[celeron533]

Hi @stisev ,
I am glad that 0.3 RC2 solved your problem.
But... I am not the author of Clumsy... 😄
This guy is the first author --> @jagt

[celeron533]

Parameters for version 0.2 could be found at:
#1 (comment)

and commit comments:
046572c

[NikoMuffin]

Yay! --lag on worked!

Sorry to bother you celeron, but 1 more question:
Can you tell me if there's any way to set a shortcut to auto-limit the lag to 2 different IPs only so other connections are not affected?

So far, I have:
\clumsy.exe --filter "inbound" --lag on --lag-time 175

Want to affect these two:
65.164.221.80
65.36.243.81

THANK YOU for your help!!!!

[celeron533]

Using the following command and parameters:

clumsy.exe --filter "ip.DstAddr == 65.164.221.80 or ip.DstAddr == 65.36.243.81" --lag on --lag-time 175

[jagt]

Thanks for the replies, I'll update the manual to include the commandline arguments soon :)
Pull requests are always welcomed.

[NikoMuffin]

Everything works now. The new version fixed the issue somehow.

Thank you both!!!

[NikoMuffin]

I know this is a bit late, but I would like to re-open this issue. It is definitely happening on a daily basis on Windows 10 64bit - all updates applied. I spoke way, waaaay too soon as the problem reappeared days after :(

Microsoft Office 2017
PIA (Private Internet Access VPN)
Priprinter
Sandboxie
VMWare Workstation <-- I am pretty sure this is not the cause . It happened long before I used this.

My gut tells me PIA somehow interfering, but I tried installing in a VM and it worked.
Clumsy works inside the VM but not on my main system.

It is impossible for the error to be appearing since I ULTIMATELY disabled UAC by using "enablelua" method. The app should run with a double click as admin.

I have tried everything under the sun and this is the only issue left with in Windows that I can't solve.

A restart seems to fix it and work properly, but it comes back CONSTANTLY and at random intervals.
It's really frustrating.... lol