Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-20-2006, 10:16 AM
|
#1
|
Member
Registered: Jul 2003
Location: Au
Distribution: SLES8, centOS 3.5 & 4 servers, xandros desktops
Posts: 95
Rep:
|
I'm surprised by this, should I worry?
Despite having limited experience I look after a small business network. We use an IPCop firewall and on our internal network we have a Centos3 Fileserver and half a dozen linux desktops connected by nfs and a printer running IPP on port 631.
A short while ago, after the office was emptied and only the file server was running, I noticed a lot of activity on the firewall. Running ethereal on the file server gave me a stream of reports like the following. On our network 192.168.20.20 is the file server and 192.168.20.10 is the firewall's internal interface.
No. Time Source Destination Protocol Info
1934 306.961029 192.168.20.20 192.168.20.10 TCP 60214 > microsoft-ds [ACK] Seq=761 Ack=7736 Win=20440 Len=0
Frame 1934 (54 bytes on wire, 54 bytes captured)
Arrival Time: Jul 20, 2006 23:33:13.806652000
Time delta from previous packet: 221.129479000 seconds
Time since reference or first frame: 306.961029000 seconds
Frame Number: 1934
Packet Length: 54 bytes
Capture Length: 54 bytes
Protocols in frame: eth:ip:tcp
Coloring Rule Name: TCP
Coloring Rule String: tcp
Why would a linux file server be sending TCP smb packets to the firewall?
Could someone enlighten me?
Thanks indeed
|
|
|
07-20-2006, 05:30 PM
|
#2
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
Probaly because you are running Samba on the Linux server. Samba is designed to allow one to do smb shares with MS-Windoze so you can mount Windows exports to Linux and vice versa. It certainly does smb traffic.
|
|
|
All times are GMT -5. The time now is 06:36 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|