From: cbaker@bbbscentralohio.org
To: netfilter@lists.netfilter.org
Subject: Re: To REDIRECT, DNAT or something else
Date: Tue, 26 Nov 2002 09:40:35 -0500 [thread overview]
Message-ID: <3DE34193.8401.55E2B99@localhost> (raw)
In-Reply-To: <F168SlVviFluZw0VclX000110a1@hotmail.com>
I know that this doesn't really answer the question. But the best
strategy is to have a firewall all by itself. If you have an old 486
around, you could try Coyote Linux <coyotelinux.com>. It boots and
runs off a floppy.
On 25 Nov 2002 at 18:43, Joel Linuxdude wrote:
> I just had a small question (maybe dumb, I dont care).
>
> My firewall PC is also my DNS server (caching), gateway to
> the internet via cable modem, web server, ftp server and
> later my proxy server.
>
> Do I need to REDIRECT packets coming into eth0 (from the
> cable modem) to the firewall itself?? I know, the packets
> are suppose to go right to INPUT chain but people over
> the internet can no longer access my WWW, FTP or TELNET
> daemon. I fear A) The cable modem company are blocking
> the use of servers or B) I screwed up somewhere in my
> firewall script.
>
> HOW CAN I MAKE SURE ALL TCP/UDP PORT 20,21,22,23,80,443
> GO FROM CABLE MODEM ON ETH0 TO MY FIREWALL AND NOT GET
> FORWARDED OVER ETH1 TO MY LAN?
>
> Thank you!
>
> _________________________________________________________________ Add
> photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
>
Chris Baker -- technical specialist
614-839-2447x108
cbaker@bbbscolumbus.org
Big Brothers Big Sisters of Central Ohio
www.bbbscolumbus.org
prev parent reply other threads:[~2002-11-26 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 23:43 To REDIRECT, DNAT or something else Joel Linuxdude
2002-11-26 14:31 ` Ben Russo
2002-11-26 14:40 ` cbaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DE34193.8401.55E2B99@localhost \
--to=cbaker@bbbscentralohio.org \
--cc=cbaker@bbbscolumbus.org \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox