Ray Olszewski wrote:
> As I look through the firewall ruleset ... the input chain specifically
> ... I don't see a rule to ACCEPT port-25 traffic. Nor do I see one to
> ACCEPT port-80 traffic (but you did say the Web server worked, didn't
> you?).
>
> WIth that as a hint, I *think* I've spot
As I look through the firewall ruleset ... the input chain specifically ...
I don't see a rule to ACCEPT port-25 traffic. Nor do I see one to ACCEPT
port-80 traffic (but you did say the Web server worked, didn't you?).
WIth that as a hint, I *think* I've spotted the error in the config file.
I
> Thanks for responding, Ray.
> I have added the diagnostic info described at leaf support.
A couple of comments...I think your main problem is you're not allowing
the mail packets through the input firewall rules. Since you're using a
PRIVATE DMZ, and port-forwarding your external firewall IP t
Thanks for responding, Ray.
I have added the diagnostic info described at leaf support.
I'm running Dachstein linux 4.0.6 with private.network at 192.168.1 and
dmz.network at 192.168.2.
The web server on dmz.network can be reached from the net.
Mail sent to the mail server on dmz.network returns
At 11:51 PM 10/4/02 -0400, Bob Skaroff comcast.net wrote:
>I'm running Dachstein linux 4.0.6 with private.network at 192.168.1 and
>dmz.network at 192.168.2.
>The web server on dmz.network can be reached from the net.
"the" net? Do you mean the Internet? If so, this is inconsistent with my
tests
I'm running Dachstein linux 4.0.6 with private.network at 192.168.1 and
dmz.network at 192.168.2.
The web server on dmz.network can be reached from the net.
Mail sent to the mail server on dmz.network returns an error message to the
sender.
I've tried varying the coding of the DMZ_OPEN_DEST and DM
