Skip to content

Commit e52cb93

Browse files
author
Amanda Butler
authored
Fix headings in networking.md
Update heading sizes for proper rendering.
1 parent 0c3d54f commit e52cb93

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

docs/reference/technology/connectivity/networking.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
1-
### IP networking
1+
## IP networking
22

33
IP Networking in Mbed OS is layered in three clearly defined API levels. The diagram below shows the layers next to the closest matching [OSI model](https://en.wikipedia.org/wiki/OSI_model) layers.
44

55
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/ip-networking.png)<span>IP networking</span></span>
66

77
The following sections introduce the APIs and technologies implemented in each level.
88

9-
#### Socket API
9+
### Socket API
1010

1111
The Socket API is the common API among all IP connectivity methods. All network stacks in Mbed OS provide the same Socket API, making applications portable among different connectivity methods or even stacks.
1212

13-
In the OSI model, the Socket API relates to layer 4, the Transport layer. In Mbed OS, the Socket API supports both [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol) and [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) protocols.
13+
In the OSI model, the Socket API relates to layer 4, the Transport layer. In Mbed OS, the Socket API supports both TCP and UDP protocols.
1414

1515
Refer to [Socket API](network-socket.html) reference for usage instructions.
1616

17-
#### IP stacks
17+
### IP stacks
1818

1919
Mbed OS has three options to select for the IP stack. The connectivity modules provides two built-in IP stacks or an external IP stack.
2020

@@ -32,7 +32,7 @@ The following table summarizes different stacks, use cases and their limitations
3232
|Nanostack|IPv6, 6LoWPAN, Thread|Mesh networking, Border Router|Only IPv6|
3333
|External IP module|Depends on the module|(Save RAM/Flash)|Depends on the module. Usually poor match to Socket API|
3434

35-
##### Configuring the IP stack interface
35+
#### Configuring the IP stack interface
3636

3737
Depending on the Layer 3, Network layer, protocol used, there are different ways to configure the interface. It also depends on the stack used, which configurations are supported on each link layer.
3838

@@ -44,7 +44,7 @@ Depending on the Layer 3, Network layer, protocol used, there are different ways
4444
|Nanostack|Ethernet|IPv6|static or [RFC 4862](https://tools.ietf.org/html/rfc4862) IPv6 Stateless Address Autoconfiguration. No DHCPv6 support|
4545
|Nanostack|IEEE 802.15.4|6LoWPAN|Thread or 6LoWPAN-ND+RPL|
4646

47-
#### Network interfaces
47+
### Network interfaces
4848

4949
Network intefaces are the application level APIs where users choose the driver, connectivity method and IP stack. Each connectivity methods requires different configuration,so these APIs are not interchangeable. The application developer must choose one. Choosing the interface also automatically pulls in the network stack as a dependency.
5050

@@ -60,29 +60,29 @@ Mbed OS implements the following network interface APIs:
6060

6161
Refer to [Network Interface](network-interfaces.html) API reference for usage instructions.
6262

63-
#### Network driver
63+
### Network driver
6464

6565
The network driver is a generic term to describe different APIs for connecting networking device to the IP stack or Socket API. Below is a description of each driver API.
6666

67-
##### Ethernet driver
67+
#### Ethernet driver
6868

6969
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/emac.png)<span>Emac API</span></span>
7070

7171
Ethernet drivers are implemented using the stack-independent EMAC API. Because the Ethernet driver requires no configuration, it does not implement any controlling interface for the application.
7272

73-
##### Wi-Fi driver
73+
#### Wi-Fi driver
7474

7575
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/wifi.png)<span>Wi-Fi driver</span></span>
7676

7777
There are two types of Wi-Fi drivers in Mbed OS, depending on which protocol layer it implements. Wi-Fi drivers are either a special case of Ethernet driver or external IP stacks. Wi-Fi drivers require configuration from an application and, therefore, implement both the low level EMAC API or Network stack API and the high level controlling interface API called `WiFiInterface`.
7878

79-
##### Cellular modem driver
79+
#### Cellular modem driver
8080

8181
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/cellular.png)<span>Cellular driver</span></span>
8282

8383
Cellular drivers have the same two separate cases as Wi-Fi. If they use an external IP stack, the driver implements the Network stack API. If they use the internal IP stack, LwIP, then they implement the Serial PPP driver.
8484

85-
##### IEEE 802.15.4 RF driver
85+
#### IEEE 802.15.4 RF driver
8686

8787
<span class="images">![](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/rf-driver.png)<span>RF driver</span></span>
8888

0 commit comments

Comments
 (0)