Re: Skype.exe
Lihue Barken
Maybe your Image File Execution Options is blocking execution of Skype.exe. Go the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options, find a key named skype.exe then delete the Debugger value.
I created an extra shortcut pointing to the skype.exe application and I added the /Shutdown parameter, very easy to close skype using that icon. This is what I used: "C:\Program Files\Skype\Phone\Skype.exe" /shutdown
One thing that has annoyed me is that when you deny an exe if that exe changes it asks again if you want to allow it access. This is most noticable with the Windows yourphone.exe (I think that is the name, my apps list got cleared as I just updated). It seems as if Microsoft changes that every other day and it triggers a new prompt.
microsoft.sharepoint.exe
lenovo.modern.imcontroller.pluginhost.settingsapp.exe
lenovo.vantage.addinhost.x86.exe
lenovovantageservice.exe
lenovovantage.exe
officeclicktorun.exe
hxtsr.exe
microsoft.sharepoint.exe
microsoft.photos.exe
miro.exe
officeclicktorun.exe
gamebar.exe
winstore.app.exe
slack.exe
skype.exe
Please fix this soon, I love GlassWire but this is my least favorite thing about the program. Once I get everything customized and set up properly it requires too much of my attention, I want it to run in the background and only alert me of something when absolutely necessary.
Briefly, can you suggest a more appropriate UDP flood threshold value (see my other recent message above)? I have the default of 500, and have just changed this to 50000, but I'm not sure if this effectively renders the protection pretty useless. I'd appreciate any thoughts you may have.
Unfortunately with the flood thresholds they have to be tuned per network so you have two choices. Start marching down in increments from your known too high then back off when you hit the legitimate traffic bump. Or march up incrementally from the known bad until the legitimate traffic is clear.
How are you connected to the internet? If you are connected with a PPP interface, all my testing has shown no matter what you do, the DSCP and COS marking will not be retained once the traffic leaves the SRX via PPP. Many ISP will actually honour some basic DSCP or COS tags. For the SRX you would need a DHCP connected internet interface for this to work end-to-end.
There are a number of ways to achieve this but I believe the simple approach is always the best approach, yes you can certainly achieve the results configuring forwarding-classes, firewall filters, traffic-control-profiles, shaping or a combination but a simpler approach might just be a policer? Perhaps allow 90Mpbs for all bandwidth and unlimited or 10Mbps for voice?
I assume you are using the windows client? If so then create a group or local policy to classify traffic on the workstations as per this article, notice the application option in step 5, you should actually specify the skype.exe in the policy and set all DSCP marking to EF (46) for that application following the article.
Secondly you will configure your firewall policy to act on those markings as follows (remember to apply the filters to the interfaces required), you don't strictly speaking require a source address, but its just good practise to be as specific as you can be:
This will then give you a process to identify the traffic as well as a way to process it on the SRX. Obviously you can use Wireshark to debug all of this and perhaps start with an FTP client to generate traffic and confirm the speed limits.
Lastly you would need to consider all the "other" traffic, if other traffic is still able to overload the interface the above will be pointless, so its important to create another policer to capture the "all-else" and limit that traffic to allow bandwidth for voice.
59fb9ae87f