| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
This allows the subsequent DHCP request to get the same IP address back,
which means it only needs one address for first boot, and the address
can be pre-allocated by the DHCP server before deployment.
This is needed for the floating address range to be allocated in some
set-ups, such as our local one at the office, where a subnet in a
different class is routed to the server.
|
| |
|
|
|
|
|
|
|
| |
This adds masking config for the virtual devices to prevent them from
attempting to DHCP, and stops us from giving the ip of eno1 to the
bridge device, since eno1's address was obtained by DHCP, so it's
against the rules to statically allocate that address to an interface.
Now, we DHCP for a new address for the bridge.
|
| | |
|
| |
|
|
|
|
| |
If we leave that interface with its address, then the routing table is
incorrect, as it will try to send connections out from an interface that
cannot handle them.
|
| |
|
|
|
|
|
|
|
|
| |
After the external interface has been bound to Open vSwitch, we should
not attempt to DHCP on it, as it won't receive the DHCP responses.
Attempting to DHCP results in startup stalling on network-online.target,
because systemd-networkd-wait-online.service looks at every network
interface it should configure based on the [Match] sections, and waits
for all of them to be configured by systemd-networkd, which will never
finish if DHCP is broken.
|
| |
|
