Hello,
I have study the code in ip_masq.c, and
I found that icmp packet use
source address, destination address, source port and
destination port to hash into masquerade table.
Do icmp packets have port information?
I have print the port information with printk,
but I can't find out the answer to this question.
Could you give me a hint? Thanks a lot.
Cheers,
Tom
Hi,
On Tue, Apr 17, 2001 at 10:28:53PM +0800, gis88530 wrote:
>
> Do icmp packets have port information?
ICMP packets quote part of the original packet that triggered the ICMP
message. From this quoted part, information can be extracted about the
connection the ICMP packet belongs to.
Andreas
--
I *____knew* I had some reason for not logging you off... If I could just
remember what it was.
Thanks for your answer, and I still have some questions.
(private)---->(masquerade)---->(public)
If I ping public host from private host using this command:
ping 140.113.1.1
What trigger ICMP message? The "ping" binary program?
AND
How masquerade gateway know the original packet port information?
Because I think original packets are in private hosts, masquerade
gateway can't get the original packet.
If I am wrong, please feel free to advice me.
Thanks in advance.
Cheers,
Tom
----- Original Message -----
From: "Andreas Ferber" <[email protected]>
To: "gis88530" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, April 17, 2001 10:39 PM
Subject: Re: icmp and port
> Hi,
>
> On Tue, Apr 17, 2001 at 10:28:53PM +0800, gis88530 wrote:
> >
> > Do icmp packets have port information?
>
> ICMP packets quote part of the original packet that triggered the ICMP
> message. From this quoted part, information can be extracted about the
> connection the ICMP packet belongs to.
>
> Andreas
> --
> I *____knew* I had some reason for not logging you off... If I
could just
> remember what it was.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>