Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This requires dhcpcd 6.4.0 or newer.
|
|
|
|
Some things should not be run with the restrictive umask.
This provides a means to do so: do_readable.
|
|
Somehow, these have gone unnoticed for quite some time.
|
|
|
|
|
|
The pid file contains more than just the pid: on the second line it
records the interface pppd manages.
|
|
The following changes introduced in Bash 4.3 necessitate this commit:
- Setting the array attribute no longer initializes an array.
- Empty-but-set arrays no longer pass [[ -v ]].
Previous attempts:
feb669f4b2a15e6ea1d84be336f12be4650f9d2d
711c46457ae9fef52c7c529d89c67d0d526f73ef
e8210827fd59e4539a70af55cb452b211633fedd
|
|
- Don't bring an interface down if it is not brought up for wireless
connections.
- Often, `read` needs '-r'.
|
|
This option sets a frequency to use in ad-hoc mode for a newly created IBSS
(when it is going to be created).
|
|
|
|
|
|
|
|
|
|
`shift 3` doesn't do anything if there are only 2 parameters.
|
|
|
|
|
|
|
|
After 755c8d5, rf_enable did not know the rfkill path anymore.
Observed by: Tom <reztho@archlinux.us>
|
|
|
|
|
|
|
|
Ifenslave is deprecated according to the kernel documentation:
https://www.kernel.org/doc/Documentation/networking/bonding.txt
It also added an additional, unnecessary dependency. I tried to update
the documentation to reflect this change.
|
|
|
|
|
|
Instead of using systemctl to manage the netctl-auto service, some users try to
invoke the start/stop commands of netctl-auto directly. Although this behaviour
is explicitly discouraged in the man page, this seems to be a source of
confusion.
The changes introduced in de8c80f will cause other netctl-auto commands to fail
if the netctl-auto service was not spawned by systemd. Therefore, this change
emits an error message if netctl-auto [start|stop] is invoked from an
interactive terminal.
|
|
Instead of searching for wpa_actiond pid files, the netctl-auto
utility now looks for running systemd netctl-auto units.
|
|
This should at some point take care of most PPP use cases, but
currently is just a frontend to pppoe. The main difference is that the
new connection type keeps track of profiles by their 'dynamic' interface
name. Hence it is not wise to use both pppoe and ppp profiles.
|
|
Temporarily enable the interface's rfkill (if specified) before issuing a scan
and restore its state afterwards.
|
|
|
|
Needed since 8a41497.
|
|
Support for additional DHCP clients is now easy to add.
|
|
The main benefit is the possibility to use interface hooks for links
that are created at runtime.
|
|
After several requests, here is SkipDAD to bypass Duplicate Address
Detection.
|
|
It is not of much use.
|
|
|
|
Now a bit more verbose when useful.
|
|
Errata to f5065. $Key has a capital.
|
|
|
|
Some abuse of the stack, but that should be no problem: the user has to
enter around 10000 existing profile names which (s)he does not want to
overwrite before a stack overflow occurs.
Feature suggested by: Paul Bienkowski <opatutlol@aol.com>
|
|
- Refactorization of option file generation
- Introduction of optional additional pppd options file specification
- Introduction of unit specification option for pppoe connections
|
|
Also: tag error messages as systemd error messages when the messages are
not directed to the terminal.
|
|
|
|
Netctl files can potentially contain passwords or execute code as root.
|
|
Testing whether transmission is blocked at all is now possible through
[[ -n $(rf_status "$Interface" "$RFKill") ]]
|
|
This is especially useful to enforce connecting in the 5 GHz band.
|
|
New timeout is 30 seconds, which equals the current dhcpcd default.
|
|
Hex WEP keys are of even length, ASCII keys are of odd length.
Using this information we make wifi-menu work better for WEP networks.
|
|
Needed in case the remote side of a tunnel is set to 'any'.
|