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

    Access ISP router

    Scheduled Pinned Locked Moved Firewalling
    6 Posts 3 Posters 592 Views 3 Watching
    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.
    • QinnQ Offline
      Qinn
      last edited by

      Hi there

      due to another ISP I am mandatory using the ISP all-in-one router. So I have set the WAN interface of pfSense to DHCP and as it it is plugged in to a LAN port of this All-in-one device of the ISP it gets a RFC1918 ip adres (in this case 192.168.2.1). Is there a way to access this All-in-one device as they are in the same subnet?

      Cheers Qinn

      Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
      Firmware: Latest-stable-pfSense CE (amd64)
      Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

      NollipfSenseN 1 Reply Last reply Reply Quote 0
      • NollipfSenseN Offline
        NollipfSense @Qinn
        last edited by

        @Qinn Your ISP would know or use Google to find out how to set in bridge mode or how to access modem/router. Do you have to use theirs or can you buy your own?

        pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
        pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

        1 Reply Last reply Reply Quote 1
        • QinnQ Offline
          Qinn
          last edited by

          Thanks for your reaction, this is a double WAN situation and I am at current trying to create a load balance between them. Alas the modem-wifi-router from the ISP has no bridge mode setting, only a DMZ option, but this is just pro forwarding. So for now I will keep it using this setting.

          Cheers Qinn

          Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
          Firmware: Latest-stable-pfSense CE (amd64)
          Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

          1 Reply Last reply Reply Quote 0
          • S Offline
            SteveITS Rebel Alliance
            last edited by

            In Interfaces/WAN ensure "Block private networks and loopback addresses" is unchecked. Then you should be able to just enter the LAN IP of the ISP's router.

            I'm not sure I understand your comment about "same subnet" but the WAN side of the pfSense has to be a different subnet than the LAN side of the pfSense.

            Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
            Upvote ๐Ÿ‘ helpful posts!

            1 Reply Last reply Reply Quote 1
            • QinnQ Offline
              Qinn
              last edited by

              Thanks for reminding me, but this one is already checked.

              Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
              Firmware: Latest-stable-pfSense CE (amd64)
              Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

              1 Reply Last reply Reply Quote 0
              • S Offline
                SteveITS Rebel Alliance
                last edited by

                Hm, then it should work by typing the LAN IP of the ISP router. We have a similar setup at several clients and at my home. Perhaps in Status/System Logs/Settings check "Log packets matched from the default block rules in the ruleset" temporarily to see if pfSense is blocking you but as long as the outbound is allowed it should work.

                Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
                Upvote ๐Ÿ‘ helpful posts!

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