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

    Please help me

    Scheduled Pinned Locked Moved Routing and Multi WAN
    15 Posts 2 Posters 5.0k 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.
    • F
      FJSchrankJr
      last edited by

      Ok, try to change the squid port from 8080 to say 8081. I don't know too much about squid but see if that fixes your problem.

      FJS - Embedded Systems Engineer
      Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
      ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

      1 Reply Last reply Reply Quote 0
      • A
        aungzawmoe
        last edited by

        Changed to 8081 and default squid port 3128 and retry.
        But nothing change.
        :(

        Another way?

        Thanks

        1 Reply Last reply Reply Quote 0
        • F
          FJSchrankJr
          last edited by

          Yes, I took a look at your diagram again.

          I think I see an issue. What type of VOIP/Router is being used between the SAT modem and pfSense?

          FJS - Embedded Systems Engineer
          Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
          ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

          1 Reply Last reply Reply Quote 0
          • A
            aungzawmoe
            last edited by

            It has no brand name. Part of IPStar service.

            Sat Modem ip is 172.25.25.100 with DHCP.
            Voip router WAN side get 172.25.25.101 from Sat modem.
            Voip router LAN address is 192.168.123.1 with DHCP.
            PFSense get 192.168.123.150 from Voip router.
            Like this

            172.25.25.100 –------ 172.25.25.101 (VOIP+Router) 192.168.123.1 --------- 192.168.123.150  ( Pfsense ) 192.168.100.2 -------- Clients ( DHCP 192.168.100.100 to 150 )

            If I replace pfsense box with another computer, I get 192.168.123.151 from Voip router
            and I can access modem's panel.

            172.25.25.100 -------- 172.25.25.101 (VOIP+Router) 192.168.123.1 --------- 192.168.123.151 ( Another Computer )

            1 Reply Last reply Reply Quote 0
            • F
              FJSchrankJr
              last edited by

              @aungzawmoe:

              It has no brand name. Part of IPStar service.

              Sat Modem ip is 172.25.25.100 with DHCP.
              Voip router WAN side get 172.25.25.101 from Sat modem.
              Voip router LAN address is 192.168.123.1 with DHCP.
              PFSense get 192.168.123.150 from Voip router.
              Like this

              172.25.25.100 –------ 172.25.25.101 (VOIP+Router) 192.168.123.1 --------- 192.168.123.150  ( Pfsense ) 192.168.100.2 -------- Clients ( DHCP 192.168.100.100 to 150 )

              If I replace pfsense box with another computer, I get 192.168.123.151 from Voip router
              and I can access modem's panel.

              172.25.25.100 -------- 172.25.25.101 (VOIP+Router) 192.168.123.1 --------- 192.168.123.151 ( Another Computer )

              in pfSense, go in to the WAN interface and uncheck the option for block private IPs then save and try it now.

              That should fix it. Just realized 172.16.0.0 through 172.31.0.0 range is private.

              FJS - Embedded Systems Engineer
              Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
              ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

              1 Reply Last reply Reply Quote 0
              • A
                aungzawmoe
                last edited by

                :( :( :( :( :(
                Already tried. Can't solved.

                I think there has no way to resolve.

                1 Reply Last reply Reply Quote 0
                • F
                  FJSchrankJr
                  last edited by

                  Ok, well I will give it some more thought and figure out where the issue is. We'll figure it out, don't worry.

                  FJS - Embedded Systems Engineer
                  Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
                  ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

                  1 Reply Last reply Reply Quote 0
                  • F
                    FJSchrankJr
                    last edited by

                    Ok, what about the VOIP Adapter/Router, can you login to that admin page from the LAN side of pfSense? Trying to figure out where it's happening.

                    FJS - Embedded Systems Engineer
                    Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
                    ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

                    1 Reply Last reply Reply Quote 0
                    • F
                      FJSchrankJr
                      last edited by

                      Have you considered testing by removing the VOIP Router and connecting pfSense WAN directly to the sat modem, you can always use DHCP/NAT in pfSense.

                      If you need VOIP, connect the VOIP Router in after pfsense.

                      At least try this to test. Also, is the gateway properly set in pfSense for the WAN interface?

                      FJS - Embedded Systems Engineer
                      Pictures are worth a thousand words, but <u>posting config.xml backups are worth 10,000</u>.  Alter the IPs, change anything revealing but leave subnets intact. Use find and replace. Please try to keep it brief on the description.
                      ALWAYS disable TSO  & LRO EXCEPT CHKSUM IF SUPPORTED. TSO/LRO breaks traffic, pf scrub and this goes for any passive device inline

                      1 Reply Last reply Reply Quote 0
                      • A
                        aungzawmoe
                        last edited by

                        Ok, I will test and report.

                        Thanks

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