Author

Topic: Come at me Bruh! (Read 643 times)

legendary
Activity: 966
Merit: 1042
May 02, 2017, 03:18:35 PM
#4
I haven't seen anyone else with this issue recently. I know I saw a post probably a year back where they had an issue but after they kept banning IP after IP I think it was resolved. I think it was Lauda? I can't seem to find it. It may be something personal against you or you may have been randomly chosen but either way I'm assuming 40GB/day won't work out well for you or your ISP.
newbie
Activity: 5
Merit: 0
May 02, 2017, 03:13:16 PM
#3
That log is from my firewall and entirely separate from bitcoin.  It is a DDOS attack which I am assuming, is intended to knock my node offline.  I suppose it could have nothing to do with bitcoin, and somebody simply has a beef with me, but I can't imagine why that would be the case. 
member
Activity: 149
Merit: 22
🔴🔵 FoxMixer.com 🔵🔴
May 02, 2017, 12:24:31 PM
#2
I never actually faced this error in the logs "flood attack".

Did you change anything in the default configuration? Does this happen continuously or only at specific times?
Maybe it could be that there are many nodes that need to download the blockchain nearby, causing this flood, but I'm just guessing here.
newbie
Activity: 5
Merit: 0
May 02, 2017, 07:23:23 AM
#1
I'm running a full node on version 14.1 and have been weathering a UDP flood attack of better than 1000 packets/second for about three days.  I had no idea I was stepping into the middle of some religious war when I decided to run a node.  I just thought it would be a cool thing to do.  Is anyone else experiencing this?  My bandwidth usage is a lot higher than the FAQ said it would be.  I'm averaging about 40GB outbound per day, and I'm hosting between 50 and 75 connections at any one time.  What is other people's experience?http://imgur.com/JozZ7zH
Jump to: