From: Patrick McHardy <kaber@trash.net>
To: Guido Trentalancia <guido@trentalancia.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Port forwarding with iptables on tunnel interface
Date: Fri, 12 Feb 2010 06:29:26 +0100 [thread overview]
Message-ID: <4B74E736.2020307@trash.net> (raw)
In-Reply-To: <1265916014.2985.72.camel@tesla.lan>
Guido Trentalancia wrote:
> Hello Patrick,
>
> thanks very much for your message !
>
> By the way, some IP addresses in the original message are wrong (read
> 192.168.3.69 instead of 192.168.1.65), but that's just a typo.
>
> Here is the log produced by iptables on 192.168.3.64:
>
> Feb 11 20:09:58 gyokuro kernel: ipencap (in): IN=eth0 OUT=
> MAC=macaddressofreceiverandsender SRC=senderipaddress DST=192.168.3.64
> LEN=76 TOS=0x00 PREC=0x00 TTL=41 ID=26562 PROTO=4
> Feb 11 20:10:01 gyokuro kernel: ipencap (in): IN=eth0 OUT=
> MAC=macaddressofreceiverandsender SRC=senderipaddress DST=192.168.3.64
> LEN=76 TOS=0x00 PREC=0x00 TTL=41 ID=28099 PROTO=4
> Feb 11 20:10:07 gyokuro kernel: ipencap (in): IN=eth0 OUT=
> MAC=macaddressofreceiverandsender SRC=senderipaddress DST=192.168.3.64
> LEN=76 TOS=0x00 PREC=0x00 TTL=41 ID=28322 PROTO=4
I don't see any decapsulated packets.
next prev parent reply other threads:[~2010-02-12 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 18:14 Port forwarding with iptables on tunnel interface Guido Trentalancia
2010-02-11 18:57 ` Patrick McHardy
2010-02-11 19:20 ` Guido Trentalancia
2010-02-12 5:29 ` Patrick McHardy [this message]
2010-02-12 13:28 ` Guido Trentalancia
2010-02-12 14:41 ` Patrick McHardy
2010-02-12 15:21 ` Guido Trentalancia
2010-02-12 17:30 ` Guido Trentalancia
2010-02-12 19:01 ` Mike Wright
2010-02-12 19:23 ` Guido Trentalancia
2010-02-12 19:56 ` Mike Wright
2010-02-12 22:27 ` Guido Trentalancia
2010-02-11 20:05 ` Guido Trentalancia
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=4B74E736.2020307@trash.net \
--to=kaber@trash.net \
--cc=guido@trentalancia.com \
--cc=netfilter@vger.kernel.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.