incubator-nuttx

History

Gregory Nutt b493dde4cf TCP networking: In the TCP connection operation, it was trying to setup the network monitor BEFORE the socket was successfully connected. This, of course, has ALWAYS failed because the socket is not yet connected and the TCP state is not yet correct for a connected socket. However, because of other changes net_startmonitor(0 no returns a failure condition that causes worse problems when trying to connect. The fix is to move the logic that starts the network monitor to AFTER the socket has been successfully connected.		2015-05-31 11:35:28 -06:00
..
arp	Networking: Get rid of g_ipv4_allzeroaddr and g_ipv4_alloneaddr. It is more efficient and more intuitive to use INADDR_ANY and INADDR_BROADCAST	2015-05-29 15:16:11 -06:00
devif	Costmetic changes to networking logic	2015-05-31 10:29:53 -06:00
icmp	Networking: Get rid of g_ipv4_allzeroaddr and g_ipv4_alloneaddr. It is more efficient and more intuitive to use INADDR_ANY and INADDR_BROADCAST	2015-05-29 15:16:11 -06:00
icmpv6	Networking: Modify event list handling: Now there are two event lists each device structure: (1) One is for ARP and ICMP data related evetns, the other is for device related events. Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list. Thus each socket type can received both custom data-related events as well as common device related events.	2015-05-28 12:01:38 -06:00
igmp	Networking: Clean up network status collection and presentation for IPv6	2015-01-24 08:26:12 -06:00
iob	IOB Configuration: Default number of IOB changes must be more than zero is UDP read-ahead is enabled.	2015-02-10 06:25:55 -06:00
local	Local sockets: Local stream sockets had problem of double releasing pipes (both server and client attempt release), which causes wrong pipe pair being closed in multi-client case. Solve by adding per connection instance ID to pipe names. From Jussi Kivilinna (2015-05-12).	2015-05-12 07:47:32 -06:00
neighbor	Fix typo introduced by commit a00f14a60a8ec54fbcf63e44d00f7101ec7cb5a3	2015-05-08 14:19:18 -06:00
netdev	TCP networking: In the TCP connection operation, it was trying to setup the network monitor BEFORE the socket was successfully connected. This, of course, has ALWAYS failed because the socket is not yet connected and the TCP state is not yet correct for a connected socket. However, because of other changes net_startmonitor(0 no returns a failure condition that causes worse problems when trying to connect. The fix is to move the logic that starts the network monitor to AFTER the socket has been successfully connected.	2015-05-31 11:35:28 -06:00
pkt	Raw sockets: Correct some compile issues; better modularized device-related logic	2015-05-29 08:47:21 -06:00
route	Networking: Get rid of g_ipv4_allzeroaddr and g_ipv4_alloneaddr. It is more efficient and more intuitive to use INADDR_ANY and INADDR_BROADCAST	2015-05-29 15:16:11 -06:00
socket	TCP networking: In the TCP connection operation, it was trying to setup the network monitor BEFORE the socket was successfully connected. This, of course, has ALWAYS failed because the socket is not yet connected and the TCP state is not yet correct for a connected socket. However, because of other changes net_startmonitor(0 no returns a failure condition that causes worse problems when trying to connect. The fix is to move the logic that starts the network monitor to AFTER the socket has been successfully connected.	2015-05-31 11:35:28 -06:00
tcp	Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert.	2015-05-31 08:34:03 -06:00
udp	TCP networking: Add support for network driver events	2015-05-30 09:12:27 -06:00
utils	Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert.	2015-05-31 08:34:03 -06:00
.gitignore	.dSYM only needs to be in the same .gitignore files as .exe	2013-05-30 15:02:04 -06:00
Kconfig	Add TUN device. From Max Neklyudov	2015-03-11 06:52:56 -06:00
Makefile	Add basic build structure for Unix domain sockets	2015-01-24 14:03:32 -06:00
README.txt	Add basic build structure for Unix domain sockets	2015-01-24 14:03:32 -06:00
net_initialize.c	Networking: The network device list was protected by a re-entrant semaphore. With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state. Of course,those drivers are unable to take the semaphore and will assert.	2015-05-31 08:34:03 -06:00

README.txt

README
======

Directory Structure
===================

  nuttx/
   |
   `- net/
       |
       +- arp      - Address resolution protocol (IPv4)
       +- devif    - Stack/device interface layer
       +- icmp     - Internet Control Message Protocol (IPv4)
       +- icmpv6   - Internet Control Message Protocol (IPv6)
       +- iob      - I/O buffering logic
       +- local    - Unix domain (local) sockets
       +- neighbor - Neighbor Discovery Protocol (IPv6)
       +- netdev   - Socket network device interface
       +- pkt      - "Raw" packet socket support
       +- socket   - BSD socket interface
       +- route    - Routing table support
       +- tcp      - Transmission Control Protocol
       +- udp      - User Datagram Protocol
       `- utils    - Miscellaneous utility functions


    +----------------------------------------------------------------+
    |                     Application layer                          |
    +----------------------------------------------------------------+
    +----------------------------------------------------------------+
    |                   Socket layer (socket/)                       |
    +----------------------------------------------------------------+
    +------------++--------------------------------------------------+
    |  Network   || Protocol stacks (arp, ipv6, icmp, pkt, tcp, udp) |
    |   Device   |+--------------------------------------------------+
    | Interface  |+------------------------------------++------------+
    | (netdev/)  ||  Network Device Interface (devif/) || Utilities  |
    +------------++------------------------------------++------------+
    +----------------------------------------------------------------+
    |                    Network Device Drivers                      |
    +----------------------------------------------------------------+