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

    What is the biggest attack in GBPS you stopped

    Scheduled Pinned Locked Moved General pfSense Questions
    737 Posts 33 Posters 679.9k 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.
    • H
      Harvy66
      last edited by

      So same issue as before, firewall is the weakest link, not the bandwidth? Maybe 2.3.

      Any news from the FreeBSD side of things?

      1 Reply Last reply Reply Quote 0
      • S
        Supermule Banned
        last edited by

        Not yet. They are digesting the attack that I did yesterday and curretnly looking at states not beeing freed as they should…. AFAIK.

        1 Reply Last reply Reply Quote 0
        • T
          torontob
          last edited by

          Did this end up in nowhere with the issue still being there?

          1 Reply Last reply Reply Quote 0
          • S
            Supermule Banned
            last edited by

            Still working on it.

            1 Reply Last reply Reply Quote 0
            • S
              Supermule Banned
              last edited by

              https://lists.freebsd.org/pipermail/freebsd-announce/2015-July/001655.html

              Latest update.

              1 Reply Last reply Reply Quote 0
              • P
                peterclark4
                last edited by

                @Supermule:

                https://lists.freebsd.org/pipermail/freebsd-announce/2015-July/001655.html

                Latest update.

                Does this need to be included in 2.2.4 before it is released?

                1 Reply Last reply Reply Quote 0
                • S
                  Supermule Banned
                  last edited by

                  That would be a very good idea if possible!

                  Opnsense has this fix done allready and a full release on friday.

                  1 Reply Last reply Reply Quote 0
                  • M
                    maverick_slo
                    last edited by

                    Do they have snapshot that you could test?

                    1 Reply Last reply Reply Quote 0
                    • S
                      Supermule Banned
                      last edited by

                      Waiting for the update to come. I will update and report back.

                      1 Reply Last reply Reply Quote 0
                      • H
                        Harvy66
                        last edited by

                        @peterclark4:

                        @Supermule:

                        https://lists.freebsd.org/pipermail/freebsd-announce/2015-July/001655.html

                        Latest update.

                        Does this need to be included in 2.2.4 before it is released?

                        You beat me to it. This thread is the first thing I thought about when I saw this in G+

                        https://www.freebsd.org/security/advisories/FreeBSD-SA-15:13.tcp.asc

                        1 Reply Last reply Reply Quote 0
                        • H
                          Harvy66
                          last edited by

                          Supermule, is this directly related to what you've been digging into?

                          1 Reply Last reply Reply Quote 0
                          • S
                            Supermule Banned
                            last edited by

                            Could very well be.

                            1 Reply Last reply Reply Quote 0
                            • T
                              tim.mcmanus
                              last edited by

                              So you haven't tested it?  It's more of a definite maybe that this resolves the issue?

                              1 Reply Last reply Reply Quote 0
                              • S
                                Supermule Banned
                                last edited by

                                Not yet.

                                @tim.mcmanus:

                                So you haven't tested it?  It's more of a definite maybe that this resolves the issue?

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

                                  @Supermule:

                                  https://lists.freebsd.org/pipermail/freebsd-announce/2015-July/001655.html

                                  Latest update.

                                  I suppose another question to ask, is how did we miss this on our own machines, and what can we do to avoid such problems from occurring again?

                                  Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

                                  Asch Conformity, mainly the blind leading the blind.

                                  1 Reply Last reply Reply Quote 0
                                  • H
                                    Harvy66
                                    last edited by

                                    Supermule didn't miss it. Well, possibly. If it turns out to be the same issue.

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

                                      Spotted the behavior but nothing outputted from pfsense to observe though.

                                      Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

                                      Asch Conformity, mainly the blind leading the blind.

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        tim.mcmanus
                                        last edited by

                                        @firewalluser:

                                        Spotted the behavior but nothing outputted from pfsense to observe though.

                                        Because it's not a pfSense issue.  This is an FreeBSD network driver issue.

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

                                          So there is nothing we can do then as this is just like a HW failure of sorts then?

                                          Capitalism, currently The World's best Entertainment Control System and YOU cant buy it! But you can buy this, or some of this or some of these

                                          Asch Conformity, mainly the blind leading the blind.

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            tim.mcmanus
                                            last edited by

                                            @firewalluser:

                                            So there is nothing we can do then as this is just like a HW failure of sorts then?

                                            Yes and no.

                                            If you can code and want to help recode the FreeBSD network drivers, they could use the help.  They've acknowledged that there will be more improvements in the networking layer in v11.

                                            Because pfSense is built on top of FreeBSD, it's only as good as the underlying operating system code.  So bugs/deficiencies in the OS code affect the applications running on it.  So we can't expect the pfSense team to fix a problem that's not in pfSense, and they are at the mercy of the FreeBSD code releases.  I know they regularly collaborate with the FreeBSD team, but they don't run that project.

                                            So it's not hardware per se, there are two layers of code that are maintained by two separate projects.

                                            Here are the two threads Supoermule opened up on the FreeBSD forums before they started ignoring him:

                                            https://forums.freebsd.org/threads/dos-and-ddos-attacks.51899/

                                            https://forums.freebsd.org/threads/freebsd-pf-and-syn-ack-flooding.51921/

                                            With any software project, you need to provide very detailed information to the developers so they can ascertain what the root cause may be as well as any code you're using to trigger the issue.  While Supermule provides a lot of data, it's not data the developers or forum users found useful, similar to what's in this thread.

                                            So it's possible the revised FreeBSD code resolves something, but until it's tested against this use case appropriately (on bare metal) it's only a guess as best that it resolves this use case.

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