[ previous ] [ next ] [ threads ]
 
 From:  "Joe Doran" <joe at jbdww dot com>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Internal to Lan
 Date:  Fri, 18 Jul 2003 08:19:19 -0500
Hey Fred,
	Thanks for the reply. I have figured it out. I had to modify
monowalls LAN rules for ipfillter. In particular having the time server
(msntpd) inside monowall to go to an internal LAN machine to get the
current time, this was being blocked.

Thanks
Joe

-----Original Message-----
From: Fred Wright [mailto:fw at well dot com] 
Sent: Thursday, July 17, 2003 11:51 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Internal to Lan


On Wed, 16 Jul 2003, Joe Doran wrote:

> 	Here is a neat question. I have a peace of software that grabs a
> flat file from a web server every so many hours and stores the data in
> memory. So I put it in m0n0wall for a test. The data is grabbed from
an
> internal web server on the LAN side, but it cannot connect to the LAN
> web server, but if I go out on the WAN side to get the data, it works.

You'll have to be more specific.  How can you go "out on the WAN side"
to
the same server, or are those different servers?  Is this one of those
cases where you're relying on NAT redirection to make the webserver
appear
to have a different IP address to teh world?

> Now I tried ping both the LAN side, and then WAN side from m0n0walls
> internal ping program, and everything seams to work.

Pinging what?  The m0n0wall's own interfaces?  Some other server in each
case?

					Fred Wright


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch