Conversion of WLAN traffic to the outside world
up vote
1
down vote
favorite
Preamble: I don't have that much experience with lower level computer networking yet.
I am currently trying to wrap my head around the workings of the WLAN protocol. While I am starting to get the hang of how the communication between AP and stations works with the different management packets and the protocol for data fragments I am currently still not really seeing how the data is passed to the outside world.
From my understanding if a station S wants to send data to the host 1.2.3.4 (which is neither the AP nor any other station in the network) it will create some IEEE 802.11 data packets (lets assume that data needs to be fragmented into 2 data packets) and encrypt them and send them to the AP. The AP will identify the station, get its current key and decrypt it.
But what next? For example, what will my router send over my fiber cable? And how does it work with fragmentation? As far as I understand there are some rules for fragmentation in WLAN, but what if the connection between my router and its next hop could transfer much more/less? Will it do some buffering or splitting in the router?
I think all of the questions above boil down to the question in my title: What does an access point do when it receives a packet that is addressed for the outside world?
wireless ieee-802.11 access-point
add a comment |
up vote
1
down vote
favorite
Preamble: I don't have that much experience with lower level computer networking yet.
I am currently trying to wrap my head around the workings of the WLAN protocol. While I am starting to get the hang of how the communication between AP and stations works with the different management packets and the protocol for data fragments I am currently still not really seeing how the data is passed to the outside world.
From my understanding if a station S wants to send data to the host 1.2.3.4 (which is neither the AP nor any other station in the network) it will create some IEEE 802.11 data packets (lets assume that data needs to be fragmented into 2 data packets) and encrypt them and send them to the AP. The AP will identify the station, get its current key and decrypt it.
But what next? For example, what will my router send over my fiber cable? And how does it work with fragmentation? As far as I understand there are some rules for fragmentation in WLAN, but what if the connection between my router and its next hop could transfer much more/less? Will it do some buffering or splitting in the router?
I think all of the questions above boil down to the question in my title: What does an access point do when it receives a packet that is addressed for the outside world?
wireless ieee-802.11 access-point
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Preamble: I don't have that much experience with lower level computer networking yet.
I am currently trying to wrap my head around the workings of the WLAN protocol. While I am starting to get the hang of how the communication between AP and stations works with the different management packets and the protocol for data fragments I am currently still not really seeing how the data is passed to the outside world.
From my understanding if a station S wants to send data to the host 1.2.3.4 (which is neither the AP nor any other station in the network) it will create some IEEE 802.11 data packets (lets assume that data needs to be fragmented into 2 data packets) and encrypt them and send them to the AP. The AP will identify the station, get its current key and decrypt it.
But what next? For example, what will my router send over my fiber cable? And how does it work with fragmentation? As far as I understand there are some rules for fragmentation in WLAN, but what if the connection between my router and its next hop could transfer much more/less? Will it do some buffering or splitting in the router?
I think all of the questions above boil down to the question in my title: What does an access point do when it receives a packet that is addressed for the outside world?
wireless ieee-802.11 access-point
Preamble: I don't have that much experience with lower level computer networking yet.
I am currently trying to wrap my head around the workings of the WLAN protocol. While I am starting to get the hang of how the communication between AP and stations works with the different management packets and the protocol for data fragments I am currently still not really seeing how the data is passed to the outside world.
From my understanding if a station S wants to send data to the host 1.2.3.4 (which is neither the AP nor any other station in the network) it will create some IEEE 802.11 data packets (lets assume that data needs to be fragmented into 2 data packets) and encrypt them and send them to the AP. The AP will identify the station, get its current key and decrypt it.
But what next? For example, what will my router send over my fiber cable? And how does it work with fragmentation? As far as I understand there are some rules for fragmentation in WLAN, but what if the connection between my router and its next hop could transfer much more/less? Will it do some buffering or splitting in the router?
I think all of the questions above boil down to the question in my title: What does an access point do when it receives a packet that is addressed for the outside world?
wireless ieee-802.11 access-point
wireless ieee-802.11 access-point
asked Dec 9 at 9:06
Cromon
1083
1083
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
You need to take a look at the various layers involved. WLAN only covers L1 and L2 of the OSI stack (the physical layer and the data link layer) and doesn't care at all about L3 (the network layer, most commonly IPv4 or IPv6).
Don't think about conversion which is (somewhat) an analog concept. A packet-based network transports payload in packets between nodes using various mechanisms.
The network layer's job is to provide end-to-end connectivity between any two nodes on a global scale. The data link layer provides connectivity between any two nodes in a local network segment. The physical layer finally provides actual data transport between two nodes connect by a common medium - a cable, fiber or a WiFi channel.
An IP packet (L3) sent to 1.2.3.4 from a wireless node is encapsulated in an IEEE 802 frame (L2) which is then sent over the air using an IEEE 802.11 physical layer (L1). In the WAP, the frame is received and forwarded to the router over wire using an Ethernet (IEEE 802.3) physical layer. The router extracts the IP packet and forwards it depending on your WAN protocol (may be Ethernet, xDSL, DOCSIS or anything else).
The WAP is basically a network bridge, forwarding between the wireless nodes and the wired nodes based on their MAC addresses (L2). WiFi encryption is an option with the 802.11 L2, it is added and removed on the WAP (and on the wireless clients, of course).
IPv4 fragmentation happens on the host or on the router. If the WAN MTU is smaller than the LAN MTU, your router needs to fragment the IPv4 packet or you need to reduce the LAN MTU.
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "496"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55313%2fconversion-of-wlan-traffic-to-the-outside-world%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
You need to take a look at the various layers involved. WLAN only covers L1 and L2 of the OSI stack (the physical layer and the data link layer) and doesn't care at all about L3 (the network layer, most commonly IPv4 or IPv6).
Don't think about conversion which is (somewhat) an analog concept. A packet-based network transports payload in packets between nodes using various mechanisms.
The network layer's job is to provide end-to-end connectivity between any two nodes on a global scale. The data link layer provides connectivity between any two nodes in a local network segment. The physical layer finally provides actual data transport between two nodes connect by a common medium - a cable, fiber or a WiFi channel.
An IP packet (L3) sent to 1.2.3.4 from a wireless node is encapsulated in an IEEE 802 frame (L2) which is then sent over the air using an IEEE 802.11 physical layer (L1). In the WAP, the frame is received and forwarded to the router over wire using an Ethernet (IEEE 802.3) physical layer. The router extracts the IP packet and forwards it depending on your WAN protocol (may be Ethernet, xDSL, DOCSIS or anything else).
The WAP is basically a network bridge, forwarding between the wireless nodes and the wired nodes based on their MAC addresses (L2). WiFi encryption is an option with the 802.11 L2, it is added and removed on the WAP (and on the wireless clients, of course).
IPv4 fragmentation happens on the host or on the router. If the WAN MTU is smaller than the LAN MTU, your router needs to fragment the IPv4 packet or you need to reduce the LAN MTU.
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
add a comment |
up vote
2
down vote
accepted
You need to take a look at the various layers involved. WLAN only covers L1 and L2 of the OSI stack (the physical layer and the data link layer) and doesn't care at all about L3 (the network layer, most commonly IPv4 or IPv6).
Don't think about conversion which is (somewhat) an analog concept. A packet-based network transports payload in packets between nodes using various mechanisms.
The network layer's job is to provide end-to-end connectivity between any two nodes on a global scale. The data link layer provides connectivity between any two nodes in a local network segment. The physical layer finally provides actual data transport between two nodes connect by a common medium - a cable, fiber or a WiFi channel.
An IP packet (L3) sent to 1.2.3.4 from a wireless node is encapsulated in an IEEE 802 frame (L2) which is then sent over the air using an IEEE 802.11 physical layer (L1). In the WAP, the frame is received and forwarded to the router over wire using an Ethernet (IEEE 802.3) physical layer. The router extracts the IP packet and forwards it depending on your WAN protocol (may be Ethernet, xDSL, DOCSIS or anything else).
The WAP is basically a network bridge, forwarding between the wireless nodes and the wired nodes based on their MAC addresses (L2). WiFi encryption is an option with the 802.11 L2, it is added and removed on the WAP (and on the wireless clients, of course).
IPv4 fragmentation happens on the host or on the router. If the WAN MTU is smaller than the LAN MTU, your router needs to fragment the IPv4 packet or you need to reduce the LAN MTU.
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
You need to take a look at the various layers involved. WLAN only covers L1 and L2 of the OSI stack (the physical layer and the data link layer) and doesn't care at all about L3 (the network layer, most commonly IPv4 or IPv6).
Don't think about conversion which is (somewhat) an analog concept. A packet-based network transports payload in packets between nodes using various mechanisms.
The network layer's job is to provide end-to-end connectivity between any two nodes on a global scale. The data link layer provides connectivity between any two nodes in a local network segment. The physical layer finally provides actual data transport between two nodes connect by a common medium - a cable, fiber or a WiFi channel.
An IP packet (L3) sent to 1.2.3.4 from a wireless node is encapsulated in an IEEE 802 frame (L2) which is then sent over the air using an IEEE 802.11 physical layer (L1). In the WAP, the frame is received and forwarded to the router over wire using an Ethernet (IEEE 802.3) physical layer. The router extracts the IP packet and forwards it depending on your WAN protocol (may be Ethernet, xDSL, DOCSIS or anything else).
The WAP is basically a network bridge, forwarding between the wireless nodes and the wired nodes based on their MAC addresses (L2). WiFi encryption is an option with the 802.11 L2, it is added and removed on the WAP (and on the wireless clients, of course).
IPv4 fragmentation happens on the host or on the router. If the WAN MTU is smaller than the LAN MTU, your router needs to fragment the IPv4 packet or you need to reduce the LAN MTU.
You need to take a look at the various layers involved. WLAN only covers L1 and L2 of the OSI stack (the physical layer and the data link layer) and doesn't care at all about L3 (the network layer, most commonly IPv4 or IPv6).
Don't think about conversion which is (somewhat) an analog concept. A packet-based network transports payload in packets between nodes using various mechanisms.
The network layer's job is to provide end-to-end connectivity between any two nodes on a global scale. The data link layer provides connectivity between any two nodes in a local network segment. The physical layer finally provides actual data transport between two nodes connect by a common medium - a cable, fiber or a WiFi channel.
An IP packet (L3) sent to 1.2.3.4 from a wireless node is encapsulated in an IEEE 802 frame (L2) which is then sent over the air using an IEEE 802.11 physical layer (L1). In the WAP, the frame is received and forwarded to the router over wire using an Ethernet (IEEE 802.3) physical layer. The router extracts the IP packet and forwards it depending on your WAN protocol (may be Ethernet, xDSL, DOCSIS or anything else).
The WAP is basically a network bridge, forwarding between the wireless nodes and the wired nodes based on their MAC addresses (L2). WiFi encryption is an option with the 802.11 L2, it is added and removed on the WAP (and on the wireless clients, of course).
IPv4 fragmentation happens on the host or on the router. If the WAN MTU is smaller than the LAN MTU, your router needs to fragment the IPv4 packet or you need to reduce the LAN MTU.
answered Dec 9 at 9:50
Zac67
25.1k21252
25.1k21252
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
add a comment |
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
That corrected a fundamental misunderstanding I had. I always assumed that the layers more or less stay fixed and not that it "goes up" again to extract the data of the upper layer, this also makes some other things much clearer, thank you!
– Cromon
Dec 9 at 11:20
add a comment |
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f55313%2fconversion-of-wlan-traffic-to-the-outside-world%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown