anchao opened a new pull request, #7004:
URL: https://github.com/apache/incubator-nuttx/pull/7004

   ## Summary
   
   net/procfs: add tcp profs support (IPv4 only)
   
   nuttx style:
   
   ```
   server> cat /proc/net/tcp
   TCP sl         local_address          remote_address st flg tmr uack rt    
rxq
     1:          0.0.0.0:  4214    192.168.31.22:  5001 04  61  12    0  0   
1024
     2:          0.0.0.0:  4213    192.168.31.22:  5001 04  61  12    0  0   
1024
     3:          0.0.0.0:  4215    192.168.31.22:  5001 04  61  12    0  0   
1024
     4:          0.0.0.0:  4216    192.168.31.22:  5001 04  61  12    0  0   
1024
     5:          0.0.0.0:  4217    192.168.31.22:  5001 04  61  12    0  0    
980
   
   server> ifconfig
   TCP sl         local_address          remote_address st flg tmr uack rt    
rxq
     1:          0.0.0.0:  4214    192.168.31.22:  5001 04  61  12    0  0   
1024
     2:          0.0.0.0:  4213    192.168.31.22:  5001 04  61  12    0  0   
1024
     3:          0.0.0.0:  4215    192.168.31.22:  5001 04  61  12    0  0   
1024
     4:          0.0.0.0:  4216    192.168.31.22:  5001 04  61  12    0  0   
1024
     5:          0.0.0.0:  4217    192.168.31.22:  5001 04  61  12    0  0    
980
   eth0    Link encap:Ethernet HWaddr 42:44:02:ee:4b:58 at RUNNING
           inet addr:192.168.31.209 DRaddr:192.168.31.1 Mask:255.255.255.0
   
           RX: Received Fragment Errors
               0000008e 00000000 00000000
               IPv4     ARP      Dropped
               0000003f 00000040 0000000f
           TX: Queued   Sent     Errors   Timeouts
               0000003f 0000003f 00000000 00000000
           Total Errors: 00000000
   ```
   
   linux kernel:
   https://www.kernel.org/doc/Documentation/networking/proc_net_tcp.txt
   
   
   ## Impact
   
   N/A
   
   ## Testing
   
   IPv4 tcp procfs


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to