From: Edmundo Carmona <eantoranz@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Problem reexplained.....
Date: Tue, 27 Sep 2005 12:53:35 -0400 [thread overview]
Message-ID: <65aa6af90509270953188aa596@mail.gmail.com> (raw)
In-Reply-To: <20050927164947.43318.qmail@web54709.mail.yahoo.com>
I would say it's a simple thing you are missing to consider. Maybe the
IPs you are using are not right... or the interfaces are not correct.
double check.
then start to build rules one by one, and testing them... it normally
shouldn't fail.
In case you are not sure if it's the kernel, get a Live-CD distribution and try.
On 9/27/05, Alaios <alaios@yahoo.com> wrote:
> I have restarted my pc just for being sure.. i have
> run your commands but the tcpdump -i eth0 -vv -n give
> nothing :(
> it doesnt work :(
> I think its time to start debugging. plz suggest me
> how to use efficiently logging so as to find out what
> the is the problem
>
> --- Edmundo Carmona <eantoranz@gmail.com> wrote:
>
> > Well.. first easiest (probably insecure) attempt:
> >
> > iptables -P FORWARD ACCEPT
> > iptables -t nat -A PREROUTING -d 143.233.222.77 -j
> > DNAT
> > --to-destination 10.2.4.2
> >
> > echo 1 > /proc/blah/blah
> >
> > That should stablish comunication between internet
> > and the 10.2.4.2
> > box (started from the internet).
> >
> > On 9/27/05, Alaios <alaios@yahoo.com> wrote:
> > > Let me reexplain the problem plz
> > > >From src 143.233.222.253 starts some traffic that
> > goes
> > > to the 143.233.222.77 this is the eth1 of the
> > laptop
> > > The laptop has also one more interface the
> > 10.2.4.1
> > > that is connected back to back (cross cable) with
> > the
> > > interface of an other pc with ip address 10.2.4.2
> > > IO want the traffic that reaches 143.233.222.77
> > reach
> > > the 10.2.4.2
> > > This is the first step.. when i succesfully
> > implement
> > > this then the next step is to forward this traffic
> > > from the pc to a second pc... ( i ll use the same
> > > methodology if step one works)
> > > So now we can only focus to the first step
> > > Plz take in mind that i dont have any firewall
> > enables
> > > /proc/sys/net/ipv4/ip_forward is set to 1. I have
> > no
> > > other iptables rules applied... I will only apply
> > what
> > > u ll write to do..
> > > Before applying any iptables rules firstly i do
> > > iptables -F
> > > iptables -F -t nat
> > > (if more flush commands are necessary plz say it
> > so)
> > > So i need your help to implement this simple task
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > >
> > >
> >
> >
>
>
>
>
> __________________________________
> Yahoo! Mail - PC Magazine Editors' Choice 2005
> http://mail.yahoo.com
>
next prev parent reply other threads:[~2005-09-27 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 16:14 Problem reexplained Alaios
2005-09-27 16:26 ` Edmundo Carmona
2005-09-27 16:49 ` Alaios
2005-09-27 16:53 ` Edmundo Carmona [this message]
2005-09-27 17:30 ` AragonX
2005-09-28 9:49 ` Jörg Harmuth
2005-09-28 10:19 ` Jörg Harmuth
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=65aa6af90509270953188aa596@mail.gmail.com \
--to=eantoranz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox