The trick is they attempted to open a UDP port, not a TCP port. Can anyone else explaion this better?
In my opinion, that is not very strange.
UDP (User Datagram Protocol), is a member in the TCP/IP protocol suite (defined by Postel RCF 768).
UDP adds a mechanism that distinguishes among destinations within a given host, allowing multiple application programs executing on a given computer to send and receive datagrams independently. In multitasking systems (windows) a process is the ultimate destination for a message. But, because processes are created and destroyed dynamically, senders seldom know enough to identify a process on another machine. And we would like to be able to replace processes that receive that datagrams without informing the sender. Third, we need to identify destinations from functions they implement without knowing the process that implements the function.
Therefor, instead of thinking of a process as the ultimate destination, we will imagine that each machine contains a set of abstract destinations points, called protocol ports.
The sender needs to know both the IP address of the destination machine and the protocol number of the destination within that machine.
UDP uses IP to transport messages between machines. IP carries the message, and UDP adds ability to distinguish among multiple destinations within a given host computer.
TCP adds even more functionality to the UDP, and in implementation, TCP is also substantially more complex.
UDP is used by many programs where reliable stream service isn't needed (which is implemented in TCP)
You asked about port 6970, well see for youself:
6970-7170 | udp | | Real Audio (inclusive) for incoming traffic only |
Main point is, don't worry!
Firewalls often gives false alerts.
