From: Ceriel Jacobs Date: 2011-11-23T02:28:03+09:00 Subject: Network connection to ruby daemon script connect on public ip of local machine but fails remotely On a Mac OSX 10.5.8 server OS, % ruby sip-alg-detector-daemon.rb -i 4.3.2.1 Mon Nov 21 00:16:46 2011 INFO: Starting SIP ALG Detector daemon... Mon Nov 21 00:16:46 2011 INFO: Use '-i IP' to set the listening IP Mon Nov 21 00:16:46 2011 INFO: Use '-p PORT' to set the listening port Mon Nov 21 00:16:46 2011 INFO: Bind address: 4.3.2.1:5060 OK ===== Being on the same machine the client sip-alg-detector.rb and telnet connect both OK to sip-alg-detector-daemon.rb on port 5060. % ruby sip-alg-detector.rb -n -si 4.3.2.1 -lp 5065 Error ===== Being on a remote Mac OSX 10.6.8 machine, the client is unable to connect to the remote port 5060, not TCP neither UDP, also telnet fails: Trying 4.3.2.1... telnet: connect to address 4.3.2.1: Operation timed out telnet: Unable to connect to remote host Tried ===== Step already tried to resolve... 1. Check server firewall The ipfw firewall accepts the packets: Nov 21 02:31:07 193 ipfw[892]: 12323 Accept TCP 1.2.3.4:50285 4.3.2.1:5060 in via en0 2. Check client firewall Firewall disabled, result = identical 3. Check from another host Grc.com/shieldsup returns a "stealth" on port 5060 Question ======== What kind of "magic" is required on Mac OSX to make this ruby daemon on port 5060 to become connectable from remote networks? -- % ruby -v ruby 1.8.6 (2009-06-08 patchlevel 369) [universal-darwin9.0] % uname -a Darwin 4.3.2.1 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 -- Posted via http://www.ruby-forum.com/.