Linux Netfilter discussions
 help / color / mirror / Atom feed
From: I.S.Kuten <i.kuten@sam-solutions.net>
To: netfilter@lists.netfilter.org
Subject: Re: fake ping reply
Date: Thu, 4 Sep 2003 20:10:00 +0300	[thread overview]
Message-ID: <20030904201000.40c0e6a4.i.kuten@sam-solutions.net> (raw)
In-Reply-To: <20030904162444.GB31513@cannon.eng.us.uu.net>

On Thu, 4 Sep 2003 12:24:44 -0400
Ramin Dousti <ramin@cannon.eng.us.uu.net> wrote:

> On Tue, Sep 02, 2003 at 04:50:26PM +0300, I.S.Kuten wrote:
> 
> > Hello ,
> > 
> > i wanted to setup iptables , when someone pings my box , echo-reply
> > would come from other machine then mine .
> 
> A very strange question. When the client sends you a echo-request, it
> expects to receive echo-reply from the same IP address. If some other
> IP address sends the echo-reply, it will simply get dropped by the OS
> on the client, as there is no match for this bogus packet...
> 
> Now, what do you want to achieve with this? Fool the client that his
> ping, pinged someone else??
> 

I'd like to archive 

when i receive ping from say 192.168.0.1 , i send ping to another ip 192.168.0.2 receive echo-reply 
and send echo-reply back to 192.168.0.1 with same type
(ping i mean icmp with some type)



sorry 
> > i wanted to setup iptables , when someone pings my box , echo-reply
> > would come from other machine then mine .
this is not quite correct what i wanted


> If you feel unconfortable with someone pinging you, just drop them...
> 
> Ramin
> 

> > 
> > I've tried to play with PREROUTING & POSTROUTING chains but had no success .
> > 
> > Anyone has solution ?
> > 
> > 
> 


  reply	other threads:[~2003-09-04 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 13:50 fake ping reply I.S.Kuten
2003-09-04 16:24 ` Ramin Dousti
2003-09-04 17:10   ` I.S.Kuten [this message]
2003-09-04 19:32   ` Chris Brenton
2003-09-04 20:04     ` Ramin Dousti

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=20030904201000.40c0e6a4.i.kuten@sam-solutions.net \
    --to=i.kuten@sam-solutions.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