Linux-Create AP that gets internet from client
I'd like to create access point that will take the internet from one of its clients. In other words, is there a way to create a bridge with a client?
I know how to create AP and bridge it with ethernet but I do not know how to do above.
Let's imagine the following scenario:
There is a phone with internet access(PH1). There is also another phone with no internet access(PH2). There is also a PC with no internet access. On this PC there is a WLAN AP set up. How to configure that AP in order to get internet from PH1 and share it to PH2 and other devices?
Speed performance does not matter at that point.
linux wireless-networking wifi-configuration hostapd
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
add a comment |
I'd like to create access point that will take the internet from one of its clients. In other words, is there a way to create a bridge with a client?
I know how to create AP and bridge it with ethernet but I do not know how to do above.
Let's imagine the following scenario:
There is a phone with internet access(PH1). There is also another phone with no internet access(PH2). There is also a PC with no internet access. On this PC there is a WLAN AP set up. How to configure that AP in order to get internet from PH1 and share it to PH2 and other devices?
Speed performance does not matter at that point.
linux wireless-networking wifi-configuration hostapd
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08
add a comment |
I'd like to create access point that will take the internet from one of its clients. In other words, is there a way to create a bridge with a client?
I know how to create AP and bridge it with ethernet but I do not know how to do above.
Let's imagine the following scenario:
There is a phone with internet access(PH1). There is also another phone with no internet access(PH2). There is also a PC with no internet access. On this PC there is a WLAN AP set up. How to configure that AP in order to get internet from PH1 and share it to PH2 and other devices?
Speed performance does not matter at that point.
linux wireless-networking wifi-configuration hostapd
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
I'd like to create access point that will take the internet from one of its clients. In other words, is there a way to create a bridge with a client?
I know how to create AP and bridge it with ethernet but I do not know how to do above.
Let's imagine the following scenario:
There is a phone with internet access(PH1). There is also another phone with no internet access(PH2). There is also a PC with no internet access. On this PC there is a WLAN AP set up. How to configure that AP in order to get internet from PH1 and share it to PH2 and other devices?
Speed performance does not matter at that point.
linux wireless-networking wifi-configuration hostapd
linux wireless-networking wifi-configuration hostapd
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
edited Jan 26 at 16:54
Michael Eagle
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
asked Jan 25 at 13:38
Michael EagleMichael Eagle
11
11
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08
add a comment |
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08
add a comment |
2 Answers
2
active
oldest
votes
An access point is already a bridge; the AP will always relay data between all its clients unless deliberately told not to. So as long as you don't accidentally enable "client isolation", it should just work by default.
(Bridging just connects things, it doesn't specifically define where the device "gets the internet from".)
However, you'll usually have poor performance, since Wi-Fi is half-duplex – the AP can't send and receive at the same time (even between different clients).
answered Jan 25 at 13:46
grawitygrawity
240k37508562
add a comment |
Beware that for security reasons, 802.11 APs are not allowed to accept packets from MAC addresses that have not authenticated and associated to the AP. That rule affects your client that is providing a path to the Internet.
If that client is a router (or NAT gateway), then your plan should work, because routers put their own source MAC address on packets they forward. But if you were planning on having that client be a simple bridge between wireless and wired Ethernet, then it won't work, because bridges don't change the source MAC address of packets they forward. So the AP will see those packets as coming from MAC addresses that have not authenticated or associated to the AP, and it will reject those packets. If you want to have a device bridge packets into your AP, you need the device to either do proxy authentication/association on behalf of all MAC addresses it sees, or you need to set up the AP and client as WDS nodes (some devices support acting as a WDS node at the same time as being an AP or client).
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
},
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%2fsuperuser.com%2fquestions%2f1398367%2flinux-create-ap-that-gets-internet-from-client%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
An access point is already a bridge; the AP will always relay data between all its clients unless deliberately told not to. So as long as you don't accidentally enable "client isolation", it should just work by default.
(Bridging just connects things, it doesn't specifically define where the device "gets the internet from".)
However, you'll usually have poor performance, since Wi-Fi is half-duplex – the AP can't send and receive at the same time (even between different clients).
answered Jan 25 at 13:46
grawitygrawity
240k37508562
add a comment |
An access point is already a bridge; the AP will always relay data between all its clients unless deliberately told not to. So as long as you don't accidentally enable "client isolation", it should just work by default.
(Bridging just connects things, it doesn't specifically define where the device "gets the internet from".)
However, you'll usually have poor performance, since Wi-Fi is half-duplex – the AP can't send and receive at the same time (even between different clients).
answered Jan 25 at 13:46
grawitygrawity
240k37508562
add a comment |
An access point is already a bridge; the AP will always relay data between all its clients unless deliberately told not to. So as long as you don't accidentally enable "client isolation", it should just work by default.
(Bridging just connects things, it doesn't specifically define where the device "gets the internet from".)
However, you'll usually have poor performance, since Wi-Fi is half-duplex – the AP can't send and receive at the same time (even between different clients).
answered Jan 25 at 13:46
grawitygrawity
240k37508562
An access point is already a bridge; the AP will always relay data between all its clients unless deliberately told not to. So as long as you don't accidentally enable "client isolation", it should just work by default.
(Bridging just connects things, it doesn't specifically define where the device "gets the internet from".)
However, you'll usually have poor performance, since Wi-Fi is half-duplex – the AP can't send and receive at the same time (even between different clients).
answered Jan 25 at 13:46
grawitygrawity
240k37508562
answered Jan 25 at 13:46
grawitygrawity
240k37508562
answered Jan 25 at 13:46
grawitygrawity
240k37508562
answered Jan 25 at 13:46
grawitygrawity
240k37508562
240k37508562
add a comment |
add a comment |
Beware that for security reasons, 802.11 APs are not allowed to accept packets from MAC addresses that have not authenticated and associated to the AP. That rule affects your client that is providing a path to the Internet.
If that client is a router (or NAT gateway), then your plan should work, because routers put their own source MAC address on packets they forward. But if you were planning on having that client be a simple bridge between wireless and wired Ethernet, then it won't work, because bridges don't change the source MAC address of packets they forward. So the AP will see those packets as coming from MAC addresses that have not authenticated or associated to the AP, and it will reject those packets. If you want to have a device bridge packets into your AP, you need the device to either do proxy authentication/association on behalf of all MAC addresses it sees, or you need to set up the AP and client as WDS nodes (some devices support acting as a WDS node at the same time as being an AP or client).
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
add a comment |
Beware that for security reasons, 802.11 APs are not allowed to accept packets from MAC addresses that have not authenticated and associated to the AP. That rule affects your client that is providing a path to the Internet.
If that client is a router (or NAT gateway), then your plan should work, because routers put their own source MAC address on packets they forward. But if you were planning on having that client be a simple bridge between wireless and wired Ethernet, then it won't work, because bridges don't change the source MAC address of packets they forward. So the AP will see those packets as coming from MAC addresses that have not authenticated or associated to the AP, and it will reject those packets. If you want to have a device bridge packets into your AP, you need the device to either do proxy authentication/association on behalf of all MAC addresses it sees, or you need to set up the AP and client as WDS nodes (some devices support acting as a WDS node at the same time as being an AP or client).
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
add a comment |
Beware that for security reasons, 802.11 APs are not allowed to accept packets from MAC addresses that have not authenticated and associated to the AP. That rule affects your client that is providing a path to the Internet.
If that client is a router (or NAT gateway), then your plan should work, because routers put their own source MAC address on packets they forward. But if you were planning on having that client be a simple bridge between wireless and wired Ethernet, then it won't work, because bridges don't change the source MAC address of packets they forward. So the AP will see those packets as coming from MAC addresses that have not authenticated or associated to the AP, and it will reject those packets. If you want to have a device bridge packets into your AP, you need the device to either do proxy authentication/association on behalf of all MAC addresses it sees, or you need to set up the AP and client as WDS nodes (some devices support acting as a WDS node at the same time as being an AP or client).
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
Beware that for security reasons, 802.11 APs are not allowed to accept packets from MAC addresses that have not authenticated and associated to the AP. That rule affects your client that is providing a path to the Internet.
If that client is a router (or NAT gateway), then your plan should work, because routers put their own source MAC address on packets they forward. But if you were planning on having that client be a simple bridge between wireless and wired Ethernet, then it won't work, because bridges don't change the source MAC address of packets they forward. So the AP will see those packets as coming from MAC addresses that have not authenticated or associated to the AP, and it will reject those packets. If you want to have a device bridge packets into your AP, you need the device to either do proxy authentication/association on behalf of all MAC addresses it sees, or you need to set up the AP and client as WDS nodes (some devices support acting as a WDS node at the same time as being an AP or client).
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
answered Jan 25 at 16:47
SpiffSpiff
77.9k10119163
77.9k10119163
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1398367%2flinux-create-ap-that-gets-internet-from-client%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
Welcome on SuperUser...Try to be more specific. Have you a laptop, a desktop, how many network interfaces in the client etc etc... Remember that you may edit your post to add such information.
– Hastur
Jan 25 at 15:08