|
|
All,
Some of you may have
read my article on configuring the NAT at www.ignite400.org in the Evelyn Porter
Institute section of the web site, tried it out, and had
difficulties.
I sent several hours with the NAT developer over the past couple of days and the
issues are routing.
Assume the
following:
You are mapping a
public address 156.96.80.70 defined to the AS/400 via an Ethernet adapter to a
private address 10.11.20.70 defined on a token ring
adapter. You
configure an IBM HTTP Server with bind specific=YES on
10.11.20.70.
You then define
mapping rules as I illustrated in the article and enable the
NAT.
You can't access
your web server.
The issue is now a
routing issue. This is what is going on.
1. An IP
packet comes in to the machine via the internet from say 206.111.20.5
addressed to 156.96.80.70
2. The NAT
intercepts the packet and changes the TO address from 156.96.80.70 to
10.11.20.70.
3. The HTTP
server gets the request and processes.
4. The HTTP
server formats the request and sends it to 206.111.20.5
IF you do not have a
route defined on your AS/400 to your public Internet router, the packet gets
stuffed in the big bit bucket in the SKY!
You must define a
default route pointing to your Internet router for this to work. You then
need subnet routes pointing to your internal LAN router
so that your
internal traffic (on the 10... subnet) is routed properly. Once the
routing is worked out NAT works like a dream!
Bob C. |
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
