Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

Rugby/firewall question

 [1/4] from: mat::b::codeplay::com at: 18-Jan-2002 16:01


Guys, Thought I'd take a look at Rugby to find out what the fuss is about. It looks quite cool and I can think of some applications. However I have a showstopping problem.
>> test "remote function ahoy!"
** Access Error: Cannot connect to 192.168.0.2 ** Where: rexec ** Near: open/no-wait/direct dest write-msg msg dest The key bit here is the ip. That's not a real ip, the server is behind NAT. It is however the dirty-net of the firewall so a request to the IP will work. However I need to get rugby to report some other IP to connect to rather than the bogus real/local IP which it has sent to my client. Is this something where I'm going to have to get my hands dirty with Rugby itself? Regards, Mat Bettinson Codeplay Tel: +44 (0)20 7482 3382 140-142 Kentish Town Rd, London, NW1 9QB http://www.codeplay.com

 [2/4] from: m:koopmans2:chello:nl at: 18-Jan-2002 18:20


The automatically generated stubs contain the ip number of the server. But... they are just automatically generated wrappers around rexec or sexec. The simplest way would be for you to create your own stub functions set using rexec or sexec using the correct ip addresses. HTH, Maarten

 [3/4] from: mat:b:codeplay at: 18-Jan-2002 17:37


Hello Maarten, MK> The simplest way would be for you to create your own stub functions set MK> using rexec or sexec using the correct ip addresses. Excellent, cheers for the pointer. I'll check it out. Regards, Mat Bettinson Codeplay Tel: +44 (0)20 7482 3382 140-142 Kentish Town Rd, London, NW1 9QB http://www.codeplay.com

 [4/4] from: greggirwin:mindspring at: 18-Jan-2002 13:16


Hi Mat, << The key bit here is the ip. That's not a real ip, the server is behind NAT. It is however the dirty-net of the firewall so a request to the IP will work. However I need to get rugby to report some other IP to connect to rather than the bogus real/local IP which it has sent to my client. >> I had this same problem when importing stubs with Rugby. My solution, for the time being, is to use rexec directly, which works fine because you're specifying the IP yourself. I'm not sure how much Rugby is at the mercy of the underlying system in this regard, or if it's something that can be addressed in Rugby itself. --Gregg