Sponsored Content
Full Discussion: Opening ports
Operating Systems AIX Opening ports Post 302129259 by sysgate on Monday 30th of July 2007 08:18:35 AM
Old 07-30-2007
The ports are opened, you just need to bind an application to listen on this port. Before that, make sure that nothing is connected on this port, verify with "netstat -na | grep "number of the port". Stop the applications running and start yours. Also, make sure that these ports are allowed at the firewall if any.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

opening ports

I need to open a port in linux to allow a connect() from another box to succeed. I have the linux box listening on port 3000 on INADDR_ANY, and a Windows box does a connect to the IP of the linux box on that same port. The Linux box refuses the connection. I think it's because all the ports are... (9 Replies)
Discussion started by: dryheat
9 Replies

2. UNIX for Dummies Questions & Answers

Opening files

I am very new to unix. I want to open a file and read one line in at a time. Can anybody help? (3 Replies)
Discussion started by: saarshad001
3 Replies

3. UNIX for Advanced & Expert Users

Opening CDE

I have installed JASS on one of my sun servers. I am now trying to open for CDE. For that I have done these steps: mv /etc/rc2.d/_S71rpc.JASS.* /etc/rc2.d/S71rpc mv /etc/rc2.d/_S99dtlogin.JASS* /etc/rc2.d/S99dtlogin but still no CDE. Any advice on this?? (3 Replies)
Discussion started by: encrypted
3 Replies

4. UNIX for Dummies Questions & Answers

Opening TCP ports

I'm not sure if this is the right place for this post, but I'd be grateful if somebody could please help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i... (2 Replies)
Discussion started by: thehaapyappy
2 Replies

5. IP Networking

problem opening TCP ports

Please can somebody help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth0 -p tcp --sport 1982 -m state --state NEW,ESTABLISHED -j ACCEPT iptables... (5 Replies)
Discussion started by: thehaapyappy
5 Replies

6. Solaris

Please help with opening a port??

Hello all, I need assistance... I need to open a port # 36677 and have it remain open even after a power cycle. I thought all I needed to do was add it to /etc/services. That was not it... Can someone please tell me how to do this. Thank you. (6 Replies)
Discussion started by: komputersman
6 Replies

7. Solaris

SMC not opening

I am working with Solaris 9.In that I am trying to open SMC(Solaris Management Console) but when I am clicking it,nothing is opening. Can any1 tell me why it is not opening??:confused: (1 Reply)
Discussion started by: smartgupta
1 Replies

8. Cybersecurity

Opening ports 8015/8016 restricted to selected IP addresses

Hello there I'm using a vendor-supplied application on RHEL4 that includes a built-in Tcl webserver. The webserver is working but I cannot access it from any computer other than the host workstation. I suspect that the firewall is blocking ports 8015/8016. I have two questions: 1. How do... (1 Reply)
Discussion started by: craig3201
1 Replies

9. UNIX for Dummies Questions & Answers

Who are all opening my datasets,?

Hi, I need a command/script, who opened my dataset, consider a situation like, if a user has opened the dataset few days back then, that command/script should list his/her id. I don't want audit on my dataset, i need only list of users who are using my dataset. Thank you. (10 Replies)
Discussion started by: subbarao12
10 Replies
MAC_PORTACL(4)						   BSD Kernel Interfaces Manual 					    MAC_PORTACL(4)

NAME
mac_portacl -- network port access control policy SYNOPSIS
To compile the port access control policy into your kernel, place the following lines in your kernel configuration file: options MAC options MAC_PORTACL Alternately, to load the port access control policy module at boot time, place the following line in your kernel configuration file: options MAC and in loader.conf(5): mac_portacl_load="YES" DESCRIPTION
The mac_portacl policy allows administrators to administratively limit binding to local UDP and TCP ports via the sysctl(8) interface. In order to enable the mac_portacl policy, MAC policy must be enforced on sockets (see mac(4)), and the port(s) protected by mac_portacl must not be included in the range specified by the net.inet.ip.portrange.reservedlow and net.inet.ip.portrange.reservedhigh sysctl(8) MIBs. The mac_portacl policy only affects ports explicitly bound by a user process (either for a listen/outgoing TCP socket, or a send/receive UDP socket). This policy will not limit ports bound implicitly for outgoing connections where the process has not explicitly selected a port: these are automatically selected by the IP stack. When mac_portacl is enabled, it will control binding access to ports up to the port number set in the security.mac.portacl.port_high sysctl(8) variable. By default, all attempts to bind to mac_portacl controlled ports will fail if not explicitly allowed by the port access control list, though binding by the superuser will be allowed, if the sysctl(8) variable security.mac.portacl.suser_exempt is set to a non- zero value. Runtime Configuration The following sysctl(8) MIBs are available for fine-tuning the enforcement of this MAC policy. All sysctl(8) variables, except security.mac.portacl.rules, can also be set as loader(8) tunables in loader.conf(5). security.mac.portacl.enabled Enforce the mac_portacl policy. (Default: 1). security.mac.portacl.port_high The highest port number mac_portacl will enforce rules for. (Default: 1023). security.mac.portacl.rules The port access control list is specified in the following format: idtype:id:protocol:port[,idtype:id:protocol:port,...] idtype Describes the type of subject match to be performed. Either uid for user ID matching, or gid for group ID matching. id The user or group ID (depending on idtype) allowed to bind to the specified port. NOTE: User and group names are not valid; only the actual ID numbers may be used. protocol Describes which protocol this entry applies to. Either tcp or udp are supported. port Describes which port this entry applies to. NOTE: MAC security policies may not override other security system policies by allowing accesses that they may deny, such as net.inet.ip.portrange.reservedlow / net.inet.ip.portrange.reservedhigh. If the specified port falls within the range specified, the mac_portacl entry will not function (i.e., even the specified user/group may not be able to bind to the specified port). security.mac.portacl.suser_exempt Allow superuser (i.e., root) to bind to all mac_portacl protected ports, even if the port access control list does not explicitly allow this. (Default: 1). security.mac.portacl.autoport_exempt Allow applications to use automatic binding to port 0. Applications use port 0 as a request for automatic port allocation when bind- ing an IP address to a socket. This tunable will exempt port 0 allocation from rule checking. (Default: 1). SEE ALSO
mac(3), ip(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_mls(4), mac_none(4), mac_partition(4), mac_seeotheruids(4), mac_test(4), mac(9) HISTORY
MAC first appeared in FreeBSD 5.0 and mac_portacl first appeared in FreeBSD 5.1. AUTHORS
This software was contributed to the FreeBSD Project by NAI Labs, the Security Research Division of Network Associates Inc. under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program. BSD
December 9, 2004 BSD
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy