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

    pfSense mangling packets?

    Scheduled Pinned Locked Moved General pfSense Questions
    53 Posts 4 Posters 3.6k 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

      Try opening the Firefox debug console and looking at the network connections/timing while doing that.

      T 1 Reply Last reply Reply Quote 0
      • T
        Tueem @stephenw10
        last edited by

        @stephenw10 Here is the entire log:
        04e5adc4-a23d-448e-ba1c-87b0e045d290-image.png

        As you can see the result is missing css

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

          It looks like you have a an adblocker and it's blocking the css file along with all the actual ads.

          T 2 Replies Last reply Reply Quote 0
          • T
            Tueem @stephenw10
            last edited by

            @stephenw10 hmmm thats weird. I'm gonna ask the VPN provider because I definitely don't have one

            1 Reply Last reply Reply Quote 0
            • T
              Tueem @stephenw10
              last edited by

              @stephenw10 I've asked the VPN provider and waiting for an answer but I don't think that will be the problem since im using google dns and the same issues happens if I use another Wireguard VPN. I'm guessing its some kind of wireguard problem

              w0wW T 2 Replies Last reply Reply Quote 0
              • w0wW
                w0w @Tueem
                last edited by

                @Tueem
                Do you have IPv6 enabled and working?

                T 1 Reply Last reply Reply Quote 0
                • T
                  Tueem @w0w
                  last edited by

                  @w0w no I don't

                  w0wW 1 Reply Last reply Reply Quote 0
                  • T
                    Tueem @Tueem
                    last edited by

                    @Tueem I just confirmed, it's definitely not the VPNs fault. I booted up a quick instance of OpenWrt and there having my server routed through the VPN works fine.

                    T 1 Reply Last reply Reply Quote 0
                    • w0wW
                      w0w @Tueem
                      last edited by

                      @Tueem
                      Interesting. I have similar issues with the same addresses 13.x.x.x and pfSense when I use a specific PPPoE connection, but the problem only arises when I use IPv6, which I also obtain via DHCP. Interestingly, everything works fine without pfSense in the loop. There must be something in pfSense itself, and in my case, IPv6 is just the trigger.

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

                        Hmm, but you're not actually using IPv6 to reach it? And also over Wireguard?

                        w0wW 1 Reply Last reply Reply Quote 0
                        • T
                          Tueem @Tueem
                          last edited by Tueem

                          I just wanted to throw in, that OpenVPN also works fine so I'm 99% sure there is something wrong with the wireguard plugin.

                          1 Reply Last reply Reply Quote 0
                          • w0wW
                            w0w @stephenw10
                            last edited by w0w

                            @stephenw10
                            No wireguard in my case. Now I use PPPoE only for IPv4 and HE GIF for the IPv6 testing and fallback. No problem with 13.x.x.x based sites currently, but I did not tested all of them.
                            I honestly don't understand what the relation to IPv6 is at all if packet capture shows that the connection is going through the IPv4 stack. I would be sure that it's some configuration error either from the provider's side or somewhere else on my end, but in fact, everything works directly, without pfSense.

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