• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Cannot access private IP's on Comcast Router

Scheduled Pinned Locked Moved NAT
1 Posts 1 Posters 232 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    jab99
    last edited by Apr 14, 2021, 12:00 AM

    Our setup is to have a Comcast Business router supplying a public IP to our pfSense appliance. A VOIP provider had difficulty hosting their equipment behind the pfSense firewall. There were complaints of garbled speech and dropped calls. The provider moved the pbx and all phones to the Comcast side on network 10.1.10.0/24.
    This all works perfectly except for when we want to access the pbx from behind the LAN.

    First, I tried to access the Comcast Web console from the LAN and could not. After some research, I created a VIP and Outbound NAT. Now browsing to 10.1.10.1 works as expected.

    The pbx is located at IP 10.1.10.200 and is pingable from the LAN. Unfortunately, the Web interface does not work. Checking the config on Comcast, they have port forwards setup for TCP/UDP 5060, TCP 443, UDP 10000-15000, TCP 80, and TCP 5061.

    I checked the Outbound NAT and it is set to allow any protocol from the internal LAN to the destination 10.1.10.0/24. What I don't understand is why the .200 address is not reachable via http or https?

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received