What is the biggest attack in GBPS you stopped
-
@cmb
He did it to me after 5 seconds traffic graph stopped at 3.19 mbits…
I dont reall care what happened after 5 seconds but before that there was no more than 3 mbits except if traffic graph was wrong...Exactly. The notoriously slow and cpu-intensive pfSense traffic graph. That's your measurement tool?
It is trivial to put a real monitoring and data gathering tools between your wan device and the pfSense wan port to see what's really happening.
And do it in a lab to eliminate all the ISP nonsense. Remove as many variables as possible and test the actual asserted problem. The first step in any bug report is providing the steps to duplicate. At least if you want the problem fixed.
-
I did only 1 test with Supermule which proved the point and then I replaced pfsense with other solution until this gets fixed.
I still have pfsense @home but I will test no more because I don`t like the way this thread is going.
If whole pfSense/ESF network is vulnerable so can be my home network, who will target me :) -
Everyone is vulnerable to DDoS, dude. Everyone. Not saying there isn't an issue, but without steps to reproduce it won't get fixed.
-
:D
I didnt work with Franco UNTIL after we didnt get anywhere with pfsense and he is NOT behind this.
After we tried to get ESF involved and push for testing at a rig in their control then they could put the collectad data upstream. But nothing.
I tested Opnsense as a measure to see if it was all systems based on FreeBSD thats vulnerable and that was the way I got in touch with Franco.
I asked him politely if he wanted to help me test and get it upstream and he would.
So pls. dont make assumptions in your own head. It has nothing to do with the real world scenario.
Franco was the only one willing to help get it upstream and the connection was made when I asked him politely.
Nothing more in it.
Dont make this an opnsense/pfsense feud. Its not. I might have called Cisco instead but their systems are vulnerable to.
I downed the emergency hotline and 2 powerstations when testing at a customer.
While somebody is using a lot of time to write about misuse of application and lots of technical stuff that is suppose to make him look smart, then it doesnt help since pfsense/ESF can be taken offline easily as well.
So either they dont understand their own words, text or product since they are very vulnerable to.
Thats the fact. We have been trying to get ESF involved by setting up freeBSD server to test in their end. Nothing.
So pfsense is vulnerable. All over the world and people using it to host servers behind it, selling hosting is vulnerable.
So stop the name calling. Its just smoke and mirrors to a severe flaw in the eco system.
That would be a very good idea if possible!
Opnsense has this fix done allready and a full release on friday.
I had to register solely for this crap. This is typical opnsense.
So you advertise your "skill" on pfsense forum that has infinitely more users than opnsense forum, refuse to show FreeBSD and pfSense developers how this is being done and then provide the "solution" to opnsense. Wow, that's so opn and open source spirited! I love the fact Franco is behind this, it just proves how low opnsense guys are willing to go.
Unfortunately for Franco and you, opnsense is still light years behind pfSense even with "your" fix.
Dude, thank you! thank you for confirming everything I wrote!
edit: I had to edit this because it's just way too much fun!
Thank you for proving me right, thank you for confirming you worked with Franco on this. Thank you for saying "pfsense is vulnerable"!!!!
-
You are quite right.
But DDoS with 3mbit bandwith shouldnt exhaust any router and it did taking everything offline.
Everyone is vulnerable to DDoS, dude. Everyone. Not saying there isn't an issue, but without steps to reproduce it won't get fixed.
-
Thing is Chris.
You accused of downing pfsense/ESF and the forum.
How was it downed and did you do a pcap?
Fact is that it was downed according to you. Why not try and use that pcap and see what was causing it?
@cmb:
Franco was the only one willing to help get it upstream and the connection was made when I asked him politely.
Not true at all. If you would have come to us with an actual useful problem report at any point, even still now, we'll be able to get attention upstream if it's really an issue. Quite possibly get it fixed ourselves, since we have multiple FreeBSD committers on staff. And I'm still absolutely willing to do that, you just refuse.
You can either backup these claims so I can actually do something about it if there is an issue, or I'm just going to ban you as a troll, because these threads are an absurd waste of everyone's time at this point.
-
But if the pfSense traffic graph is the measurement of "3Mbit/s" I call bullshit.
One question:
Why didn't you provide the FreeBSD security team the details of your alleged vulnerability?
-
Thing is Chris.
You accused of downing pfsense/ESF and the forum.
How was it downed and did you do a pcap?
Fact is that it was downed according to you. Why not try and use that pcap and see what was causing it?
I experienced problems one afternoon trying to get on the forum and even reported it, I dont know who or what was behind it, but I can speculate until the cows come home. :D
I then had a hell of job trying different ways to get to the forum, like using proxys based in different parts of Europe.
The proxy based in another country generally was successful at accessing the forum, until I tried to log in, read that as having identified myself, at which point connections were dropped.
I never had a problem at accessing the pfsense website on the different IP address at the same time, in fact it was plain sailling so to speak all along the various ESF IP addresses, but once I displayed a repeatable pattern when accessing the forum thats when access was blocked. Things is, AI is a quick learner.
-
The forum has occasional problems. They feel like database issues to me.
-
The forum has occasional problems. They feel like database issues to me.
Thats one way of putting it.
-
This shit still going on? Supermule, which part of the post I linked you do not get? Absolutely NOONE is interested in YT videos, PM to get (D)DoS-ed and similar bullcrap! Want it being worked on and fixed? Provide the information required! Instead of stupid excuses why not to do so…
-
:D
I didnt work with Franco UNTIL after we didnt get anywhere with pfsense and he is NOT behind this.
After we tried to get ESF involved and push for testing at a rig in their control then they could put the collectad data upstream. But nothing.
I tested Opnsense as a measure to see if it was all systems based on FreeBSD thats vulnerable and that was the way I got in touch with Franco.
I asked him politely if he wanted to help me test and get it upstream and he would.
So pls. dont make assumptions in your own head. It has nothing to do with the real world scenario.
Yea, nice try but I'm not buying it. This thread and the ones on FreeBSD forums prove the opposite. Your plan was to make pfSense look vulnerable to the phantom issue and present opnsense as a better solution.
I'm also beginning to think that this "trick" you refused to share with anyone is actually Franco's idea in the first place, considering his packetwerk background.
Feel free to continue to deny it, keep saying that poor you just tried to help but nobody gave you a chance, but we all know that opnsense promotion was behind all this time. Now it makes sense why you behaved like this, why you refused to share any useful details on the issue. Now it shows how truly corrupt and malicious opnsense people and their drones like you really are.
Thanks once again for proving me right.
-
Why didn't you provide the FreeBSD security team the details of your alleged vulnerability?
crickets
-
I dont ask you to buy it. I am just beeing honest.
Picture is from opnsense forum messages.
Conversation beginning at June 9th. As of june 22nd we havent gotten around to test and Franco is in the dark as well and havent been able to get any info. 4 PM's preceeding this picture.
Did the attacks occur before june 9th?? If it did, then its not related to Opnsense as stated and they have nothing to do with it.
So try again. And lose the tinfoil suit your wearing.
EDIT: AS you can see I registered June 6th. Was that before or after the attacks??
If after then you look stupid in many peoples views. Including mine.
If it was Franco then why would he need to test things in the 1st place?? If he had the script.
-
The problem has shifted into how transparent are people posting on this forum.
From a pfsense/ESF perspective, this isnt good for business, because even the mention of other solutions can be good/bad for business as it raises awareness of others which undermines marketing.
Whilst theres no denying no one can do anything about bandwidth domination, aka flooding, (D)Dos, how a security product handles it does matter if and when it falls over. Hopefully pfsense/ESF can come up with a solution, perhaps better education of their product to their users which might be lucractive or at least damage limitation.
Either way I've learnt more from this thread and seeing things on my own system which is always educational.
-
I dont ask you to buy it. I am just beeing honest.
Picture is from opnsense forum messages.
Conversation beginning at June 9th. As of june 22nd we havent gotten around to test and Franco is in the dark as well and havent been able to get any info. 4 PM's preceeding this picture.
Did the attacks occur before june 9th?? If it did, then its not related to Opnsense as stated and they have nothing to do with it.
So try again. And lose the tinfoil suit your wearing.
EDIT: AS you can see I registered June 6th. Was that before or after the attacks??
If after then you look stupid in many peoples views. Including mine.
If it was Franco then why would he need to test things in the 1st place?? If he had the script.
Ha! You're making 0 sense, you know that, right? You think it matters when you registered on opnsense forum? Dude, you must think everyone here is stupid.
No, that does not make you right. There's still proof right here that you ignored all requests for more information from both pfSense guys and FreeBSD team. That means you intentionally created this charade for self-promotion of yourself and your patrons, opnsense (whom you "gave" a fix for the issue).
Opnsense is known for their lies and maliscious behaviour from day 1 since their inception, so your denial and refusal to provide any kind of information except those worthless youtube videos speaks volumes.
You had a chance and you blew it, give it up. Go sell opnsense somewhere else.
I just love the way you're being nervous because you got busted! Say hi to Franco!
-
-
This thread requires moderation please. It was an interesting read, but is going nowhere…
-
What??
:D
Geesus.
I let people decide whats right and whats not. We have emails dating back about 6mths asking pfsense/ESF for advise and asking them for help. Almost nothing came back.
Ask yourself if you would provide a script to strangers that can down almost anything with 3mb/s traffic and wait for a fix.
Its like providing guns to the youth of America and trusting them not to use it…. just to provide information to the producers of whether the damn thing could kill people or not.
You keep bickering about Opnsense.
I think everyone has seen that this is not about Opnsense and me since we are not related in any way.
I didnt provide a fix to Franco. He did that by himself when I posted the security advise from FreeBSD.
So pls. stop since you look like a fool IMHO.
Lets look at it differently:
When you get attacked, you call the person responsible and ask for his code?
Or do you log and see whats coming and how the box behaves?
You are forced to do chose the 2nd option since you have no control over whats coming your way.
So providing the code has no relevance at all. Providing the test rig and do Dtrace and DEV work is the way ahead.
Come on guys....
I know you can do better than that, but youre cornered and have no way out.
Just admit you handled it badly and we can get on with it. Nothing more in it.
-
No I did not. Where do you see that??
Why didn't you provide the FreeBSD security team the details of your alleged vulnerability?
crickets
Interestingly he did provide the details to opnsense, which was part of the plan since the beginning of this charade. He's so busted ;D
