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

    WAN not connecting with bridge modem rogers cable

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 6 Posters 2.7k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      If they both have the same gateway then you would not be able to route traffic to them differently. It's not really valid.

      Steve

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @stephenw10
        last edited by

        @stephenw10

        My gateway on pfsense is 99.246.124.1, but 99.246.150.1 on my 2nd connection, so they are completely separate subnets. Both have /23 subnet mask. The MTU on my 2nd connection is 1280, vs 1500 on pfsense.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • JKnottJ
          JKnott @learner
          last edited by

          @learner

          As I mentioned, I used to be able to connect, but that failed with 2.6.0, IIRC. Ping works, but OpenVPN doesn't. However, it does if I tether to my cell phone.

          Here's what I get when I try to connect via my 2nd connection. Similar would happen with ssh.

          fab0b81c-da2e-4696-a4b5-6e23f343840b-image.png

          packetcapture.cap

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, that's between your two WANs somehow? I could definitely see that failing...

            JKnottJ 1 Reply Last reply Reply Quote 0
            • JKnottJ
              JKnott @stephenw10
              last edited by

              @stephenw10

              The thing is, it used to work, prior to 2.6.0. Those are 2 completely independent subnets. After I updated to 2.6.0, I wasted a lot of time trying to understand what was wrong with my configuration, until I realized I had done nothing wrong. It was pfsense or perhaps FreeBSD that failed.

              PfSense running on Qotom mini PC
              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
              UniFi AC-Lite access point

              I haven't lost my mind. It's around here...somewhere...

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Between 2 pfSense devices then?
                Hard to see how that could have worked between two interfaces on the same device...

                JKnottJ 1 Reply Last reply Reply Quote 0
                • JKnottJ
                  JKnott @stephenw10
                  last edited by

                  @stephenw10

                  Between pfsense and a notebook computer. I have a ThinkPad which I use for testing. It runs Linux and prior to pfsense I was also using Linux for a firewall. It worked then and after I moved to pfsense about 5.5 years ago, it continued to work. Then 2.6.0...

                  PfSense running on Qotom mini PC
                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                  UniFi AC-Lite access point

                  I haven't lost my mind. It's around here...somewhere...

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, I can't think of anything in 2.6 that would cause something like that.

                    If it come in on the WAN it will send replies back to the WAN gateway. There could be an issue with the ISP moving that traffic both ways over the link, assuming the gateway is at the ISP end.

                    There were some changes to that code in 2.5.X but 2.6 retains that.

                    Steve

                    JKnottJ 2 Replies Last reply Reply Quote 0
                    • JKnottJ
                      JKnott @stephenw10
                      last edited by

                      @stephenw10

                      Well, as I said, it worked before. The last time it did was just a couple of days before I updated. As the packet capture shows, the packets are getting through. I had a fair bit of discussion about this in the OpenVPN section just after 2.6.0 came out. Ping works, but I don't know enough about OpenVPN or ssh to take it further.

                      So, when I test, I now have to tether to my cell phone, when I didn't before.

                      PfSense running on Qotom mini PC
                      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                      UniFi AC-Lite access point

                      I haven't lost my mind. It's around here...somewhere...

                      1 Reply Last reply Reply Quote 0
                      • JKnottJ
                        JKnott @stephenw10
                        last edited by

                        @stephenw10

                        Except it failed overnight, when I changed versions. As the capture shows, there are 2 gateways involved, so there should be no conflict that way and my cell phone is with the same company. I do recall there were some OpenVPN changes when this happened. I redid my config to accommodate them and also because I wasn't thrilled with what I had.

                        Correction, this came in with pfsense 2.5.0, not 2.6.0. I'm currently running 2.5.2. 2.5.0 came out on Feb. 17 and I was inquiring about the the OpenVPN version in openSUSE on Feb. 24, to see if that might be the cause of the problem.

                        PfSense running on Qotom mini PC
                        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                        UniFi AC-Lite access point

                        I haven't lost my mind. It's around here...somewhere...

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