, 2015 11:29:54
Subject: Re: SNAT and remote IP problem
I reacall this was fine in clean 4.4.0 or 4.4.1/2cant remember any
more...
but anyone willing to share their VR output, as I asked, will I guess help
us greatly...
On 18 March 2015 at 12:28, Erik Weber terbol...@gmail.com wrote
Sent: Wednesday, 18 March, 2015 11:29:54
Subject: Re: SNAT and remote IP problem
I reacall this was fine in clean 4.4.0 or 4.4.1/2cant remember any
more...
but anyone willing to share their VR output, as I asked, will I guess
help
us greatly...
On 18 March 2015 at 12:28, Erik
I reacall this was fine in clean 4.4.0 or 4.4.1/2cant remember any
more...
but anyone willing to share their VR output, as I asked, will I guess help
us greatly...
On 18 March 2015 at 12:28, Erik Weber terbol...@gmail.com wrote:
Has anyone checked if this is present in 4.5? If so we should
Has anyone checked if this is present in 4.5? If so we should aim to have a
fix available with 4.5.1
--
Erik
On Wed, Mar 18, 2015 at 10:47 AM, Paul Shadwell shadw...@me.com wrote:
I also have this problem, it effects running vPBX/VoIP services behind a
VR.
In fact any service that requires
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
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,
