Skip to content
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

Lack of IPv4 doesn't mean disconnected #275

Merged
merged 1 commit into from
Apr 6, 2021
Merged

Lack of IPv4 doesn't mean disconnected #275

merged 1 commit into from
Apr 6, 2021

Conversation

fhunleth
Copy link
Member

@fhunleth fhunleth commented Apr 6, 2021

The Internet connectivity checker would declare that the network was
disconnected if an IPv4 address wasn't available. This is untrue for a
couple reasons:

  1. IPv6 addresses are available
  2. DHCP and layer 2 protocols could still be used

This also had a weird side effect where interfaces would initially come
up (lan connectivity), then go disconnected when an IPv4 address
wasn't found, and then come back when an IPv4 address was found.

Fixes #268

The Internet connectivity checker would declare that the network was
disconnected if an IPv4 address wasn't available. This is untrue for a
couple reasons:

1. IPv6 addresses are available
2. DHCP and layer 2 protocols could still be used

This also had a weird side effect where interfaces would initially come
up (`lan` connectivity), then go disconnected when an IPv4 address
wasn't found, and then come back when an IPv4 address was found.

Fixes #268
@fhunleth fhunleth merged commit 6ecbe54 into main Apr 6, 2021
@fhunleth fhunleth deleted the no-ipv4-still-lan branch April 6, 2021 17:36
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.

wlan connection status transition order does not match the document(?)
3 participants