Question on ACLs and TCP/UDP ports posted 08/13/2006
- Subject: Question on ACLs and TCP/UDP ports
- From: sabrina pittarel <sabri_esame@xxxxxxxxx>
- Date: Sun, 13 Aug 2006 15:20:30 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4/gdAyTJ7JKSdg8ZZNscx3KQuVzxYPWJ6m39pLouMEzkbZWw9sEMijF5fiGz319ovW1OzGcMtHTRrfb0+5Tg3XGn9GT6+N1SKzNKF8EmL1deUlQrcU7YHgiYnECe1txERTyY+4ePhMS18M/6WmDC3eX5S5gEiM0a986ypzWl844= ;
when I'm told that an application send traffic using
UDP port X, how should I interpret that?
As a destination or as a source port?
Some time the application runs on a client, sometime
on a server.
My first instict would be to use that information as a
destination port for traffic generated by the client
and as a source port for traffic generated by the
server...but I'm not sure that's correct. Looking at
many of the solutions in the IEWB it seems like it is
always used as destination port.
Is there anything in the wording I should pay
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around