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.
I was wondering if anybody here could offer me any advice.
At home I have a Clark Connect Linux file-server running Slimserver, managed though ssh. This is connected to the internet through an ageing SMC Barricade 7004ABR router. While recently changing some settings on my router the following entries in the log caught my eye.
2007/05/07 06:05:07 ** IP Spoofing ** <IP/UDP> 192.168.2.2:48527 ->> **.**.***.***:6346
2007/05/07 06:07:07 ** IP Spoofing ** <IP/UDP> 192.168.2.2:48527 ->> **.**.***.***:6346
2007/05/07 06:09:07 ** IP Spoofing ** <IP/UDP> 192.168.2.2:48527 ->> **.**.***.***:6346
2007/05/07 06:11:07 ** IP Spoofing ** <IP/UDP> 192.168.2.2:48527 ->> **.**.***.***:6346
2007/05/07 06:13:07 ** IP Spoofing ** <IP/UDP> 192.168.2.2:48527 ->> **.**.***.***:6346
The internal is my server IP and the **.**.***.*** is my actual external IP, I don't wish to display it in case this is something to be worried about.
So my next question is this, is it something to be worried about?
Although I have configured the box I am not very up on hardening a Linux Box to limit it to just the access I need.
If it is something to be concerned about I would be grateful for any help on how to deal with it, or at least discover what is causing it.
The port number may well have changed (high port numbers like that are generally random, used for outgoing connections).
If you're worried about it, then go back into the router and find the port number, then run the command above with that number.