• Port forward issue to PBX

    NAT
    10
    0 Votes
    10 Posts
    1k Views
    E

    @emc

    This issue has been fixed. NAT is working. It was a firewall issue in the PBX. I've whitelisted the IPs on the PBX's firewall and it works. Thank you everyone for your help.

  • 0 Votes
    3 Posts
    642 Views
    stephenw10S

    Technically you could do it by running pfSense as a virtual machine in Windows using hyper-V or VBox etc. But pfSense is a complete operating system, it cannot run as an application on your desktop. It expects to be running on it's own dedicated hardware but running virtualised can also work.

    Steve

  • Squid URL based proxy with port redirects

    Cache/Proxy
    1
    0 Votes
    1 Posts
    504 Views
    No one has replied
  • 0 Votes
    5 Posts
    962 Views
    stephenw10S

    Yeah you should be able to use either HAProxy or reverse Squid to redirect requests based on the host headers to different internal servers. Or different ports on the same server.

    https://docs.netgate.com/pfsense/en/latest/packages/haproxy-package.html

    https://youtu.be/FJSHMyrd29E

    Steve

  • Forwarding and ping from WAN dont work. (SOLVED)

    NAT
    27
    0 Votes
    27 Posts
    7k Views
    johnpozJ

    Nat reflection is ALWAYS the worse option to choose.. I don't understand why anyone would ever want to nat reflect..

    if host.domain.tld is on the same network next to you - then why would you not just resolve host.domain.tld to that IP.. Why would you ever want to go to the public IP to be reflected back in??

    As to forwarding port X to port Y.. That is always a work around in itself to all to go to the same service with the limitation of napt and only 1 public IP, etc.

    If you want to go to host.domain.tld:port then go there where host.domain.tld resolves to the local IP and not the public ip..