Firewall woes

Im still new to torque but so far I have a dedicated server running on Linux with its own master server thanks to Thomas "Man of Ice" Lund's perl prototype.

In order to get the MasterServer working in perl I had to modify the IO::Socket to include a LocalHost address before it would pass through my firewall.( otherwise the firewall did not have a source ip address to check against its rule, or so I thought).

I was having a simular problem when my client would try to connect to the game server with the server recieving information from the client but the client unable to recieve information from the server. I can set my client in the DMZ zone of the router and work however. (The client is still running a software firewall which seems to work with the connection fine).

From what I found in the code Torque only sends the data part to the socket and the IP header (where the firewall would get the source address from) is left to the OS network stack so I no longer believe this to be the problem and if I understand correctly by default port 28002 is used to contact and communicate with the master server and is initiated by the client (shouldn't be a problem there) My server is listening on port 28000 and recieves the request fine. Is the server not using the same connection made by the client to send information back? I havent found anything to suggest otherwise.