From: "Juan Hernandez" <alucard@kanux.com>
To: netfilter@lists.netfilter.org
Subject: RE: help with routing/firewall
Date: Thu, 18 Dec 2003 14:08:08 -0400 [thread overview]
Message-ID: <007901c3c591$e420f200$3800a8c0@kanux1> (raw)
In-Reply-To: <20031218180112.66315.qmail@web20419.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Mmm im not sure if we are able to help you that way. that would be
making the job for you I guess. correct me if I'm wrong. Read some
manuals, get a grip in netfilter and if you don't understand something,
we'll help you.
Juan
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Fred Gurn
Sent: jueves, 18 de diciembre de 2003 14:01
To: netfilter@lists.netfilter.org
Subject: help with routing/firewall
Hi,
I have set up suse linux as bridge/firewall.
Simple configuration.
eth0 internet
eth1 local net
Everything accepted from eth1, nothing from eth0, traffic from eth1 is
routed to internet.
IP forwarding is enabled.
From local net I can ping eth1 and eth0 (that means machine is routing
packets), but I cant go outside eth0. Same happens when ther is no
firewall. What's the problem with routing?
What comands can I use to monitor what is happening with packets?
Tahnks in advance.
_____
Do you Yahoo!?
New
<http://pa.yahoo.com/*http:/us.rd.yahoo.com/evt=21260/*http:/photos.yaho
o.com> Yahoo! Photos - easier uploading and sharing
[-- Attachment #2: Type: text/html, Size: 8873 bytes --]
next prev parent reply other threads:[~2003-12-18 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 18:01 help with routing/firewall Fred Gurn
2003-12-18 18:08 ` Juan Hernandez [this message]
2003-12-18 18:15 ` Ian Hunter
2003-12-18 18:33 ` Jeffrey Laramie
2003-12-18 19:11 ` Togan Muftuoglu
2003-12-18 18:19 ` Jeffrey Laramie
2003-12-18 20:46 ` Rob Sterenborg
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 19:29 Togan Muftuoglu
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='007901c3c591$e420f200$3800a8c0@kanux1' \
--to=alucard@kanux.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.