| Age | Commit message (Collapse) | Author |
|---|
|
The DHCPv6 client can't start on an interface when DAD is ongoing.
There is a workaround in place to wait for DAD to complete, but it
only works on eth0!
|
|
Checks done to verify a dhcp-lease on the interface is updated to look for a
ip-address like response from dhclient before returning an error.
This fixes the error where a newline was enough to make the checks fail..
Updated to also make sure no newline is returned after the address to make
sure commands using adresses from this script is not cut in half by the newline,
and to be in line with the syntax on all errors. (no newline at the end)
(cherry picked from commit 8f4b8917d23b42d15b7f48eb3f814a56cc5a4343)
|
|
T1045: static route dhcp-interface: check for ip in response
|
|
Checks done to verify a dhcp-lease on the interface is updated to look for a
ip-address like response from dhclient before returning an error.
This fixes the error where a newline was enough to make the checks fail..
Updated to also make sure no newline is returned after the address to make
sure commands using adresses from this script is not cut in half by the newline,
and to be in line with the syntax on all errors. (no newline at the end)
|
|
(cherry picked from commit c03bf343285b0c79cba59df90139e491e29057b2)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Increase NTP config version from 0 to 1. For more information see [1].
ntpd: Warning: the "dynamic" keyword has been obsoleted and will
be removed in the next release
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553976
(cherry picked from commit 46d8b9b9105b67ea5ab8c06054586f66bd0daa12)
|
|
Increase NTP config version from 0 to 1. For more information see [1].
ntpd: Warning: the "dynamic" keyword has been obsoleted and will
be removed in the next release
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553976
|
|
|
|
|
|
|
|
In other words, remove top level tag nodes from radius-server and introduce
a regular "radius" node, thus we can add additional features, too. A migration
script is provided in vyos-1x which takes care of this config migration.
Change VyOS CLI from:
vyos@vyos# show vpn pptp
remote-access {
authentication {
mode radius
radius-server 172.16.100.10 {
key barbarbar
}
radius-server 172.16.100.20 {
key foofoofoo
}
}
To:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius {
server 172.16.100.10 {
key barbarbar
}
server 172.16.100.20 {
key foofoofoo
}
}
}
(cherry picked from commit 4a5db8a416fc6126a504bc3a9f1b5f6de84e119d)
|
|
In other words, remove top level tag nodes from radius-server and introduce
a regular "radius" node, thus we can add additional features, too. A migration
script is provided in vyos-1x which takes care of this config migration.
Change VyOS CLI from:
vyos@vyos# show vpn pptp
remote-access {
authentication {
mode radius
radius-server 172.16.100.10 {
key barbarbar
}
radius-server 172.16.100.20 {
key foofoofoo
}
}
To:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius {
server 172.16.100.10 {
key barbarbar
}
server 172.16.100.20 {
key foofoofoo
}
}
}
|
|
|
|
|
|
stderr is silenced to prevent useless error messages about the mail dir not being found.
|
|
stderr is silenced to prevent useless error messages about the mail dir not being found.
|
|
In other words, remove top level tag nodes from radius-server and
introduce a regular
"radius" node, thus we can add additional features, too. A migration
script is provided
in vyos-1x which takes care of this config migration.
Change VyOS CLI from:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius-server 172.16.100.10 {
key barbarbar
}
radius-server 172.16.100.20 {
key foofoofoo
}
radius-source-address 172.16.254.100
}
To:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius {
server 172.16.100.10 {
key barbarbar
}
server 172.16.100.20 {
key foofoofoo
}
source-address 172.16.254.100
}
}
(cherry picked from commit f68dda9d619ea74bed266122ac86604284e1a9e4)
|
|
In other words, remove top level tag nodes from radius-server and
introduce a regular
"radius" node, thus we can add additional features, too. A migration
script is provided
in vyos-1x which takes care of this config migration.
Change VyOS CLI from:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius-server 172.16.100.10 {
key barbarbar
}
radius-server 172.16.100.20 {
key foofoofoo
}
radius-source-address 172.16.254.100
}
To:
vyos@vyos# show vpn l2tp
remote-access {
authentication {
mode radius
radius {
server 172.16.100.10 {
key barbarbar
}
server 172.16.100.20 {
key foofoofoo
}
source-address 172.16.254.100
}
}
|
|
|
|
* Add grub-efi package dependencies
* Install grub-efi if we install on efi partition
|
|
T955: Integrating EFI into the installer
|
|
|
|
|
|
T967: Support NVMe drives in installer
|
|
In the absence of this commit, the installer hangs right after:
> How big of a root partition should I create?
|
|
I had a difficult time finding a canonical source of device name
formatting in Linux (was hoping for an RFC), but this should be pretty
close to reality.
NVMe drives are typically named as so:
- nvme0: first registered device's device controller
- nvme0n1: first registered device's first namespace
- nvme0n1p1: first registered device's first namespace's first partition
|
|
|
|
|
|
|
|
|
|
|
|
(cherry picked from commit 7de05b2de4f1b57115fd7593bfaa79f0042c10f4)
|
|
|
|
|
|
|
|
Conflicts:
Makefile.am
debian/changelog
|
|
This reintroduces hagbard's change that has somehow gone missing.
|
|
T903: Wait for IPv6 DAD to complete before attempting to start dhclient v6
|
|
If this is not done, dhclient will fail with error "Can't bind to dhcp
address: Cannot assign requested address". Also, misc whitespace fixes to
file.
|
|
|
