No Access to specific machines after Update, including ports 8000,8080,8100

[PotatoCarl]

Hi
since the latest update, I cannot access from my VPN services that are available at ports 8000, 8080, 8100 etc.
On hosts, providing those services, I cannot even get a ping (either direction) through or login.

This worked right before the last update (24.1.9_hf4).

I did not change anyhting a the firewall rules. I tried to loosen the rules, but no effect.

Specifically one virtual machine running in the main net 192.168.1.33 is not accessible. On any port.
My VPN runs (openVPN) at 192.168.21.x
I cannot ping in either direction or connect.

The Firewall seems to accept the cooection  ("pass") from the VPN - after that it is silence.

Within the main main net, the hosts in question (192.168.1.33) is reachable on any port, ping, ssh etc.

It seems as the packages send are just eaten up from the firewall.

I am runnign out of ideas how to find the problem. The hosts in question is a VM, but on that machine a number of identically configured VMs are present and all work.

Any idea where that comes from and how to solve?
Thanks.

[tiermutter]

I had a similar issue (not sure if this is related to the update) where I could no longer reach some machines via VPN on Windows client (Android client was not affected).
I am sorry I no longer know what exactly I changed, but I made changes in VPN server regarding redirect gateway option. I believe I changed it from 'local' to 'none', already having the pushed routes configured.

[PotatoCarl]

I have spent now a lot of time in these matters. But no results.

I am at a point were I can assume the following:

I run several OpenVPN Servers e.g. on port 1195, 1196, 443. Port 443 (TCP) operates on both internet landlines.

It seems as when I connect via port 443 one, and exactly one IP in the internal network of the VPN Firewall is not accessible. ALL other ports work fine. When I reconnect and connect to UDP Port 1195 for example - I can access it.

I am more than somewhat confused about it. All openVPN servers have different IP ranges (and are there for exactly this purpose - being stuck in a hotel that blocks our IP ranges, so I tried to avoid that problem by having differen VPNs that would allow in any case to use a private network).

I do see that the access from the VPN to the firefill is transferred to the IP address ("pass"). However, it does not seem to arrive.

Maybe it is of importance that the host "missing" is a virtual machine - on the other hand, all other virtual machines work fine.

It would be great if anybody has an idea where the problem could be based or at last, how I might be able to trace it. Currently my only option is to reconnect the VPN until I see the host again...