From: Jeremy Tregunna <jtregunna@...>
Date: 2006-10-04T06:52:07+09:00
Subject: Re: NET::HTTP behind a firewall?


> On 10/3/06, Joe Regular <kristapestry@yahoo.com> wrote:
>>
>> I recently deployed an app to my production server that accesses  
>> other
>> websites via NET::HTTP. Due to my firewall (iptables), the app is  
>> unable
>> to access the other sites.
>>
>> What ports should I open/changes should I make to my firewall config
>> script (KISS) to enable ruby to make the appropriate outgoing  
>> requests?
>

Outgoing connections are almost always made on high ports. It doesn't  
matter what you're using to connect out, the fact that you're making  
a client request to some remote server on some port, will cause your  
client ip:port to be <ip you're going out over>:<some high port,  
probably over 10000>.

So be sure you open up say 10000 - 65535 outgoing tcp

If this still doesn't work, there's probably some sort of transparent  
firewall between your router and your destination blocking this.

--
Jeremy Tregunna
jtregunna@blurgle.ca