What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

SYN Flood problem after FW 376.4X_X

Hexabion

Occasional Visitor
Hi, after upgrading the fw, and setting up scripted start of samba minidlna and transmission (in /jffs/scripts and /configs), my router is much faster and works like a dream, exept minidlna "crashes", basically just stops after some time, and it always happens after a log message like this:

"kernel possible syn flooding on port 8200. sending cookies".

Every time I have downloaded someting, or move someting through SMB to one of the media-folders "watched" by inotify in minidlna, it sends that message in log and minidlna stops.

Problem is this also happens halfway into movies even when im not doing anyting special.
I have a script looping/running from services-start that checks pidof on minidlna to check if running, if not running it will restart the minidlna service, but that doesnt stop my problem minidlna crashing in the midst of movies.

I have the following setup:

Firewall: On (DDOS attack-protection ON), tried OFF on both with no luck
HDD: Running the DB and logging of minidlna on a ext2/3 (non-ntfs) partition, but the mediafiles itself on a second partition (NTFS) on that same HDD.

What i've read here earlier is that keeping the DB on a non-ntfs, meaning a ext2/3 partition should make it run without problems, which it also did until i upgraded FW from 374_30_3 (RMERLIN). There I used an entware version of minidlna (1.1.2 i think), and that worked fine (exept problems with ()null folders)

I'm currently running the 1.1.4 minidlna that comes with the latest RMERLIN FW, but starting it in a script instead of via the GUI.

I have looked at IPTABLES and the filter_rules file, and i suspect the solution to it lies there somewhere, I just dont know how to implement a SYN Packet rule different than the one allready there.

Can i tamper with the IPTABLES command on each boot without fearing to ruin the filer_rules file permanently? Meaning, does it get regenerated each boot, if so I could insert alot of experimental IPTABLES commands in firewall_start.

I need some help on those two questions:

1: Will inserting / modifying the IPTABLES / filter_rules be permantent (meaning a chance of bricking the rules / ruining them) ?

2: If not, what command should i construct and put into firewall_start with IPTABLES?

Thanks in advance.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top