From: "Sebastiao Antonio Campos \(GWA\)" <sa.campos@datasulsp.com.br>
To: Netfilter list <netfilter@lists.netfilter.org>,
Sertys <sertys@supportivo.org>
Subject: Neighbour table overflow
Date: Wed, 23 Mar 2005 11:08:34 -0300 [thread overview]
Message-ID: <000901c52fb2$ee024ee0$080211ac@PIVT> (raw)
After I had applied the solution bellow I got the follwing msg error:
Neighbour table overflow.
Tks
----- Original Message -----
From: "Sebastiao Antonio Campos (GWA)" <sa.campos@datasulsp.com.br>
To: "Netfilter list" <netfilter@lists.netfilter.org>; "Sertys"
<sertys@supportivo.org>
Sent: Tuesday, March 22, 2005 9:51 PM
Subject: Re: Two netwok cards to access the internet.
> Thanks.
>
> It is working good.
>
>
>
> ----- Original Message -----
> From: "Sertys" <sertys@supportivo.org>
> To: "Netfilter list" <netfilter@lists.netfilter.org>
> Sent: Tuesday, March 22, 2005 7:24 PM
> Subject: Re: Two netwok cards to access the internet.
>
>
> On Tue, 22 Mar 2005 18:54:26 -0300, Sebastião Antônio Campos
> <sa.campos@datasulsp.com.br> wrote:
>
> Well, that's easy. When you know the ports you want to map through the
> interfaces, just do
>
> iptables -t nat -A POSTROUTING -m multiport -p tcp -s 172.17.1.8 --dports
> 25,110,1723,1701,47 -o eth0 -j MASQUERADE
> iptables -t nat -A POSTROUTING -s 172.17.0.0/16 -o eth2 -j MASQUERADE
> or even better
> iptables -t nat -A POSTROUTING -s 172.17.0.0/16 -o eth2 -j SNAT
> --to-source $ETH2_IP
>
> Those are simple states, you might add --syn or -m state, it's a choice of
> yours anyway.
>
>
> > Hi!
> >
> > I have the following:
> >
> > A RedHat 9.0 with 3 Network cards: One we use in local network (eth1)
> > and the other (eth0 and eth2) to access the internet.
> >
> > I'd like to separate the traffic. In the eth0 use only with the e-mail
> > server (pop, smtp, 1723, 1701 and protocol 47) and the eht0 with others
> > traffis (http, https, msn....).
> >
> > I tried
> >
> > iptables -t nat -A POSTROUTING -o eth2 -s 172.17.1.8 -j MASQUERADE
> > (--this ip addrs is pop and smtp server)
> > iptables -t nat -A POSTROUTING -o eth0 -s 172.17.0.0/16 -j MASQUERADE
> >
> > But when I did this I could not access the port 1723, 1701 and protocol
> > 47 using the eth2.
> >
> > I tried too use only iptables -t nat -A POSTROUTING -o eth2 -s
> > 172.17.0.0/16 -j MASQUERADE
> >
> > And I got the same prob.
> >
> > If I use iptables -t nat -A POSTROUTING -s 172.17.0.0/16 -j MASQUERADE
> >
> > I will get a success access. Only when I use iptables -t nat -A
> > POSTROUTING -s 172.17.0.0/16 -j MASQUERADE (without -o eth2 or -o
eth0).
> >
> >
> > Who could help me?
> >
> > Thanks
> >
> >
> > Sebastiгo Antфnio Campos
> > Infojoi Computadores Ltda
> > Joinville -SC - R. Iririъ, 3587
> > Cml. (47) 437-0796 - Cel. (47) 9927-5349
> > tiao@infojoi.com.br
> > http://www.lupusnet.com.br
>
>
>
> --
> www.supportivo.org
>
> I can't stop myself checking for pigs in the outlets. Everybody thinks i'm
> a punk, cause of the hairstyle(220V).
> end
>
next reply other threads:[~2005-03-23 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 14:08 Sebastiao Antonio Campos (GWA) [this message]
2005-03-23 14:23 ` Neighbour table overflow Jason Opperisano
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 0:42 ro0ot
2005-01-05 2:25 ` Jason Opperisano
2004-10-28 2:25 John Pearson
2004-10-26 17:39 Dominik Karall
2004-10-26 21:23 ` Chris Wedgwood
2004-10-26 22:10 ` Dominik Karall
2004-10-26 21:52 ` Ernst Herzberg
2004-10-26 22:11 ` Dominik Karall
2004-10-26 23:06 ` David S. Miller
2004-10-26 23:58 ` Wichert Akkerman
2004-10-27 0:30 ` Dominik Karall
2002-11-26 14:40 more than 1 source ip Ben Russo
2002-11-26 18:39 ` Neighbour table overflow g_netfilter
2002-11-26 18:38 ` Ard van Breemen
2002-11-28 16:40 ` Roberto Nibali
2002-11-27 4:08 ` Arnt Karlsen
2001-01-22 14:38 Daniel Furse
2001-01-22 15:22 ` Wolfgang Denk
2001-01-22 11:33 Daniel Furse
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='000901c52fb2$ee024ee0$080211ac@PIVT' \
--to=sa.campos@datasulsp.com.br \
--cc=netfilter@lists.netfilter.org \
--cc=sertys@supportivo.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.