On Sun, Dec 10, 2000 at 01:31:54AM -0700, Sean Reifschneider wrote:
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x T=64 (#37)
Dec 10 01:02:55
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x T=64 (#37)
Dec 10 01:02:55 meg kernel: Packet log: output REJECT eth0 PROTO=6 166.84.147.
124:4396
At 01:31 AM 12/10/00 -0700, Sean Reifschneider wrote:
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6
166.84.147.
124:3687 206.26.89.202:25 L=1064 S=0x00 I=46413 F=0x T=64 (#37)
Dec 10 01:02:55 meg kernel:
Steve Manes [EMAIL PROTECTED] writes on 10 December 2000 at 10:31:24 -0500
At 01:31 AM 12/10/00 -0700, Sean Reifschneider wrote:
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6
166.84.147.
124:3687
At 08:47 AM 12/10/00 -0800, Phil Oester wrote:
Your output rule for port 25 is definitely the problem. Contrary to your
belief, it is filtering outbound traffic on eth0. Personally, I don't think
that's such a good idea - my firewall allows everything outbound, and only
filters inbound. Try
* Steve Manes [EMAIL PROTECTED] [001210 12:06]:
At 08:47 AM 12/10/00 -0800, Phil Oester wrote:
Your output rule for port 25 is definitely the problem. Contrary to your
belief, it is filtering outbound traffic on eth0. Personally, I don't think
that's such a good idea - my firewall allows
On Sun, 10 Dec 2000, Steve Manes wrote:
I know what port 25 is and, no, it's not blocking incoming connections. It
seems to be blocking outgoing connections. But if you look at the script
you'll see that port 25 is open both ways:
# SMTP server (25)
#
ipchains -A
On Sun, 10 Dec 2000, David Dyer-Bennet wrote:
# SMTP server (25)
#
ipchains -A input -i $EXTERNAL_INTERFACE -p tcp \
--source-port $UNPRIVPORTS \
-d $IPADDR 25 -j ACCEPT
ipchains -A output -i $EXTERNAL_INTERFACE -p tcp ! -y \
-s $IPADDR
On Sun, 10 Dec 2000, Peter Green wrote:
Most likely, you have a rule in the output chain that has a higher
precendence that is blocking the outgoing traffic. By adding a rule like:
Or a 'default' REJECT rule is catching it because the ACCEPT higher up is
too specific.
/sbin/ipchains -I
On Sun, Dec 10, 2000 at 10:31:24AM -0500, Steve Manes wrote:
I know what port 25 is and, no, it's not blocking incoming connections. It
seems to be blocking outgoing connections. But if you look at the script
you'll see that port 25 is open both ways:
Ahh, I didn't notice the output rule.
Am Sonntag, 10. Dezember 2000 09:39 schrieb Timothy Legant:
On Sun, Dec 10, 2000 at 01:31:54AM -0700, Sean Reifschneider wrote:
On Sun, Dec 10, 2000 at 02:51:24AM -0500, Steve Manes wrote:
Dec 10 01:02:49 meg kernel: Packet log: output REJECT eth0 PROTO=6
166.84.147. 124:3687
/ipchains -A output -j ACCEPT -i $EXTERNAL_INTERFACE -p tcp -s $IPADDR
25 -d 0.0.0.0/0
-Phil
-Original Message-
From: Steve Manes [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 10, 2000 7:31 AM
To: Sean Reifschneider
Cc: [EMAIL PROTECTED]
Subject: Re: IPCHAINS and Qmail
At 01:31 AM 12
I installed 'ipchains' on my Redhat 7.0 mail server today. Not being a
firewall guru, I had the www.linux-firewall-tools.com/linux/firewall/ site
build me a script. I had pretty good luck with it on a web server but I've
run into a problem with Qmail. As soon as I activate the firewall,
13 matches
Mail list logo
