+-----------+
| Satellite | 	
+-----------+	
     +		     	       Linux Box	
     +     +------------------------------------------------+
    AIR    |   						    |	
     	   |     Pent@NET card(a) 	  application(g)    |
     +	   |    +----------------+	 +-------------+    |	
     +--------->| Tuner + Fusion |       | 	       |    |		
    CABEL  |    | -------------- |       +-------------+    |
	   |    |      Data 	 | 		^           |
	   |    |    Demuxing(b) | 		+           |
	   |	|--------------- |		V           |
	   |    |  PID-filter(c) |	  TCP/IP stack(f)   |
	   |	+----------------+	 +-------------+    |	
           |    |  MAC-filter(d) |       |	       +    |	
	   |    +----------------+	 +-------------+    |
	   |            +			^  ^        |
 	   |		+			+  +        |
	   |		+-----------------------+  +        |
           |			  (e)		   +	    |
           |	  ethernet card(h)		   +	    |
    LAN    |	+-----------------+		   +	    |
      <-------->| 		  |<---------------+	    |
           |	+-----------------+			    |
           +------------------------------------------------+
		           < block diagram >


 Basic data process
======================
 
  These are generic data process.
  
  The basic data process is two ways. The one is unicast, the other is multicast.
  
  (1) Unicast 

    - Initiailly the driver receives all data from the satellite.
    - demuxing all data and get some informations from it.
    - compares the PID of it with the PID(tp.conf) used when trying to lock. if not match, discard the data.
    - compares the MAC-address of it with own MAC address. if not match, discard the data.
      (NOTE: use the decimal value as PID on text application) 
    - To check (e)step at the upper diagram, use 'tcpdump' utility or 'ifconfig' and so on.

	ex) shell> tcpdump -i pentanet0 : this shows all Rx/Tx packets at the pentanet0 interface. Please check whether packets across pentanet0 inteface exists or not. if exists, the driver works fine.

	ex) shell> tcpdump dst my-ip-adress : this shows all Rx/Tx packets at all network interfaces. Please check whether packets across pentanet0 inteface exists or not. if exists, the driver works fine.

	ex) shell> ifconfig pentanet0 : just check whether Rx packet count increases or not. if it increases, the driver'job is good. it must be normal operation.  	
	
	if you want more information about it, please refer each manual
          		
   - The operations after this depends on user's free action. 

 
  (2) Multicast 
    	 
    - Initially the driver receives all data from the satellite.
    - demuxing all data and get some informations from it.
    - compares the PID of it with the PID(tp.conf) used when trying to lock. if not match, discard the data.
      (NOTE: use the decimal value as PID on text application) 
    - compares the MAC-address of it with the addresses set inside the driver. if not match, discard the data.
    - if you want to check the MAC-addresses set inside the driver, use Pent@VALUE text application called 'pentanett'.
      That is, run 'pentanett -m' at the command line. You can get the multicast information.
      (NOTE:if you use ifconfig with a option allmulti or promisc,the drivercan receive all multicast packets or all packets. please refer ifconfig manual ) 
      (NOTE:the multicast IP address may be set to the driver at kernel-level when open stream on media-player )
       
    - if you want to check (e) at the upper diagram, use 'tcpdump' utility or 'ifconfig'.

	ex) shell> tcpdump -i pentanet0 : this shows all Rx/Tx packets at the pentanet0 interface. Please check whether packets across pentanet0 inteface exist or not. if exists, the driver works fine.

	ex) shell> tcpdump dst multicast-ip-adress : this shows a specific multicast packets at all network interfaces. Please check whether packets across pentanet0 inteface exist or not. if exists, the driver works fine.

	ex) shell> ifconfig pentanet0 : just check whether Rx packet count increases or not. 	

	ex) shell> tcpdump ether multicast : this show all multicast packetsat all network interfaces.

	if you want more information about it, please refer each manual
 	
   - The operations after this depends on user's free action. 
