Seems al fine (port forwarding AND static NAT) on 4.4.1. Just tested.
@Rohit - Is it too late now to actually submit a bug for this port
forwarding - and possibly backport to 4.3.2 ?
Thanks
On 11 December 2014 at 10:25, Andrija Panic wrote:
> Static NAT (all port forwarding) - also broken, all
Static NAT (all port forwarding) - also broken, all connections to private
IP on VM, seems to come from main Public IP of VPC VR, instead of real
client's IP... :(
Will test 4.4 and possibly 4.5rc now...
On 10 December 2014 at 13:56, Andrija Panic wrote:
> Marcus, for outbound I meant Source NA
Marcus, for outbound I meant Source NAT, sorry... Will check other Static
NAT (all port forwarding) and will also test sinle port forwarding stuff on
4.4 or possibly 4.5. I see this as a serious issue for any VDC user... so
will check...
On 9 December 2014 at 17:34, Marcus wrote:
> Yeah, that se
Yeah, that seems strange. I don't recall it working that way in the past.
It uses the standard iptables DNAT, and I believe the same methods as
static NAT to rewrite the destination ip. Do you see the same behavior with
static NAT on routing incoming traffic to a particular VM?
Just to make sure w
Hi Marcus,
static NAT (outound connections) works fine - when internal VM access
internet, it's source address is replaced with the MAIN public IP of the
VPC VR (call it IP1 in my example - x.x.x.x) - so all fine.
Then I have additional public IPs to be able to do port forwarding... -
when I do po
Or wait, you're not using static NAT, you're just using port forwarding,
correct? Everything will be NAT'ed outbound to the VPC router's public IP
per SNAT, like one would expect behind a NAT. You could force outbound to
match the IP that the port forwarder is on, but what if you have multiple
IPs
It sounds like some iptables rules got broken at some point for the static
NAT, and since there's still a catch-all SNAT for outbound it gets caught
by that and still keeps working, but is broken in a subtle way that goes
unnoticed.
On Mon, Dec 8, 2014 at 2:55 PM, Andrija Panic
wrote:
> And just
Hi Erik - yes I know of shared network - been using that, but want to move
behind VPC to organize stuff a little bit more... ok, for loadbalancing -
did not check, as that is not my problem at the moment.
But port forwarding really is - this is really bad implemenation or bug in
my opinion, never
On Mon, Dec 8, 2014 at 11:55 PM, Andrija Panic
wrote:
> And just to spice things a little bit, ALL remote connections appears to
> come from main Public IP of the VPC VR.
> So we can not block some stuff on firewall onVM (while doing port
> forwading) because all connections appear to come from m
On Mon, Dec 8, 2014 at 11:42 PM, Andrija Panic
wrote:
> Hi,
>
> when doing port forwarding on VPC VR - port 80 - when some client access
> web site - only the main Public IP of the VPC is logged in apache access
> logs as remote IP.
>
> Why is this behaviour - and can this be changed ?
> My under
And just to spice things a little bit, ALL remote connections appears to
come from main Public IP of the VPC VR.
So we can not block some stuff on firewall onVM (while doing port
forwading) because all connections appear to come from main Public IP of
the VPC VR.
This is terrible design/bug - can
Hi,
when doing port forwarding on VPC VR - port 80 - when some client access
web site - only the main Public IP of the VPC is logged in apache access
logs as remote IP.
Why is this behaviour - and can this be changed ?
My understanding is that this is kind of bug (unless needed for some other
rea
12 matches
Mail list logo
