On Tue, May 28, 2002 at 07:53:18PM +0100, Antony Stone wrote: >On Tuesday 28 May 2002 7:42 pm, George Georgalis wrote:
>> Also, I was wondering why a connect from the LAN port 50422 (to the >> firewall) does nat to 192.168.0.1:22? It works from the internet.... > >Er, I don't quite understand the question, but if it's the usual one, which >is "my firewall is DNATting external address A to internal address B, and it >works when I connect to A from the outside, but it doesn't work when I >connect to A from the inside (although it does work if I connect to B from >the inside)", then the answer is routing. > >Put simply, to repond to an external client, B has to reply through the >firewall, so "it works". To repond to an internal client, though, B does >not route the reply through the firewall, so it doesn't work. Yeah, I think that's it. Guess I need to MASQ the lan to lan port forwarding, but that's a bummer. :) // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:[EMAIL PROTECTED] File, Print, DB and DNS Servers. http://www.galis.org/george
