What is the biggest attack in GBPS you stopped

Harvy66 · Jun 28, 2015, 8:04 PM

EDIT: It was my bandwith that caused to attacked IP to survive.

No change in resilience. (Sorry).

It was your bandwidth? Isn't that the goal? The weakest link should be the bandwidth, not the firewall, yes? What issue(s) still remain? Same?

Supermule · Jun 28, 2015, 8:38 PM

As soon as I was able to push 10mbit/s out on my private line, then it failed again….

Harvy66 · Jun 29, 2015, 12:15 AM

So 10Mb/s of special traffic against your greater than 10Mb/s link caused the link to fail? Did the firewall stop working or only the link go down?

Supermule · Jun 29, 2015, 8:25 AM

Firewall stopped routing traffic. Link was fine.

Lots of packetloss once again.

Harvy66 · Jun 29, 2015, 1:21 PM

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

Any news from the FreeBSD side of things?

Supermule · Jun 29, 2015, 1:22 PM

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

torontob · Jul 9, 2015, 2:26 AM

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

Supermule · Jul 9, 2015, 2:33 AM

Still working on it.

Supermule · Jul 23, 2015, 7:16 AM

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

Latest update.

peterclark4 · Jul 23, 2015, 7:25 AM

@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?

Supermule · Jul 23, 2015, 7:46 AM

That would be a very good idea if possible!

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

maverick_slo · Jul 23, 2015, 10:00 AM

Do they have snapshot that you could test?

Supermule · Jul 23, 2015, 10:05 AM

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

Harvy66 · Jul 23, 2015, 1:14 PM

@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

Harvy66 · Jul 23, 2015, 1:21 PM

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

Supermule · Jul 23, 2015, 1:25 PM

Could very well be.

tim.mcmanus · Jul 23, 2015, 3:16 PM

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

Supermule · Jul 23, 2015, 3:31 PM

Not yet.

@tim.mcmanus:

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

firewalluser · Jul 23, 2015, 3:35 PM

@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?

Harvy66 · Jul 23, 2015, 4:54 PM

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