Multiple PUBLIC IP leashed line setup for NAT

Hi .
I'm having trouble trying to get one of the Public IP(Alias) to be nat onto voice subnet interface.
Here's the diagram below.
Network Diagram.

Here's what i configure for the Leased IP Line.

For voice LAN interface Subnet i configure as below.

As for rule. I did it as below.

I have trouble reaching 202.111.122.113 via 4000 to 4008.

May i know which settings i did wrong or is there something i left out ?




Added TAGs
[edited by: emmosophos at 7:47 PM (GMT -8) on 25 Feb 2021]
Parents
  • Hi ywillie,

    As per configuration screenshot, Use Outbound Address seems to be incorrect as this rule is for allowing traffic from WAN(XG-A1) to PABX so there is no need for NATing it with IP 202.111.122.113, you can either uncheck "Rewrite source address" of select Rewrite source address as MASQ instead of 202.111.122.113.

    Regards,
    Hardik R

     
  • I've found the issue. The problem indeed came from the tplink router itself.
    Today i remove the router and plug a laptop straight to the lan port of the firewall under interface A5.
    I even configured the laptop static with an ip 172.20.110.11/24 matching the Pabx system's ip.
    I downloaded port listener on the laptop and have it listen on port 4001 and other ports each time to test the connection.
    Everything went through from externally without issue.
    The public ip had actually successfully nat to the internal ip .
    The only problem is the tplink router isn't returning the packets back . It's dropping the packets at some point.

Reply
  • I've found the issue. The problem indeed came from the tplink router itself.
    Today i remove the router and plug a laptop straight to the lan port of the firewall under interface A5.
    I even configured the laptop static with an ip 172.20.110.11/24 matching the Pabx system's ip.
    I downloaded port listener on the laptop and have it listen on port 4001 and other ports each time to test the connection.
    Everything went through from externally without issue.
    The public ip had actually successfully nat to the internal ip .
    The only problem is the tplink router isn't returning the packets back . It's dropping the packets at some point.

Children
No Data