From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: routing within same nic card
Date: Tue, 31 May 2005 01:31:13 -0500 [thread overview]
Message-ID: <429C04B1.60208@riverviewtech.net> (raw)
In-Reply-To: <00ca01c565a7$759eeaa0$d40aa8c0@winxp>
> Presently I have 2 NIC cards;
> eth1 = 212.119.xxx.98/30 directly connected to internet
> eth0 = 212.119.xxx.105/29 connected to LAN, with this setup everything
> is working fine
>
> now I need to add another network, since I cannot Add another NIC card,
> my solution is like this
> eth1 = 212.119.xxx.98/30 directly connected to internet
> eth0 = 212.119.xxx.105/29 connected to LAN1
> eth0:1 = 192.168.3.0/26 connected to LAN2
This seems reasonable enough.
> I already done the 3 lines below
> sysctl -w net.ipv4.ip_forward=1
> iptables -A FORWARD -s 192.168.3.0/26 -d 212.119.xxx.104/29 -j ACCEPT
> iptables -A FORWARD -s 212.119.xxx.104/29 -d 192.168.3.0/26 -j ACCEPT
This should also work as it allows traffic between the 192.168.3.0/26 212.119.xxx.104/29 networks. I would need to see the contents of your nat table POSTROUTING chain to make sure that you would not be NATing traffic that you would not want. Other than that I don't think you would have any problems. Seeing as how you are not filtering based on interface I don't think you will have any issues with it.
Grant. . . .
next prev parent reply other threads:[~2005-05-31 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 5:20 routing within same nic card Wennie V. Lagmay
2005-05-31 5:49 ` Taylor, Grant
2005-05-31 6:10 ` Wennie V. Lagmay
2005-05-31 6:31 ` Taylor, Grant [this message]
2005-05-31 6:51 ` Wennie V. Lagmay
2005-05-31 6:59 ` Taylor, Grant
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=429C04B1.60208@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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