On Wed, Jul 30, 2014 at 08:18:51AM +0100, Joe wrote: <snip> > Something else you might do now is to place temporary logging rules > before your 'DROP' rules, to confirm whether it is indeed iptables > which is blocking those packets. No logs, it's somebody or something > else. And if you have anything other than just a bare modem between you > and the outside world, which is not really best practice, then the first > place to look is the Net router.
The temporary logging rules is a good idea, I'll do that. > And as someone else asked, why are you worried about this 'stealth'? As > long as the bad packets don't get in, what does it matter? Why is there a DROP instruction in iptables as well as REJECT? If a hacker gets no response he's less likely to dig further. Thanks for your thoughts. Mike -- Who knows what evil lurks in the hearts of men? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140730153335.GE14982@playground
