NAT working fine for ping, but not for HTTP
|
(Sorry in advance for this ridiculous question, but I've scanned through the docs and can't find anything to explain my problem).
I've installed the NAT patch into my 2.0.36 kernel (I used Warren Chartier's 2.0.36-nat-arp.patch), and I've yet to get NAT working for anything but ping. Here's the cast of players: The Linux machine with NAT installed. It has two NICs on it, one for each subnet it's attached to (I'll call the IP addresses nat-net1 and nat-net2). An HTTP server on net1 (I'll call it http-net1). I'm trying to make this one look like it's on net2 (I'll call that address bogus-net2). A test machine on net2 (I'll call it test-net2). From the NAT machine I can ping and HTTP into http-net1. From the test machine, I can add a route to http-net1 through nat-net2, and then ping and HTTP http-net1. Now I add a NAT rule:
ipnatadm -v -O -i -b -D bogus-net2/32 -N http-net1 and I update the routing table on the test machine:
route add -host bogus-net2 gw nat-net2 With this rule in place, the test-net2 machine can ping bogus-net2, but can't HTTP into it. The NAT machine can ping and HTTP into bogus-net2. I'm at a loss to as to the solution. Does anyone have a clue what I'm doing wrong?
|
