Further information - If 10.10.18.25 and 10.10.18.54 are both defined interfaces on a single iSeries, the filter rules work fine. Unfortunately, this is not what I need to do - I need to use one system as a "traffic cop" to redirect requests to a second system. If 10.10.18.25 and 10.10.18.54 are on separate systems, the same filter rules as above do not work. I can only conclude that, when the IP filter rules change the IP address in the packet, the packet does not get put back out on the network. Can anyone confirm or deny this? Thanks, Steve "Steve McKay" <steve.mckay@xxxxxxxxxxxxxx> wrote in message news:brdbpp$mr$1@xxxxxxxxxxxxxxxx > Greetings list! > > I am attempting to forward HTTP requests from one iSeries Apache webserver > to another on a private network (not VPN, just a non-Internet Ethernet > network). I have created the following IP packet rules: > > ADDRESS frontend IP = 10.10.18.25 TYPE = BORDER > ADDRESS backend IP = 10.10.18.54 TYPE = TRUSTED > HIDE backend:80 BEHIND frontend:80 TIMEOUT = 16 MAXCON = 512 JRN = > OFF > > When I activate the rules and point the browser to 10.10.18.25, I get a > "Cannot find server or DNS error" message but if I go directly to > 10.10.18.54, I get the expected website. > > Any ideas? > > > > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/web400 > or email: WEB400-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. > >
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.