DDoS/Spam Detection
I've been trying to build up this spam detector to run on my machines, but I've been struggling due to Nginx Proxy Manger / Nginx in general. I've already added
to the advanced config in NPM but it's still detecting packets as from my own IP

19 Replies
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close
!close
!solved
!answered
Requested by ashanki#0
not really mc related sry but would be nice
it seems to be for servers
wdym
looks like hes trying to create a spam detection plugin for mc servers
not really... mc
discord interaction is a thing
think you're misinterpreting the use case
I run many things, I just want to know where the traffic is coming from / going. I operate a server host
So many mc servers, webapplications, apis, cdns etc
ahhh ok
and i just now realized you were the poster, im dead tired lol
get some rest
looks like he'sš brother im the OP š I just read that
i would but it's 7 am and i dont wanna destroy my sleep schedule by going to bed now
š alr ig
How are you detecting packets?
Are you using Nginx streams?
no, I have 0 idea how
thats the thing
I'm just using tcpdump, and that can't detect nginx stuff
How do I use nginx streams?
tcpdump doesn't understand proxy_protocol
so you would need a program which was proxy_protocol aware to do your logging
or something like mmproxy to "undo" the proxy_protocol https://github.com/cloudflare/mmproxy
GitHub
GitHub - cloudflare/mmproxy: mmproxy, the magical PROXY protocol ga...
mmproxy, the magical PROXY protocol gateway. Contribute to cloudflare/mmproxy development by creating an account on GitHub.
I believe you could maybe also do it with tshark with the right path
alr ig
I mean, tcpdump doesn't understand proxy_protocol, so there's no way to magically change the source ip back
It's why you'd typically run it only on your proxy instead