From: Raido Kurel <raido@elin.ttu.ee>
To: netfilter@lists.netfilter.org
Subject: Re: dnat problem in transparent firewall
Date: Wed, 4 Aug 2004 15:05:00 +0300 [thread overview]
Message-ID: <200408041505.00078.raido@elin.ttu.ee> (raw)
In-Reply-To: <200408041230.03828.Antony@Soft-Solutions.co.uk>
> What do your LOGging rules say? Is it possible that you are trying to LOG
> packets addressed to aaa.aaa.aaa.12, and therefore the rules no longer see
> the packets once the address has been changed to aaa.aaa.aaa.13?
That's a good point. I checket it also over several times.
Thats why I also tested and wrote, that I see packets if I try to connect to
aaa.aaa.aaa.13
I added 2 logging rules for every logging point from a) to d).
For example exact logging rules for a) are :
iptables -t nat -A PREROUTING -s nnn.nnn.nnn.nnn -d aaa.aaa.aaa.12 -j LOG
--log-prefix " ipt nat pre "
iptables -t nat -A PREROUTING -s nnn.nnn.nnn.nnn -d aaa.aaa.aaa.13 -j LOG
--log-prefix " ipt nat pre "
where nnn.nnn.nnn.nnn is a computer from where I connect behind other ISP.
It should not be relevant, but the port I try to connect for testing right now
is ssh. I try to connect with telnet aaa.aaa.aaa.12 22.
both .12 and .13 have ssh servers up and running.
Raido
next prev parent reply other threads:[~2004-08-04 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 7:10 dnat problem in transparent firewall Raido Kurel
2004-08-04 8:45 ` Antony Stone
2004-08-04 11:14 ` Raido Kurel
2004-08-04 11:30 ` Antony Stone
2004-08-04 12:05 ` Raido Kurel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 11:36 Raido Kurel
2004-08-03 12:33 ` Antony Stone
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=200408041505.00078.raido@elin.ttu.ee \
--to=raido@elin.ttu.ee \
--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.