[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
On Fri, Dec 05, 2003 at 05:58:19PM +0000, Simon Waters wrote: > For various reasons I don't pretend to understand we want to forward > https requests from one machine on our LAN to another. > > Set up IP forwarding, plaguarised a script from the Internet, and nothing. > > Set up "echo" on port 7, changed "443" to "7" in the firewall script, > and bingo it worked first time. > > Is there any reason to expect https to be different? It certainly is possible to do this, otherwise https://www.st-peters-high.devon.sch.uk wouldn't work :) > I wondered if it was possibly existing processes on the forwarding box > that try to do the same thing (broken https forwarding), but I don't > think the should even see the packets if the are altered in a > "PREROUTING" rule. netstat -nat |grep 443 should show if anything has the port open for listening. > We have lots of other ways of doing this, but I am perplexed as to why > port forwarding doesn't just work. Is it making any kind of connection at all? -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.