Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • bookworm
  • pu/disable-hotplug-detection
  • pu/ifupdown+wireless-v2
  • pu/ifupdown+wireless
  • salsa-ci
  • jessie
  • jessie-kfreebsd
  • wheezy
  • pu/wpa
  • people/pkern/vlan
  • people/sorina/write_config
  • feature/ipv6
  • feature/write_config
  • people/pkern/ipv6
  • people/gaudenz/check_netmask
  • people/sorina/check_netmask
  • people/avtobiff/fix-magic-numbers
  • people/sorina/link_timeout
  • people/sorina/coding_style
  • 1.195
  • 1.194
  • 1.193
  • 1.192
  • 1.191
  • 1.190
  • 1.187+deb12u1
  • 1.189
  • 1.188
  • 1.187
  • 1.186
  • 1.185
  • 1.184
  • 1.183
  • 1.182
  • 1.181
  • 1.180
  • 1.179
  • 1.177
  • 1.176
40 results
Blame Permalink
  • Cyril Brulebois's avatar
    815cdfcc
    Fix DHCP+SLAAC case on wireless interfaces. · 815cdfcc
    Cyril Brulebois authored 
    At least in the WPA case, wpa-* options cannot be set in both the “inet
dhcp” and the “inet6 auto” stanzas: testing shows that wpa_supplicant
would trigger association, possibly get an address via DHCP, before
moving on to the SLAAC stanza, and deauthenticate, leaving the network
interface DOWN.

If both DHCP and SLAAC are enabled, IPv6 settings should be received
via RAs anyway, so writing a SLAAC entry seems superfluous.
    815cdfcc
    History
    Fix DHCP+SLAAC case on wireless interfaces.
    Cyril Brulebois authored 
    At least in the WPA case, wpa-* options cannot be set in both the “inet
dhcp” and the “inet6 auto” stanzas: testing shows that wpa_supplicant
would trigger association, possibly get an address via DHCP, before
moving on to the SLAAC stanza, and deauthenticate, leaving the network
interface DOWN.

If both DHCP and SLAAC are enabled, IPv6 settings should be received
via RAs anyway, so writing a SLAAC entry seems superfluous.
write_interface.c 9.25 KiB