I also have this problem, it effects running vPBX/VoIP services behind a VR.
In fact any service that requires a view on incoming IPs and domain names.
For example fail2ban will block ALL access to ssh because it only ever sees the
VR IP address.
Upgrading to 4.3.2 did not fix it.
This needs f
Hi,
is anybody willing to share the result from the folowing command, run in VR
(VPC VR):
iptables -t nat -nvL
This should preferable be run from SSH-to-VR, instead of
ConsoleProxy-to-VR, because of nice output over SSH.
It seems in 4.3.0 and 4.3.2, SNAT is done on ALL incoming connections, no
