Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
you open a port by using it. there's no such thing as being just "opened" outright. you can explicitly deny access with a firewall if you have one, but if not there's nothing in the way of doing what you want.
ok...In that cse, i installed Sebek and configured the source port to be UDP port 1101.
But i could not really see any sebek data.
So i checked it by runnning nmap and scanned for UDP open ports. I did not find UDP port 1101 in the resuls given by nmap.And this could be the reason why sebek is not logging anything.
I dont know why this nmpa doesnt show 1101 as open port.
to list all listening udp sockets. If yours is listed there, then there is something else preventing others from sending to it. Take a look at your iptables rules (if you have any configured). If those look sane, are you behind any external firewall device? If so, make sure that it is not dropping those packets.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
maybe posting your distro and version someone may be familiar with it to tell you where to edit to open a port in your iptables firewall config file. that is if there is a firewall running on the machine. As root one maybe able to tell from this command as root.
/sbin/iptables -L
Perhaps the netstat output is correct, but it’s listed as the service name instead of a numerical port. In this case, it might say pt2-discover. I should have mentioned this earlier, but if you want to force numerical port numbers, give the -n flag. If you want to see processes owning the sockets, use the -p flag (may require root privileges). If you want to see both listening and sending sockets, use the -a flag. Altogether, that’s:
Code:
sudo netstat -aunp
Also, are you sure that sebek is running (in addition to being installed)? What is the output of:
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Now knowing the distro in question and if you used default RHEL 5 install options then the firewall iptables daemon script is enabled. You need to edit /etc/sysconfig/iptables and place this line somewhere in the middle.
Code:
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 1101 -j ACCEPT
Then restart iptables daemon as root use this command.
/sbin/service iptables restart
That's okay, because the firewall only controls access to a port, it has no part to play when it comes to "opening" it. As already mentioned by acid_kewpie, you need to have something use the port in order for it to be open. At this point, I suggest you use the netstat advice you've received in order to make sure your service is listening properly.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
If you have disabled the iptables firewall then I don't think that is your problem.
Is selinux enabled? If so I would disable to see if that works if no firewall is running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.