Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Mar 2004 13:54:16 -0500
From:      "Thomas S. Crum - 1WISP, Inc." <tscrum@1wisp.com>
To:        <whizkid@ValueDJ.com>, <Barbish3@adelphia.net>
Cc:        freebsd-ipfw@freebsd.org
Subject:   RE: Problems connecting to port 25
Message-ID:  <02d801c40863$72353290$d452eb44@wolf>
In-Reply-To: <61088.208.253.246.93.1079106884.squirrel@www.ValueDJ.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
I found it much easier to reload firewall rules with:

sh /etc/rc.firewall

no need to reboot.

Best,
Tom

-----Original Message-----
From: owner-freebsd-ipfw@freebsd.org
[mailto:owner-freebsd-ipfw@freebsd.org] On Behalf Of whizkid@ValueDJ.com
Sent: Friday, March 12, 2004 10:55 AM
To: Barbish3@adelphia.net
Cc: freebsd-ipfw@freebsd.org; whizkid@ValueDJ.com
Subject: RE: Problems connecting to port 25

> Your ISP has closed ports 25 and 80 for all their non-commercial
> accounts.
> This is very normal, and becoming standard among ISP's.
>
Thanks for all your comments.  I pay for a Business type DSL with 5 ip
addresses and I am allowed to run all my own servers.  I didn't have
this
issue until I re-complied my kernel with the IPFIREWALL option.  I have
now resloved the issue.

Basically what I did was move the rule for port 25 to the top of the
list.
 Changed the add 04010 to 03001.  When I did a nmap on the localhost I
could see port 25 open, but when I did the nmap from one of my other
servers on the same subnet, it did not list port 25.  A quick reboot of
the server, and all is well.

Thank you all for your comments.
_______________________________________________
freebsd-ipfw@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw
To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?02d801c40863$72353290$d452eb44>