Skip to content

NEWS: dhcpcd>=7.1.0 update may require manual intervention #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2019
Merged

NEWS: dhcpcd>=7.1.0 update may require manual intervention #34

merged 1 commit into from
Jan 25, 2019

Conversation

maxice8
Copy link
Contributor

@maxice8 maxice8 commented Jan 23, 2019

Users of the 10-wpa_supplicant hook will need to adjust their systems to guarantee
that wireless connection keeps working.

The following actions are required when dhcpcd is updated to 7.1.0 for users of wpa_supplicant hook.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for users of the `wpa_supplicant` hook

The following actions are required when dhcpcd is updated to 7.1.0 for users of wpa_supplicant hook.

1. Make sure wpa_supplicant is at least 2.6_14
2. [enable](https://docs.voidlinux.org/config/services/index.html) the wpa_supplicant service.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enable

@maxice8
Copy link
Contributor Author

maxice8 commented Jan 23, 2019

@Vaelatern updated and made a few other changes, please re-check

comments: false
---

Starting with 7.1.0 the [dhcpcd(8)](https://man.voidlinux.org/dhcpcd.8) package is dropping the 10-wpa_supplicant hook
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Starting with 7.1.0, the (added comma)

---

Starting with 7.1.0 the [dhcpcd(8)](https://man.voidlinux.org/dhcpcd.8) package is dropping the 10-wpa_supplicant hook
in favour of setting CONFIG_MATCH_IFACE in [wpa_supplicant(8)](https://man.voidlinux.org/wpa_supplicnt.8), as suggested by upstream.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

. Instead of the hook, upstream wants users to set CONFIG_MATCH_IFACE in [wpa_supplicant(8)](https://man.voidlinux.org/wpa_supplicnt.8)

(maybe this should be a doc link instead? wpa_supplicant.conf?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or reference the -M option, at least. AFAIK that is what is documented in wpa_supplicant(8).

in favour of setting CONFIG_MATCH_IFACE in [wpa_supplicant(8)](https://man.voidlinux.org/wpa_supplicnt.8), as suggested by upstream.

Users of the 10-wpa_supplicant hook will need to adjust their systems to guarantee
that wireless connection keeps working.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that their wireless connection

Users of the 10-wpa_supplicant hook will need to adjust their systems to guarantee
that wireless connection keeps working.

The following actions are required when [dhcpcd(8)](https://man.voidlinux.org/dhcpcd.8)is updated to 7.1.0 for users of the 10-supplicant hook.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing space after )

@Duncaen
Copy link
Member

Duncaen commented Jan 24, 2019

There is a typo https://man.voidlinux.org/wpa_supplicnt.8https://man.voidlinux.org/wpa_supplicant.8

@maxice8
Copy link
Contributor Author

maxice8 commented Jan 24, 2019

pushed changes fixing it

@maxice8 maxice8 merged commit 735d0d6 into void-linux:master Jan 25, 2019
@maxice8 maxice8 deleted the dhcpcd branch January 25, 2019 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants