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

    ATT Internet AIr

    Scheduled Pinned Locked Moved General pfSense Questions
    290 Posts 5 Posters 46.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.
    • A
      ahole4sure @stephenw10
      last edited by

      @stephenw10

      Back again lol
      Trying to get ready for the holidays so my side line IT job has suffered

      During the last week- both of the ATT moderns gateways have remained online ( one with the direct interface connection and the other with the VLAN connection ) - that is with the static IP configuration.

      Got around to a few fail over tests. Latest one tonight.
      Upon unplugging the WAN cable from the fiber modem fail over is successful but 2 issues remain

      1 ) the ATT modem just doesn’t seem to behave as far as DNS resolution (will ping IP addresses but can’t resolve DNS) - unless I check Enable DNS Forward Mode in the DNS Resolver settings. We explored this before but never figured out why

      1. possibly bigger issues - when I plug the fiber modem cable back in the Frontier fiber internet cable just won’t come back online. Even if I “reset all states” it won’t come back online. The only way I can get the fiber modem Tier 1 gateway back online is to full reboot pfsense.

      Ideas?

      Thank you

      G 1 Reply Last reply Reply Quote 0
      • G
        Gblenn @ahole4sure
        last edited by Gblenn

        @ahole4sure Hmm, how have you set up your resolver? Which interfaces have you selected in the list?

        70107964-699a-4c1e-8669-1426138c1bfa-image.png

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

          Hmm, odd. Unbound should be able to resolve directly via any outbound interface as long as it's selected. By default it tries to use all interfaces.
          Do you see any blocked traffic? Do you see states on port 53 when failed over to the AT&T modem?

          The Frontier gateway shows as off line? Or the NIC never links?

          A 1 Reply Last reply Reply Quote 0
          • A
            ahole4sure @stephenw10
            last edited by

            @stephenw10 @Gblenn

            I did not check for "blocked traffic". If I test again this PM would I just fail the WAN and then check the logs for the firewall? And where / how is best way to monitor or look for "states" on port 53?

            As far as the Frontier WAN interface -- the gateway on the status page shows red or "offliine" for much longer than expected (like a couple minutes), then it flashes to blue "unknown", then back to offline, then back to blue unknown -- ultimately after 4 or 5 minutes it settles in on blue unknown and just never links back up. I then tried reset states --- Ulitmately the only thing that lets it reconnect is just go to Diagnostics and choose "normal reboot". Back online , like normal, after the reboot.

            G 1 Reply Last reply Reply Quote 0
            • G
              Gblenn @ahole4sure
              last edited by

              @ahole4sure I guess the two problems are separate and not necessarily related. So on the first one about the DNS issue, which I responded to, have you checked the settings for the resolver? Which interfaces have you selected for it to use?
              In the forwarder, there is no such setting and I assume it's automatic as @stephenw10 suggests.

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

                Go to Diag > States and filter by :53

                What is logged in the System and Gateway logs when you reconnect the Frontier modem?
                How are you running the failover test? Physically unplugging something?

                A 3 Replies Last reply Reply Quote 0
                • A
                  ahole4sure @stephenw10
                  last edited by

                  @stephenw10 I'll have to retest and check the logs

                  And yes to fail - I just unplug the ethernet cord from the back of the frontier modem

                  1 Reply Last reply Reply Quote 1
                  • A
                    ahole4sure @stephenw10
                    last edited by

                    @stephenw10
                    Here are the screen shots of the info
                    Apologies and thanks for help!!

                    They start with states during failover
                    Show the DNS error on web browser
                    (the is with Forwarder Mode off under DNS Resolver settings)

                    Then shows what happens after waiting for Frontier WAN to come back up

                    Ultimately would not fully connect and come back up untill full reboot of pfsense

                    Screenshot 2024-12-18 161020.png Screenshot 2024-12-18 161006.png Screenshot 2024-12-18 160945.png Screenshot 2024-12-18 160930.png

                    Screenshot 2024-12-18 161345.png Screenshot 2024-12-18 161307.png Screenshot 2024-12-18 161110.png Screenshot 2024-12-18 161043.png
                    Screenshot 2024-12-18 161436.png

                    Screenshot 2024-12-18 161505.png

                    1 Reply Last reply Reply Quote 0
                    • A
                      ahole4sure @stephenw10
                      last edited by

                      @stephenw10 Screenshot 2024-12-18 162829.png

                      1 Reply Last reply Reply Quote 0
                      • A
                        ahole4sure @Gblenn
                        last edited by

                        @Gblenn
                        I have checked ALL for both

                        Is that correct?

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

                          Hmm, no DNS states shown there on states with ports starting with 53. You might need to filter differently to see that in the states.

                          I don't see the link state change in the logs there. Does it actually show the that when you reconnect the modem?

                          A 1 Reply Last reply Reply Quote 0
                          • G
                            Gblenn @ahole4sure
                            last edited by

                            @ahole4sure said in ATT Internet AIr:

                            @Gblenn
                            I have checked ALL for both

                            Is that correct?

                            Yes that is correct, and I'm starting to think that ATT is actually blocking access to authoritative servers... If this is true you either have to stick to Forwarder mode, or ask ATT to stop blocking. I wonder if there is some setting you can change for your account perhaps?

                            On the fiber issue, there are a few things that stand out to me.

                            1. Gateway shows an IP but status is pending. So that IP is probably cached data in pfsense, the link is up (eth to frontier box) but pfsense has not verified the DHCP lease?

                            2. I notice you have IPv6 enabled on the fiber WAN. Could that cause issues? Try disabling it and see if that makes any difference when testing?

                            3. Have you tried pulling the fiber instead of the ethernet cable to pfsense? If that is possible to do?
                              Keeping the physical link up on pfsense interface thoughout the test... If there is something on that side that isn't really working as it should?
                              If you look at the dashboard instead of Status / Gateways, you will also see the negotiated settings for the interface. Does that seem ok, and is it the same before and after pulling and reconnecting the cable?

                            1 Reply Last reply Reply Quote 0
                            • A
                              ahole4sure @stephenw10
                              last edited by

                              @stephenw10
                              Yes it does show this when I reconnect the Frontier fiber modem -- I will have to try it again this PM to try to get the states again
                              As far as ATT - wonder if @Gblenn is correct - I have been reading that ATT has some sort of DNS assist that could be hijacking my DNS queries -- not sure how to determine that.

                              https://gist.github.com/CollinChaffin/24f6c9652efb3d6d5ef2f5502720ef00

                              Image 12-19-24 at 10.04 AM.jpeg

                              @Gblenn
                              I will retest with IPv6 disableld tonight ! I see (after some ressearch) that ATT could be hijacking the DNS. I will look into this. Thanks

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

                                Yes if they're redirecting DNS that would break the resolver.

                                1 Reply Last reply Reply Quote 0
                                • G
                                  Gblenn @ahole4sure
                                  last edited by Gblenn

                                  @ahole4sure Why can't ISP's just leave things alone... I'm assuming, since you run the modem(s) in passthrough mode, that it's not in the device that is being blocked, or is it?
                                  I'm thinking you need to log in to their portal (your accounts) to disable that "helper feature"...

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    ahole4sure @Gblenn
                                    last edited by

                                    @Gblenn @stephenw10

                                    So am trying to leave things in situ as they have been setting and working (ie the ATT modems)
                                    They are supposoed to be accesible from my LAN (and they were right after I re setup my pfsense) - via 192.168.2.1 and 192.168.3.1 (set in the device as the configuration addresses)
                                    Through VIPs

                                    For some reason I can't access either of those VIPs any longer --

                                    I was trying to see if I could change the DNS settings we were discussing.

                                    I can ping both 192.168.2.1 and 192.168.3.1 but can't access via web browser

                                    Screenshot 2024-12-19 180100.png

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

                                      Do you have outbound NAT rules in place for those?

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        ahole4sure @stephenw10
                                        last edited by

                                        @stephenw10

                                        Just auto
                                        But looks like it’s there ????IMG_0398.png IMG_0399.png

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

                                          Well it looks like you have conflict with the 192.168.2.10 VIP. You have that subnet on an internal interface too it appears since it's included in the auto rules.

                                          You should also have manual rules to translate to the VIPs for traffic from LAN to the modem.

                                          A 3 Replies Last reply Reply Quote 0
                                          • A
                                            ahole4sure @stephenw10
                                            last edited by ahole4sure

                                            @stephenw10

                                            I think it is where I set up a static route trying to do what @Gblenn had suggested back in this thread previously

                                            So the static route must have done the auto rule

                                            Just so I don’t screw it up, after I have now deleted the static route, how should I set up the the outbound rule?

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