This “fixed itself”. Not sure what happened. I just reapplied the rules.

Regards,
Marty Godsey


From: Wei ZHOU <ustcweiz...@gmail.com>
Date: Tuesday, October 22, 2024 at 2:41 PM
To: users@cloudstack.apache.org <users@cloudstack.apache.org>
Subject: Re: Issue with Port Forwards in VR.
WARNING: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


Does the network have port forwarding rules on other public ips ? Do they
work ?



On Tuesday, October 22, 2024, Marty Godsey <mar...@rudio.net> wrote:

> Yes.
>
> I have an existing VR that is set up in the “normal” way. This is advanced
> networking without security groups.
>
> The VR has a public interface and an interface on an isolated network
> (private). This is not a VPC, just a VR.
>
> The public interface has a few IP addresses assigned to it. The private
> interface has one.
>
> On a public IP, I have opened a port to be allowed in the firewall:
>
> Source CIDR: 0.0.0.0/0
> Protocol: TCP
> Start Port: 475
> End Port: 475
>
> In the Port Forward settings, I have forwarded this port to a VM:
>
> Private Port Start: 475
> Private Port End: 475
> Public Port Start: 475
> Public Port End: 475
> Protocol: TCP
> Instance: Selected Instance (I know its listening)
>
> When I do a PCAP on the instance, I don’t see any packets on my port
> hitting the interface. I then checked the VR. I ran a PCAP on the pubic
> side, I see my packet hit the VR. I run a PCAP on the private side, I dont
> see my packet.
>
> I have rebuilt the network, rebooted the VR (even though rebuilding
> reboots it anyway), rebooted the instance.
>
> I have other port forwards configured in the same manner going to some
> other instances and they work fine. This router has not been touched since
> the update from 4.18.x to 4.19.x. This is the first time something is being
> added to it.
>
> The version of the software on the router is 4.19.0.2
>
> Regards,
> Marty Godsey
> Rudio, LLC
>
> Book Time: 
> https://atpscan.global.hornetsecurity.com?d=iycO2Cq8arlaCeNzu97XPiByx4FbtPhiamV9MzKBMtY&f=V6SmldKPkgCiZztsSqXFGxzSAOPjnCGInClwpinz8kkLck8HIk4_VgRoDqN_x2LU&i=&k=T9km&m=oNvBAE2e0tdDI61sixvKxYfLwdUEIFAz2dR4haDH1fZTUZAKe_q0oWVfE5l8Jo3rft33BDCMGcf_Tk6ByjkusuCff9YGq3YAeTf-8CMoQ6sRC_kkoFObMM3IVgzbXqlk&n=GnhvmsO3ZnTszvGJknh8OzzOXzxGQUxvRgDNX02EspdyMhUYbciQqV3UJCDUza30&r=riHZkyujaTUaSFy0atWO16cz1eaBUhLxZ0-hSRfdo1HLXU9Jq_2Xdck9exTzyq90&s=2681e47f410bac40ece712397dff92482429239190d22c9d84ee681f1a812433&u=https%3A%2F%2Fcalendly.com%2Frudio-martyg
> Support: supp...@rudio.net<mailto:supp...@rudio.net?subject=Rudio%
> 20Support>
> Ph: 859-328-1100
> The content of this email is intended for the person or entity to which it
> is addressed only. This email may contain confidential information. If you
> are not the person to whom this message is addressed, be aware that any
> use, reproduction, or distribution of this message is strictly prohibited.
> If you received this in error, please contact the sender and immediately
> delete this email and any attachments.
>
>
> From: Wei ZHOU <ustcweiz...@gmail.com>
> Date: Tuesday, October 22, 2024 at 11:09 AM
> To: users@cloudstack.apache.org <users@cloudstack.apache.org>
> Subject: Re: Issue with Port Forwards in VR.
> WARNING: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Marty,
>
> As I understand, #9053 is not a bug, it has been fixed by adding a network
> ACL for the private port.
>
> Can you share more details ?
>
> -Wei
>
> On Tue, Oct 22, 2024 at 4:52 PM Marty Godsey <mar...@rudio.net> wrote:
>
> > Hello,
> >
> > I see there is a bug filed for the issue I am seeing:
> >
> > https://github.com/apache/cloudstack/issues/9053
> >
> > I see this bug was closed, and there is a workaround. Has the issue
> itself
> > been addressed?
> >
> > I am on 4.19.0.2. This used to work, and the existing entries are
> working,
> > but new entries are not.
> >
> > Regards,
> > Marty Godsey
> >
> >
>

Reply via email to