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

    Web GUI access to cable modem

    Scheduled Pinned Locked Moved
    NAT
    3
    5
    1.0k
    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.
    • B
      Bizbot
      last edited by

      Please excuse my ignorance as I have just installed my first pfSense 2.2.4 instance yesterday. I am having trouble establishing rules/NAT to enable access to my cable modem which sits on a different subnet on the other side of the firewall, obviously connected to the WAN port. The cable modem in question hosts a web GUI with a static IP of 192.168.100.1 which differs from my internal subnet of 192.168.1.0/24.

      Following the 'Configure NAT' step in the below article still has not enabled access to the cable modem. I ignored the 'Configure a new Interface' step in the article as it seems to only apply to PPPoE/DSL connections.
      https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

      Any help would be greatly appreciated. I have included a simple map of my network setup and a screenshot of the outbound NAT rule I have created below.

      Network map of current setup:

      Outbound NAT rule I currently have in place and expect should work:

      TL;DR: How do I enable access the my cable modems web GUI from inside the firewall which is on a different subnet?

      "I like offending people because I think people who get offended, should be offended."
      -Linus Torvald

      1 Reply Last reply Reply Quote 0
      • B
        Bizbot
        last edited by

        I have done some research in the logs and have noticed pfSense is saying it cannot resolve the IP address of my cable modem.

        "I like offending people because I think people who get offended, should be offended."
        -Linus Torvald

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          @Bizbot:

          I have done some research in the logs and have noticed pfSense is saying it cannot resolve the IP address of my cable modem.

          What are your firewall rules on LAN?

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • B
            Bizbot
            last edited by

            "I like offending people because I think people who get offended, should be offended."
            -Linus Torvald

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              Honestly, the NAT is useless. In fact, it's breaking things, IMHO. The "cannot resolve" is not an error.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.