Ethereal-users: SV: Re: [Ethereal-users] No source and destination port for ICMP protocols??

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: JS <fedevaps@xxxxxxxx>
Date: Tue, 27 Sep 2005 23:37:50 +0200 (CEST)
Ok would another explanations like ICMP protocols are
not in "contact" with any processes on a remote system
also apply? I guess it only TCP and UDP that
communicates with the processes and therefore ICMP and
IP does not need to have source and destination ports.


--- Bjorn Townsend <eriktown@xxxxxxxxx> skrev:

> For the same reason that the IP protocol does not
> have a source and
> destination port -- it doesn't apply. Only the TCP
> and UDP protocols
> have source and destination ports, and they're not
> even in the same
> layer of the OSI model (layer 3 vs. layer 4).
> 
> This is like asking "Why doesn't HTTP have a source
> and destination
> port?" -- meaningless.
> 
> On 9/27/05, JS <fedevaps@xxxxxxxx> wrote:
> > Why is it that an ICMP protocol does not have any
> > source and destination port?
> >
> >
> > _______________________________________________
> > Ethereal-users mailing list
> > Ethereal-users@xxxxxxxxxxxx
> >
>
http://www.ethereal.com/mailman/listinfo/ethereal-users
> >
> 
> 
> --
> Bjorn Townsend | eriktown@xxxxxxxxx
> 
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
>
http://www.ethereal.com/mailman/listinfo/ethereal-users
>