> For instance can you ensure that you can connect to the web server from > the redirector(the machine running relayd) by using netcat? > > Run this on the web server. > > $ nc -l 1234 > > and from the relayd machine try > > $ nc 192.168.4.78 1234
Well this worked out : # nc 192.168.4.78 80 GET / <html><body><h1>It works! web01 </h1></body></html> # nc 192.168.4.76 80 GET / <html><body><h1>It works! web02 </h1></body></html> > For instance have you ensured that the web server and the clients are in > separate networks connected/routed by the relayd machine? My nodes have the relayd machine as default gateway. Is that sufficient ? > There are certain unwritten ground rules to be followed for rdr to work. > > For instance if your reverse path does not match the forward path > between the client and the server, then > rdr will fail and the TCP handshake will not go through. Okay, as a client we have a firewall that serves as our default gateway for our laptops which 192.168.4.254. The relayd server has that as a default gateway as well. But the nodes have the relayd server as their default gateway so the forward/return should be identical in my configuration if I'm not mistaken. > Basically rdr should get a chance to see the packets in both directions > to function properly. Thanks for your kind attention to my problem, I'm still confused though, I'll go ahead and tcpdump this and see where it takes me. I would appreciate greater understanding of this. Sincerely, Uday
