From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: Mart Frauenlob <mart.frauenlob@chello.at>
Cc: netfilter@vger.kernel.org
Subject: Re: icmp forward
Date: Fri, 30 Jan 2009 12:36:06 +0100 [thread overview]
Message-ID: <4982E626.80800@cetrtapot.si> (raw)
In-Reply-To: <4982C662.7030807@chello.at>
Mart Frauenlob wrote:
> Hinko Kocevar wrote:
>> Our customers want to be able to ping the mobile device behind the
>> linux firewall
>> and IMHO it is not possible for ICMP packets to be forwarded since it
>> is a protocol
>> by itself (not a TCP/UDP style service).
>>
>>
>
> *clearing my throat*
> TCP and UDP are protocols no services! many services use TCP/UDP protocol!
> TCP and UDP are very different, UDP is a connectionless protocol, in
> opposite to TCP.
>
> So ICMP is more like UDP, than like TCP.
Right.
>> Is it possible to 'port forward' ICMP requests?
>>
>
> First try, then cry ;-p
>
> If u have an unused ip addr. on your gw, you could use that one to nat
> the icmp, so your gateway still is reachable with icmp.
>
Hmm that seems like a viable solution - totally forgot about the network
interface aliasing 8).
Thanks!
--
Hinko Koèevar, OSS developer
ÈETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel ++386 (0) 4 280 66 03
e-mail hinko.kocevar@cetrtapot.si
http www.cetrtapot.si
prev parent reply other threads:[~2009-01-30 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 8:18 icmp forward Hinko Kocevar
2009-01-30 8:33 ` Michele Petrazzo - Unipex srl
2009-01-30 8:53 ` Payam Chychi
2009-01-30 9:19 ` Hinko Kocevar
2009-01-30 8:49 ` Christoph Paasch
2009-01-30 9:12 ` Hinko Kocevar
2009-01-30 10:53 ` Pascal Hambourg
2009-01-30 11:24 ` Hinko Kocevar
2009-01-30 11:35 ` Hinko Kocevar
2009-01-30 11:42 ` Pascal Hambourg
2009-01-30 11:36 ` Mart Frauenlob
2009-01-30 9:20 ` Mart Frauenlob
2009-01-30 11:36 ` Hinko Kocevar [this message]
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=4982E626.80800@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--cc=mart.frauenlob@chello.at \
--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.