Subj : Injoy To : Darrell Salter From : Mike Luther Date : Fri Mar 22 2002 04:45 am Darrell .. I got in on this thread late here. DS> There are many advantages to having Injoy do it. ;) DS> HTTP is just the first server I plan to address in this DS> fashion. DS> Here's the relevant snippet from my rules file ... DS> 192.168.0.3 is my Injoy Internet Gateway DS> 192.168.0.9 is the Linux box running MySQL and Apache/PHP DS> Naturally, I want http to take a round-trip to the Linux box. DS> PORTMAP-WWW-IN Rule-Status = Enabled, DS> Comment = "Map WWW requests to the DS> Linux box at 192.168.0.9", DS> Source = "any", DS> Destination = "192.168.0.3", DS> Service = 80, DS> Rule-Action = Portmap, DS> Mapping-Dest-IP = "192.168.0.9", DS> PORTMAP-WWW-OUT Rule-Status = Enabled, DS> Comment = "Map WWW requests from 192.168.0.9 out", DS> Source = "192.168.0.9", DS> Destination = "any", DS> Source-Port = 80, DS> Rule-Action = Portmap, What does enablement of logging under Injoy 2.3 tell you about the above? I assume this is the rules operation built into the Injoy product? The Injoy product, as opposed to the IJFIRE professional version may have different limitations, to my feeble memory about what number of things it can do,perhaps both direct on a one-step basis, as well as second stepped like you propose. I'm using IJFIRE behind a ZyXel Prestige 310 broadband router here for a similar thing and it is working with that product. Somewhere in my feeble brain I recall a level-of-service limitation on Injoy, but I'm no expert at any of this, I assure you. Secondly, every tech question I've ever asked of the Injoy tech support operation by Email has been pretty promptly answered to me. What do they comment about it? --> Sleep well; OS/2's still awake! ;) Mike @ 1:117/3001 --- Maximus/2 3.01 * Origin: Ziplog Public Port (1:117/3001) .