enabling Wifi direct (p2p) along with DHCP server












0















How can I enable WiFi p2p on raspberry pi zero w and have dhcp service running so that other devices that connect to it get assigned an IP address?



I am able to configure the dhcp service on the pi by following this link:



https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md



but the article asks for disabling the wpa_supplicant by adding nohook wpa_supplicant to the end of /etc/dhcpcd.conf while I am supposed to run wpa_supplicant in order to enable WiFi p2p



how can I do that?










share|improve this question













migrated from superuser.com Feb 10 at 9:04


This question came from our site for computer enthusiasts and power users.



















  • I think the default behavior for wifi-direct is via "APIPA" addresses.

    – Tim_Stewart
    Feb 10 at 1:31






  • 1





    I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

    – Spiff
    Feb 10 at 1:51











  • so does this mean it is doable or not?

    – Mohyddin
    Feb 10 at 10:34











  • It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

    – Ingo
    Feb 10 at 12:59











  • The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

    – Ingo
    Feb 10 at 13:02
















0















How can I enable WiFi p2p on raspberry pi zero w and have dhcp service running so that other devices that connect to it get assigned an IP address?



I am able to configure the dhcp service on the pi by following this link:



https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md



but the article asks for disabling the wpa_supplicant by adding nohook wpa_supplicant to the end of /etc/dhcpcd.conf while I am supposed to run wpa_supplicant in order to enable WiFi p2p



how can I do that?










share|improve this question













migrated from superuser.com Feb 10 at 9:04


This question came from our site for computer enthusiasts and power users.



















  • I think the default behavior for wifi-direct is via "APIPA" addresses.

    – Tim_Stewart
    Feb 10 at 1:31






  • 1





    I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

    – Spiff
    Feb 10 at 1:51











  • so does this mean it is doable or not?

    – Mohyddin
    Feb 10 at 10:34











  • It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

    – Ingo
    Feb 10 at 12:59











  • The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

    – Ingo
    Feb 10 at 13:02














0












0








0








How can I enable WiFi p2p on raspberry pi zero w and have dhcp service running so that other devices that connect to it get assigned an IP address?



I am able to configure the dhcp service on the pi by following this link:



https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md



but the article asks for disabling the wpa_supplicant by adding nohook wpa_supplicant to the end of /etc/dhcpcd.conf while I am supposed to run wpa_supplicant in order to enable WiFi p2p



how can I do that?










share|improve this question














How can I enable WiFi p2p on raspberry pi zero w and have dhcp service running so that other devices that connect to it get assigned an IP address?



I am able to configure the dhcp service on the pi by following this link:



https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md



but the article asks for disabling the wpa_supplicant by adding nohook wpa_supplicant to the end of /etc/dhcpcd.conf while I am supposed to run wpa_supplicant in order to enable WiFi p2p



how can I do that?







linux networking






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 9 at 23:35









MohyddinMohyddin

112




112




migrated from superuser.com Feb 10 at 9:04


This question came from our site for computer enthusiasts and power users.









migrated from superuser.com Feb 10 at 9:04


This question came from our site for computer enthusiasts and power users.















  • I think the default behavior for wifi-direct is via "APIPA" addresses.

    – Tim_Stewart
    Feb 10 at 1:31






  • 1





    I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

    – Spiff
    Feb 10 at 1:51











  • so does this mean it is doable or not?

    – Mohyddin
    Feb 10 at 10:34











  • It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

    – Ingo
    Feb 10 at 12:59











  • The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

    – Ingo
    Feb 10 at 13:02



















  • I think the default behavior for wifi-direct is via "APIPA" addresses.

    – Tim_Stewart
    Feb 10 at 1:31






  • 1





    I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

    – Spiff
    Feb 10 at 1:51











  • so does this mean it is doable or not?

    – Mohyddin
    Feb 10 at 10:34











  • It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

    – Ingo
    Feb 10 at 12:59











  • The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

    – Ingo
    Feb 10 at 13:02

















I think the default behavior for wifi-direct is via "APIPA" addresses.

– Tim_Stewart
Feb 10 at 1:31





I think the default behavior for wifi-direct is via "APIPA" addresses.

– Tim_Stewart
Feb 10 at 1:31




1




1





I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

– Spiff
Feb 10 at 1:51





I second what @Tim_Stewart said. I believe Wi-Fi Direct (Wi-Fi P2P) devices use what the IETF standards call "IPv4 link-local" addresses, which in Microsoft proprietary jargon are called "APIPA" addresses. That is, self-assigned addresses in the 169.254.0.0/16 subnet.

– Spiff
Feb 10 at 1:51













so does this mean it is doable or not?

– Mohyddin
Feb 10 at 10:34





so does this mean it is doable or not?

– Mohyddin
Feb 10 at 10:34













It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

– Ingo
Feb 10 at 12:59





It is doable to use a DHCP server with WiFi Direct. But the GO (group owner) is required to implement an DHCP server: Wi-Fi Direct vs Ad-hoc mode.

– Ingo
Feb 10 at 12:59













The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

– Ingo
Feb 10 at 13:02





The link you are using does not set up a WiFi Direct connection. It installs a managed access point. That is a complete different approach.

– Ingo
Feb 10 at 13:02










0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
return StackExchange.using("schematics", function () {
StackExchange.schematics.init();
});
}, "cicuitlab");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "447"
};
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: 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
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f94063%2fenabling-wifi-direct-p2p-along-with-dhcp-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Raspberry Pi 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f94063%2fenabling-wifi-direct-p2p-along-with-dhcp-server%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕