All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasca <rasca-ml@triad.de>
To: netfilter@lists.netfilter.org
Subject: port forwarding with one interface to trace traffic?
Date: Wed, 21 Jan 2004 16:45:55 +0100	[thread overview]
Message-ID: <400E9EB3.4070309@triad.de> (raw)

Hi IP-gurus,

I want to setup a specific port forwarding to trace the
ip traffic between a macos9 and a hp net printer to debug
a spooler problem.

I thought the port forwarding feature of linux/iptables
would be nice to do that. But until now I wasn't able
to get it running ;-(

May be some one can help here. The setup is quite simple.

* one class C net (192.168.10.0)
* a linux box with one interface (eth0), kernel 2.4.24
   and iptables 1.2.9 (192.168.10.156

* macos9 machine with 9.2.x (192.168.10...)

* HP laser printer with network interface (192.168.10.9)

I want to configure the Mac to print to the linux box.
The linux box should do port forwarding to the hp printer.
So I can use "ethereal" or what ever to dump the traffic.

Because it's not a firewall all chains have as default
"accept".

I added the following rule (which seems not to be enough,
cause the printing freezes):

iptables -t nat -A PREROUTING -p tcp --dport 515 \
	-d 192.168.10.156/32 -j DNAT --to-dest 192.168.10.9:515

Any ideas?

thx + cu
  rasca


-- 
_______________________________________________________________
| Triad Berlin Projektgesellschaft mbH | http://www.triad.de/ |



             reply	other threads:[~2004-01-21 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 15:45 Rasca [this message]
2004-01-21 16:16 ` port forwarding with one interface to trace traffic? Caracal - G. Hostettler
2004-01-21 16:46   ` Rasca
2004-01-21 22:07 ` Antony Stone
2004-01-22 13:16   ` Jeffrey Laramie
2004-01-22 13:36     ` Rasca
2004-01-22 13:39     ` PPTP and GRE Jan Kaastrup
  -- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:33 port forwarding with one interface to trace traffic? Piers Finlayson

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=400E9EB3.4070309@triad.de \
    --to=rasca-ml@triad.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 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.