linux-nc-and-python-sockets — revision history

rev 5 | foxhop | 1347744223000 | JSON

	rev 4			rev 5
	55	>>> # when you are finished run s.close()		55	>>> # when you are finished run s.close()
	56			56
t	57		t	57	The constant socket.AF_INET creates a socket which allows us to connect to an ip
				>	/name and port. The constant socket.AF_UNIX creates a socket which allows us t
				>	o connect via files? socket.SOCK_STREAM is the type of socket (tcp/ip). socket
				>	.SOCK_DGRAM (data-gram)
	58			58
	59			59

rev 4 | foxhop | 1347743435000 | JSON

	rev 3			rev 4
	53	>>> # To learn more about sockets do:		53	>>> # To learn more about sockets do:
	54	>>> help( s )		54	>>> help( s )
t			t	55	>>> # when you are finished run s.close()
	55			56
	56			57

rev 3 | foxhop | 1347742593000 | JSON

	rev 2			rev 3
	26			26
	27	Like the man page suggests all text submitted on either terminal A or B will app		27	Like the man page suggests all text submitted on either terminal A or B will app
	>	ear on both terminals.		>	ear on both terminals.
t	28	Conventionally the server "listening" for connections is typically labeled the s	t	28	Conventionally the server "listening" for connections is typically labeled the s
	>	erver.		>	erver. In this case neither terminal is a server because if either closes, both
				>	close...
	29			29
	30			30

rev 2 | foxhop | 1347742562000 | JSON

	rev 1			rev 2
	11	Start listening (nc -l) for a connection on a port (31337).		11	Start listening (nc -l) for a connection on a port (31337).
	12			12
n	13	On terminal A	n	13	On terminal A
	14			14
	15	.. code-block:: bash		15	.. code-block:: bash
	19	Connect to (127.0.0.1) on a port (31337).		19	Connect to (127.0.0.1) on a port (31337).
	20			20
t	21	On terminal B	t	21	On terminal B
	22			22
	23	.. code-block:: bash		23	.. code-block:: bash

rev 1 | foxhop | 1347742503000 | JSON

+linux-nc-and-python-sockets
+==============================
+nc or netcat lets you create socket servers or connect to services via sockets.
+The nc man page is excellent.  This first thing I tried was creating a simple-ch
+at like program between two terminals.
+Simple nc chat application
+=================================
+Start listening (nc -l) for a connection on a port (31337).
+On terminal A
+.. code-block:: bash
+ nc -l 31337
+Connect to (127.0.0.1) on a port (31337).
+On terminal B
+.. code-block:: bash
+ nc 127.0.0.1 31337
+Like the man page suggests all text submitted on either terminal A or B will app
+ear on both terminals.
+Conventionally the server "listening" for connections is typically labeled the s
+erver.
+Use python to interact with nc
+===================================
+On terminal A
+.. code-block:: bash
+ nc -l 31337
+On terminal b
+.. code-block:: python
+ python
+ >>> import socket
+ >>> s = socket.socket( socket.AF_INET, socket.SOCK_STREAM )
+ >>> s.connect( ( 'localhost', 31337 ) )
+ >>> s.send( 'python says hello nc' )
+ >>> s.recv( 30 )
+ 'nc says hello python\n'
+ >>> # To learn more about sockets do:
+ >>> help( s )