Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Lycan]

I like that. I'm going to use that one. Tell your dad he is smart.

[EddieZ]

Well, it is like my father says.

"Locks exist to keep honest people honest, they will only ever slow down dishonest people"

Also applies to 18-year old daughters 

[Fatman]

I knew there was a reason my father raised no daughters...


But in all seriousness can we either get to OP to clarify or this thread to die, as while it is amusing, anyone who comes in here looking for forensic networking tips is going to find something else entirely.

[EddieZ]

From a Dlink perspective you're right :-)

As to the topic, I think this thread has answered all questions that can be answered.

[funchords]

Eddie -- MAC filtering won't help.  This is a WAN-side attack.

This is the log from my NAS.  
My router has a port open so I can access the Media Station from the internet.  It would be nice to be able to block IP's if I detect a hack attempt.  

That will get old. 

Make sure your NAS security is tight.  If it's open to the Internet, it's going to be probed. 

You can reduce these -- these measures are more prevention than security. 

If you want to limit your port-forward entry to IP addresses on the network that you'll use when you're away, then you can do that (the IP addy that was attacking you first was in Brazil). 

If possible, use a port that doesn't match a frequently-attacked service.  This is tougher if your NAS or router won't support it.

HTH

[EddieZ]

Eddie -- MAC filtering won't help.  This is a WAN-side attack.

Hi Rob,
You're right  MAC filtering does not have any effect.

[Lycan]

The router/firewall logs were never produced and I think this topic has reached the end of it's usefulness.

As always if anyone feels I've done them wrong by locking this thread, PM me with a good reason and I'll unlockify it. (Bush-ism).

-Lycan