Linux Netfilter discussions
 help / color / mirror / Atom feed
From: horape@tinuviel.compendium.com.ar
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: DNATing packets sent to the NATing box
Date: Sun, 14 Dec 2003 14:51:45 -0300	[thread overview]
Message-ID: <20031214175144.GB19059@tinuviel.compendium.com.ar> (raw)
In-Reply-To: <200312141716.40029.Antony@Soft-Solutions.co.uk>

> > It looks like the proxy is grabbing the packets first and then dropping
> > them directly onto the INPUT chain. Try disabling the proxy and release the
> > bound ports then try it again. Once the packets reach PREROUTING you can
> > DNAT them to another port.
> I could ubnderstand the proxy code managing to grab the packet off the wire 
> before netfilter (PREROUTING) sees it, but I don't see how it would then get 
> seen by the INPUT chain - as far as I know, it's not possible for a packet to 
> reach netfilter's INPUT chain without first going through the PREROUTING 
> chain.   If a packet bypasses one of these, it will bypass both.

> However, the idea of disabling the proxy, and then seeing if the LOG rules 
> show anything different, is a good one.

> How is the proxy connected to the socket?   Anything unusual?

The proxy is just a normal udp socket. (socket, bind, poll, recvfrom...)

What I'm doing is an IVR over H.323, the program receives and send rtp
packets until a conference is made, when the conference is made it starts
working as a proxy (ie, it gets the packet with a recvfrom and sends by
other socket with sendto) Nothing strange there.

> Antony

Saludos,
					HoraPe
---
Horacio J. Peña
horape@compendium.com.ar
horape@uninet.edu


  parent reply	other threads:[~2003-12-14 17:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 13:52 DNATing packets sent to the NATing box horape
2003-12-14 14:28 ` Jeffrey Laramie
     [not found] ` <200312140919.04832.JALaramie@Loudoun-Fairfax.com>
2003-12-14 15:26   ` horape
2003-12-14 15:51     ` Jeffrey Laramie
2003-12-14 16:04       ` horape
2003-12-14 16:55         ` Jeffrey Laramie
2003-12-14 17:16           ` Antony Stone
2003-12-14 17:35             ` Jeffrey Laramie
2003-12-14 17:51             ` horape [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-14 18:02 horape
2003-12-14 15:39 horape
2003-12-14  0:52 horape
2003-12-14  4:55 ` Joel Newkirk
2003-12-14  8:42 ` Antony Stone
2003-12-14 12:32   ` horape
2003-12-21  4:49 ` horape

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=20031214175144.GB19059@tinuviel.compendium.com.ar \
    --to=horape@tinuviel.compendium.com.ar \
    --cc=Antony@Soft-Solutions.co.uk \
    --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