Ports, port forwarding...
I have setup port forwarding on my firewall for a filesharing application - xMule (needs 4662 forwarded). This works great until I crash xMule. When I restart the application, it complains that port 4662 is not available. Port 4662 remains unavailable until I restart the computer - I don't do anything with the firewall machine (a seperate computer). After a restart, port 4662 is again available. So.. here's the question... how can I release the 4662 port that has been "claimed" by the crashed application? I cannot find anything in my process list that is hanging around after the crash. I don't know what else to look for to find what is keeping port 4662 engaged. Rebooting seems like a silly way to correct a problem. So... any ideas or suggestions? C.
On Mon, 2003-07-14 at 20:34, Clayton Cornell wrote:
So.. here's the question... how can I release the 4662 port that has been "claimed" by the crashed application? I cannot find anything in my process list that is hanging around after the crash. I don't know what else to look for to find what is keeping port 4662 engaged. Rebooting seems like a silly way to correct a problem. So... any ideas or suggestions?
try "fuser 4662/tcp" and see which process is holding the port. And you're right, a reboot shouldn't be necessary. As soon as the app holding the port exits (for whatever reason) the port should be released. So I have to assume it hasn't exited
On Monday 14 July 2003 20:38, Anders Johansson wrote:
On Mon, 2003-07-14 at 20:34, Clayton Cornell wrote:
So.. here's the question... how can I release the 4662 port that has been "claimed" by the crashed application? I cannot find anything in my process list that is hanging around after the crash. I don't know what else to look for to find what is keeping port 4662 engaged. Rebooting seems like a silly way to correct a problem. So... any ideas or suggestions?
try "fuser 4662/tcp" and see which process is holding the port.
fuser is an interesting and handly little app... so may of these I still don't know about. After researching more, it seems that port handling in xMule is less than friendly. When I look at the port useage for 4662, it is not claimed by anything until I restart xMule. xMule still complains.. so the root fo the problem seems to be xMule itself. So, thanks for the pointer to fuser... it was the tool I was looking for. Ciao C.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Next time xMule crashes on you try doing ps aux | grep xmule and see if some portion of the xMule process is still running. If so, do a killall -9 xmule. Then restart xmule and see if you still get the same problem. If so then try doing /etc/init.d/network restart. If one of those doesn't help then I'm not sure. Vince On Monday 14 July 2003 01:34 pm, Clayton Cornell wrote:
I have setup port forwarding on my firewall for a filesharing application - xMule (needs 4662 forwarded). This works great until I crash xMule. When I restart the application, it complains that port 4662 is not available. Port 4662 remains unavailable until I restart the computer - I don't do anything with the firewall machine (a seperate computer). After a restart, port 4662 is again available.
So.. here's the question... how can I release the 4662 port that has been "claimed" by the crashed application? I cannot find anything in my process list that is hanging around after the crash. I don't know what else to look for to find what is keeping port 4662 engaged. Rebooting seems like a silly way to correct a problem. So... any ideas or suggestions?
C. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQE/Evi6UDfttpvll6wRAsbsAJ4loojqJbK5aLze7fs8QFnEs5+/qACfX4Tf p0gC9G6pWhAJumW6bPsDgzI= =/Vb/ -----END PGP SIGNATURE-----
participants (3)
-
Anders Johansson
-
Clayton Cornell
-
Vincent Colombo