-
Notifications
You must be signed in to change notification settings - Fork 1
/
NOTES
25 lines (18 loc) · 2.23 KB
/
NOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
= NOTES on Implementing Unicast (UDP) to multicast (UDP) =
Date: 2014-01-29
'''Purpose:''' In testing an application that involved Google glass it seem prudent to implement a simple middle server that could accept UDP packets and repurpose them for multicast. It should be noted that this (type of application) is implemented in many, many Internet routers, so this implementation is solely for our application. Meaning, this is a proof of concept - and NOT intended for commercial use.
''Before starting here are a few important notes.''
== On Multicast ==
# It should be noted that multicast was originally intended as a way to send multimedia over the Internet and private networks. Multimedia has the implied meaning of ''continous audio and video streams''.
:SEE: http://en.wikipedia.org/wiki/IP_multicast
# Multicast network traffic on an IP network is determined by the destination IP address, not the PORT. The port is generally insignificant.
:SEE: http://www.rfc-editor.org/rfc/rfc5771.txt (current standard)
:SEE: http://www.rfc-editor.org/rfc/rfc988.txt (original proposal)
# One important IP address is 224.0.0.1 It is designated as the IP for "All Systems on this Subnet". Meaning, that all devices on a local area network (or subnet for larger network) should listen to traffic with the destination address of 224.0.0.1
:SEE: http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml
== On Unicasting ==
''UDP datagrams'' and unicasting are synonymous for this purpose.
== On Special Network IP Numbers ==
# You can always get your IP on an a Unix system by issuing at the command-line: ''ifconfig''
# The network address ''127.0.0.1'' is reservered for the "localhost" - or your machine. That is, this IP number, often refered to as the "loopback", is intended for the machine to send message to itself via an internal socket. It is often used for testing, but can also be used for internal messaging. However, it is often consider "too heavy" for internal message, and often gives ways to other methods (such as shared memory).
# The network address that ends with 255, such as 10.0.0.255, is defined as the "broadcast address". As such, if at the command line you type ''ping 10.0.0.255'', every machine that is capable will respond.