Hello, I am sort of a newbie to IPFW for FreeBSD-5.2.1. I have never
used it and need some help with the configuration. Ok here goes if
anyone can help.
I compiled IPFIREWALL into the kernel with the options to DEFAULT TO
ACCEPT ALL and the VERBOSE=50 option. With the support for IPFW in the
k
Hi Jonathan,
> will be able to work. My box is located at a datacebter and my box is
> allocated with about 90 IP addresses (and also the main
> server IP which
> was given to me when i first purchased the line). I would
> like to know
> how to configure /etc/rc.firewall to support my MAIN ip
Of Jonathan
Sent: Wednesday, August 04, 2004 10:00 PM
To: [EMAIL PROTECTED]
Subject: IPFW Configuration
Hello, I am sort of a newbie to IPFW for FreeBSD-5.2.1. I have never
used it and need some help with the configuration. Ok here goes if
anyone can help.
I compiled IPFIREWALL into the kernel
Gentleones,
I have a commercial website/mail product running on a box. Unfortunately,
the product is not so smart and when it needs to bounce something, it
ignores the SMTP "Always Relay Via" setting and attempts to connect directly
to the mail exchanger for the domain it's bouncing to.
So what I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 31 October 2004 21:39, Bill Eccles wrote:
> Gentleones,
>
> I have a commercial website/mail product running on a box. Unfortunately,
> the product is not so smart and when it needs to bounce something, it
> ignores the SMTP "Always Relay Via
Actually, you bring up an interesting point that, yes, I'd forgotten about
natd. However, I realized after watching a tcpdump that the outgoing port is
a random port--only the destination port is 25 on the upstream box.
So, somehow I have to rig up something that listens for an SMTP connection
des
> I believe you'll have one additional problem to resolve. Even if you
> successfully modify the destination IP address and get it pointed to
> the upstream server, the source IP will be unmodified and will still
> be the originator. Since the source IP is unmodified - the upstream
> mail server wi
Actually, the original question contains the tidbit that the machine
doing the serving is also the problem child, i.e., all of the traffic
that I need to redirect is being produced on the same box from that
box's SMTP server.
Thanks for the explanation, though. Low-level TCP stuff is not my
fo
