Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
OK. I think I found the outbound part. Stupid me! The addresses w/ port 53 were dynamically assigned DNS servers from my ISP. So when I was asking for a web page the router was contacting the DNS for info. It seems reasonable, don't you think?
But the first part is still a mystery to me. Why I keep on getting TCP packets to a torrent port although I do not use torrent?
Last edited by dimitris.kalamaras; 04-03-2006 at 06:33 PM.
If you have a dynamic ip maybe you are taking the ip of a person who before you was doing bittorent with this IP. And the time that the bittorent removes you from good sources you will still receive questions from others. I don't know bittorent so I don't know the mechanism.
In this case, what I do is restart my router (and wait >5mn) so that I am assigned a new IP.
In a way, as your firewall is blocking the port (you're not saying : the port is open/closed, you're not answering anything which is not standard), the other clients will try again. You could open the port on your firewall..
For the rest of the traffic, it looks like some DNS or some webserver are longer to answer that the timeout of your firewall (good values can be 15mn for TCP,40s for UDP if you can modify them)
And these kind of logs are pretty useless because as int0x80 said you would need the complete headers which you probably can't have from the webconsole of your router.
You could also get a kernel >= 2.6.15 it has some more network security features.