1. 23 Aug, 2021 1 commit
  2. 10 Aug, 2021 1 commit
    • Jouke Witteveen's avatar
      Reach network.target before communicating · 02ecc4e1
      Jouke Witteveen authored
      Let the netctl profile service yield at the last moment before any
      communication on the interface takes place. That way, we catch as many
      problems as possible without suffering unpredictable delays.
      This means network.target is reached earlier for wireless connections.
      02ecc4e1
  3. 06 Jul, 2021 1 commit
  4. 13 May, 2021 2 commits
  5. 17 Jan, 2021 1 commit
    • Jouke Witteveen's avatar
      Add verify subcommand to netctl · 9b70046f
      Jouke Witteveen authored
      The name of the subcommand mirrors the same subcommand of systemd-analyze.
      
      Verification before restarting would be useful. However, verification
      requires the profile file to be readable by the current user. The current
      user may be a regular user with permission to control systemd, so
      restarting does not require the profile file to be readable. Therefore, we
      do not attempt verification before restarting.
      9b70046f
  6. 16 Oct, 2020 1 commit
  7. 09 Oct, 2020 3 commits
  8. 26 Jun, 2020 1 commit
    • Семён Марьясин's avatar
      Speed up 'netctl list' · b34f51a1
      Семён Марьясин authored and Jouke Witteveen's avatar Jouke Witteveen committed
      When you call `netctl list`, it calls `systemctl status` for each of the
      profiles. By default, `systemctl status` fetches the last log entries from the
      journal, which is often a time-consuming operation. Additionally, the status
      output is not meant for machine processing.
      b34f51a1
  9. 27 Apr, 2020 1 commit
  10. 24 Apr, 2020 1 commit
    • Jouke Witteveen's avatar
      Bring dhcpcd support up to date (FS#66349) · 115411c3
      Jouke Witteveen authored
      With dhcpcd 9, the rundir has moved. We follow this change and no longer
      support older versions of dhcpcd.
      While here, also support information only use on IPv6, which has been
      possible with dhcpcd for quite a while already.
      
      Reported by: Antonio Rojas <arojas@archlinux.org>
      115411c3
  11. 17 Apr, 2020 3 commits
  12. 10 Apr, 2020 2 commits
  13. 28 Mar, 2020 4 commits
  14. 25 Dec, 2019 1 commit
  15. 26 Jun, 2019 1 commit
  16. 12 Feb, 2019 1 commit
  17. 07 Feb, 2019 3 commits
    • Jouke Witteveen's avatar
      Move away from using wpa_actiond · f2c3edb1
      Jouke Witteveen authored
      The same functionality is provided by wpa_supplicant, so we do not need
      an extra and Arch Linux specific dependency.
      f2c3edb1
    • Jouke Witteveen's avatar
      Do not allow the kernel to try and be smarter than us · 162af2a4
      Jouke Witteveen authored
      When accept_ra is set to 1, router advertisements are still ignored if
      the interface is in forwarding mode. For such configurations, the
      interface should have a static configuration and netctl already sets
      accept_ra to 0. Setting it to 2 otherwise forces the kernel to accept
      router advertisements regardless of the forwarding setting.
      162af2a4
    • Eli Schwartz's avatar
      Makefile: specify the correct shell to use · ea9ccfd2
      Eli Schwartz authored and Jouke Witteveen's avatar Jouke Witteveen committed
      The Makefile commands in use include bash-specific features like brace
      expansion, and thus cannot run under the default /bin/sh shell as that
      may or may not be GNU bash (bash supports brace expansion even in posix
      mode).
      
      Consequently, the Makefile failed to execute correctly when the system
      /bin/sh was a different sh implementation, such as dash or busybox ash.
      
      Fix this by declaring the SHELL which will be used when running all
      commands.
      ea9ccfd2
  18. 15 Nov, 2018 3 commits
  19. 07 Aug, 2018 1 commit
  20. 04 Aug, 2018 1 commit
  21. 03 Aug, 2018 1 commit
  22. 02 Aug, 2018 1 commit
  23. 29 Jul, 2018 1 commit
  24. 28 Jul, 2018 1 commit
  25. 26 Jun, 2018 2 commits
  26. 25 Jun, 2018 1 commit
    • Jouke Witteveen's avatar
      wifi-menu: Support UTF-8 encoded SSIDs (FS#45384) · e4638274
      Jouke Witteveen authored
      Strictly speaking, we should check with the SSIDEncoding value sent out
      by the station, as specified in the 2012 version of 802.11 (page 566),
      but wpa_supplicant does not (yet) expose this information and stations
      may not set the field to UTF-8 and still encode their SSID accordingly.
      
      We therefore assume SSIDs to be UTF-8 encoded (the only real alternative
      is treating SSIDs as raw byte string) in wifi-menu. Note that wifi-menu
      is only provided as a convenience and many/most use cases involve
      writing profile files manually.
      
      When the current character map is not set to UTF-8, wifi-menu will only
      use ASCII characters in its screen output.
      This can be forced using for example `LC_CTYPE=C wifi-menu`.
      
      Thanks to Declspeck <declspeck@declblog.com> for their activity on the
      Flyspray task.
      e4638274