SunOS 5.8

Xorgroth · 12-13-2006, 11:35 AM

I'm in pure command line here, SunOS 5.8, was wondering if there was a command to kick connections of a specific port #. We could reboot and have it done or reboot the PCs connecting, but thought there was a way to kick connections of a port #.

MensaWater · 12-13-2006, 11:47 AM

You could use lsof to determine what process is using the port and try killing that process.

However if its a FIN_WAIT status of some sort there may be no process and it may not go away until a reboot.

I did find a script using ndd that would get rid of FIN_WAIT_2 on HP-UX. Not sure if you can use it on SunOS 5.8. Only Sun I have here 5.6 and it doesn't show the tcp_discon as available.

The script if you want to play with it AT YOUR OWN RISK:

Code:

#
# Taken from Jim Dunn's script.
#
# Doug Burton - 1/23/2004
# http://home.tampabay.rr.com/batcave/
#
# jlightne 02-Jul-2004 - Found on HP ITRC-Modified for bluebird port 1502 issue
#############################################################

# jlightne Modified center line to look only for port 1502 on bluebird's IP:
stuff=$(/usr/bin/printf "%.2x%.2x%.2x%.2x%.4x%.2x%.2x%.2x%.2x%.4x\n" \
 $(/usr/bin/netstat -an | /usr/bin/grep 64.102.0.149.1502 | \
 /usr/bin/awk '{print $4,$5}' | /usr/bin/sed 's/\./ /g'))

# jlightne This line was center line above as I found it -  This would kill ALL
# FIN_WAIT_2 items which might be risky:
# $(/usr/bin/netstat -an -f inet | /usr/bin/grep FIN_WAIT_2 | \

for x in $stuff
  do
  echo $x
    /usr/bin/ndd -set /dev/tcp tcp_discon_by_addr $x
done

Xorgroth · 12-13-2006, 12:21 PM

Yeah, we've killed the process its SQL, most sites I've been to say change the port # but that would screw over the clients that are connected.

MensaWater · 12-13-2006, 12:38 PM

I'm confused. If clients are connected on the port how would you free it?

If clients are connected via separate ports then changing port number wouldn't affect them but might affect new connections that expected you to be listening on the original port.

If you run "ndd /dev/tcp \? |grep tcp_discon" do you see anything?
On HP-UX I see:
tcp_discon (write only)
tcp_discon_by_addr (write only)

which is what allows above script to work. By the way in the above I hardcoded port 1502 - you'd want to modify it for the one you wanted if you decided to try it.

The script is AT YOUR OWN RISK but the command in this post doesn't write anything - just checks to see what capabilities you have for /dev/tcp.

Xorgroth · 12-13-2006, 12:46 PM

Well, we rebooted but tcp_discon isn't available on 5.8 so the ndd comes up with nothing.

Yeah, I think a couple were on separate ports, but after killing SQL they are still connected.

mdhmi · 12-27-2006, 02:24 PM

Install lsof from SunFreeware.com. That'll help you determine what's running and which process are controlling it.

MensaWater · 12-27-2006, 03:26 PM

Question was how to stop the connections rather than determine what they are. However I heartilly recommend lsof for all Unix/Linux OSes. It has many uses including the one you mention.