How to disable wpa _ supplicant in dhcpcd?
In the same example, the wlan0 interface (e.g, the one to be used as AP), defines a static IP address and network mask: Also, it disables the wpa_supplicant hook, so that wpa_supplicant is not activated for this interface. The denyinterfaces directive of /etc/dhcpcd.conf disables processing specific interfaces.
How to call wpa _ supplicant for a static IP address?
For wlan0, static IP address and no wpa_supplicant: For wlan1, no changes to the default /etc/dhcpcd.conf, but had to create an interface-specific version: Although this is an answer, @Nasha above was correct: you can specify a different wpa_supplicant.conf file per interface. Leaving this (wrong) answer here as it may prove useful.
How to disable processing specific interfaces in dhcpcd?
The denyinterfaces directive of /etc/dhcpcd.conf disables processing specific interfaces. In this case, specific configurations, like setting a static IP address of an interface, should be done by different services (like systemd-networkd via configuration files in /etc/systemd/network/ directory).
How to configure dhcpcd to ignore wlan1?
Use /etc/dhcpcd.conf. From the man pages: When discovering interfaces, the interface name must not match pattern which is a space or comma separated list of patterns passed to fnmatch (3). So just add denyinterfaces wlan1 to dhcpcd.conf and dhcpcd will ignore that interface when sending DHCP requests.
What happens if I set static IP for wlan0 in dhcpcd?
If I set a static IP for wlan0 in dhcpcd.conf, dhcpcd still calls wpa_supplicant and so even with a static IP it joins the AP – which causes conflicts when trying to run hostapd.
How does wpa supplicant work in wireless LAN?
A supplicant in wireless LAN is a client software installed on end-user’s computer that needs to be authenticated in order to join a network. Now let’s see how to connect to WPA2 wireless network using wpa_supplicant. First, make sure your wireless card is enabled.