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

    Resolved: T-Mobile CellSpot connectivity issues

    Scheduled Pinned Locked Moved Firewalling
    54 Posts 5 Posters 24.3k 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.
    • DerelictD
      Derelict LAYER 8 Netgate
      last edited by

      If you have states to them and two-way traffic to them and no connection requests are seen by them, not sure what to tell you really.

      You could packet capture but all you will be able to see is probably some DNS then the outside of an IKE/IPsec tunnel. You might do it and see if things seem to break down when packet sizes increase past about 1400 or something.

      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
      • chpalmerC
        chpalmer
        last edited by

        Tell us more about the hardware you are running pfSense on..

        Especially the interface types.

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

          @chpalmer:

          @Asterix:

          What I have not tried yet is force opening port 53 for the CellSpot even though the VoIP subnet (like the LAN) is wide open. I have even tried keeping on default LAN on a fresh plain install.. same issue.

          Your interface the cellspot is on needs full access to the internet.  Basically it needs to be able to surf to anything it wants to. Rule=  Voipnet  any port  any destination any port. Block nothing if you have not already.  You really need nothing on WAN for it at all.

          Other thing-  Go to  System/Advanced/Firewall&NAT  TFTP Proxy.  Enable that for your VOIP interface.

          Another thing you could try is to make your devices port 4500 static in the outbound NAT page.

          Im off to work in the field today so good luck!

          FINALLY !!!!  I can see the counters increasing steadily !!

          It wasn't the TFTP Proxy.. but the MFS (Maximum Frame Size) on the network. Not sure why this happened now in pfSense v2.3.2 but I have the network config on 9216 (9000K) since 2012 with zero issues and the CellSpot worked just fine all these months. I installed an older v2.2 copy of pfSense last night on a backup server and the CellSpot connected fine once I restored the old config on it.

          Definitely a frame size issue on v2.3.2. I confirmed this twice by changing the MFS to 9K and see the CellSpot disconnect. Tried putting a 9000 MTU on the interface but it didn't help.

          states.jpg
          states.jpg_thumb

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

            ALL devices on a jumbo frame segment have to support, and be configured for, the jumbo frame size. Not quite sure how you are doing that on the cell spot with no config knobs.

            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
            • A
              asterix
              last edited by

              Yeah, the CellSpot has 100Mbps port and not gigabit.

              Along with changing the MFS to 1518 I had to enable (uncheck) the default set on the interface : Hardware TCP Segmentation Offloading & Hardware Large Receive Offloading.

              Since I have intel 4 port NIC, I thought enabling it wouldn't hurt.

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

                @Asterix:

                Yeah, the CellSpot has 100Mbps port and not gigabit.

                Along with changing the MFS TO 1518 I had to enable (uncheck) the default set on the interface : Hardware TCP Segmentation Offloading & Hardware Large Receive Offloading.

                Since I have intel 4 port NIC, I thought enabling it wouldn't hurt.

                Intel drivers are generally just fine with those two checked. Is it em, igb or ?? Are you sure it's a real intel card and not a far-east knockoff?

                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
                • A
                  asterix
                  last edited by

                  It's igb. Yeah it was brand new ordered through corporate supplies.

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

                    Thousands and thousands and thousands of igb ports out there running 2.3.2 with those two options disabled (checked) by default. Zero issues as far as I know.

                    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
                    • A
                      asterix
                      last edited by

                      Yeah, the MFS setting resolved my issue. Enabling the other two options was just a test to see if it helped.

                      1 Reply Last reply Reply Quote 0
                      • chpalmerC
                        chpalmer
                        last edited by

                        Congrats!  Good info to know for others that come along as well with similar issues.

                        :)

                        Triggering snowflakes one by one..
                        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                        1 Reply Last reply Reply Quote 0
                        • L
                          Leonardo Lowry
                          last edited by

                          Since T-Mobile cellspot is no longer available, I wonder if anyone has had good experience with signal boosters like the ones shown here: https://www.signalbooster.com/pages/tmobile

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

                            @Leonardo-Lowry

                            Do your phone and carrier support Wifi calling? I have lousy cell service in my home but, with Wifi calling, I now have an excellent signal. Added bonus is data does not count against my cell phone.

                            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.