When using AdGuard VPN, access to the local network by VST plugins will be blocked, causing the plugins to stop working or leading to crashes.

### Please answer the following questions for yourself before submitting an issue.

- [x] I checked the [knowledge base](https://adguard-vpn.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard VPN version

2.9.6

### Environment

```markdown
- OS:Windows 11 Home 25H2
- Other network-level software: AdGuard ad blocker
```

### Which DNS server do you use?

AdGuard DNS

### Custom DNS

_No response_

### Use Wintun

- [ ] yes, I do

### Issue Details

Steps to reproduce:
1.Launch Steinberg Cubase (14 Pro).
2.Insert Sonible Smart:reverb2 into two or more tracks of your choice in Cubase.
3.You will notice that some of the parameters displayed in the Smart:reverb2 GUI disappear.

### Expected Behavior

Sonible's Smart:reverb2 features a function called inter-plugin communication (IPC), which allows multiple instances to call and control one another. This enables the use of features such as grouping, where multiple Smart:reverb2 effects can influence one another.

### Actual Behavior

AdGuard VPN blocks Smart:reverb2’s inter-plugin communication (IPC), which renders most of its features unusable and can cause the plugin to crash.
Since Smart:reverb2 does not have an EXE file (.vst3), it cannot be added to the VPN exclusion list.

### Screenshots

Screenshot 1

### Additional Information

AdGuard VPN Support asked me to report this issue directly to the development team via this GitHub issue, so I am submitting this issue.
Sonible’s support team informed us that IPC uses UDP port 5670.