From: Rudi Starcevic <tech@wildcash.com>
To: netfilter@lists.netfilter.org
Subject: Re: dumb question...route from local eth1 to eth2 and vice versa
Date: Thu, 01 Dec 2005 20:18:20 +1000 [thread overview]
Message-ID: <438ECDEC.20106@wildcash.com> (raw)
Hi,
>> I think ip_a_route_1.sh is way too difficult for this setup. I didn't
>> even read it all through (saw something about tables, rules
>> and prio)..
Very true, but it's the only way I know.
>> ifconfig eth0 192.168.3.10 netmask 255.255.255.0 up
>> ifconfig eth1 192.168.1.1 netmask 255.255.255.0 up
>> route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.3.254
Nice one .....
>> You did not set the policy of FORWARD to DROP. It will DROP
>> nothing.
>> You did not set the policy of OUTPUT to DROP. The OUTPUT >> rules are
useless because everything will be accepted, even
>> without these rules.
Yes sorry. I didn't cut'n'paste that part of the script in.
It's my fault for trying to hurry out a quick post just before I left work.
>> He just needs to allow
>> forwarding between these to interfcaes and let routing do the
>> rest.
>> Your scripts are doing something different.
Yes ... but I thought it would be handy to have net too so
all the boys and girls and play online together as well :-)
Using things like tables, rules and prio also puts one in place
to do QOS on the network traffic with the tc command.
Don't want those pesky emails, downloads and other important
stuff to lag out the gaming connection ... :-) lol .....
Cheers,
Rudi
next reply other threads:[~2005-12-01 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 10:18 Rudi Starcevic [this message]
2005-12-01 21:04 ` dumb question...route from local eth1 to eth2 and vice versa Anthony Sadler
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 2:43 Joel F
2005-12-01 3:13 ` Jesse Gordon
2005-12-01 3:22 ` Thomas Kuiper
2005-12-01 3:36 ` Jesse Gordon
2005-12-01 6:44 ` Rob Sterenborg
2005-12-01 6:59 ` Rudi Starcevic
2005-12-01 8:49 ` Rob Sterenborg
2005-12-01 7:05 ` Rudi Starcevic
2005-12-01 7:08 ` Rudi Starcevic
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=438ECDEC.20106@wildcash.com \
--to=tech@wildcash.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.