From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: Problem reexplained.....
Date: Wed, 28 Sep 2005 11:49:45 +0200 [thread overview]
Message-ID: <433A6739.7090904@mnemon.de> (raw)
In-Reply-To: <20050927161440.60437.qmail@web54707.mail.yahoo.com>
Alaios 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
First do as AragonX recommended. There is no sense in continuing if the
basics aren't ok. Additionally check if the default gateway of 10.2.4.2
is set to 10.2.4.1. Then try Edmundo's approach and add
iptables -t nat -A POSTROUTING -o eth1 -j SNAT \
--to 143.233.222.77
Question: Is 143.233.222.77 a dial-up interface ?
If it doesn't work tcpdump on 143.233.222.77, then on 10.2.4.1,...,
briefly: find the point, where it breaks. You may post the dumps. Some
surrounding information could help too: ifconfig, route -n,
iptables-save, hmm - I think that should do.
Good luck,
Joerg
next prev parent reply other threads:[~2005-09-28 9:49 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
2005-09-27 17:30 ` AragonX
2005-09-28 9:49 ` Jörg Harmuth [this message]
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=433A6739.7090904@mnemon.de \
--to=harmuth@mnemon.de \
--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