summary refs log tree commit diff
path: root/nixos/tests/networking.nix
Commit message (Collapse)AuthorAge
...
* nixos/networking: network is online if default gw setFranz Pletz2017-09-18
| | | | | | | | | | Previously services depending on network-online.target would wait until dhcpcd times out if it was enabled and a static network address configuration was used. Setting the default gateway statically is enough for the networking to be considered online. This also adjusts the relevant networking tests to wait for network-online.target instead of just network.target.
* networking/bonds: fix examplesProfpatsch2017-03-08
| | | | | | | After the change of the bonding options, the examples were not quite correct. The diff is over-the top because the new `let` needs everything indented. Also add a small docstring to the `networkd` attr in the networking test.
* Merge pull request #22822 from Mic92/iputilsJörg Thalheim2017-02-22
|\ | | | | iputils: 20151218 -> 20161105
| * replace ping6 with pingJörg Thalheim2017-02-17
| | | | | | | | | | | | | | | | | | reason: after the upgrade of iputils from 20151218 to 20161105 functionality of ping6 and tracepath6 was merged into ping and tracepath. Ping is now mostly a drop-in replacment for ping6, except that selecting a specific interface is done by encoding it into the address (ex.: fe80::1%eth0) rather then specifing it with the `-I` flag.
* | networking.bonds: add support for arbitrary driverOptionsProfpatsch2017-02-16
|/ | | | | | | | | Until now the four attributes available very selectively provided a small subset, while copying upstream documentation. We make driver options an arbitrary key-value set and point to kernel documentation, which is always up-to-date. This way every option can be set. The four already existing options are deprecated with a warning.
* networking test: test IPv6 with RA and DHCPv6Nikolay Amiantov2017-01-15
|
* tests.networking: remove network-interfaces.targetAlexander Ried2016-09-13
|
* nixos/tests/networking: Expose subtests via attrsaszlig2016-03-01
| | | | | | | | | | | | | | | So far the networking test expression only generated a single test depending on the passed "test" attribute. This makes it difficult to autodiscover the subtests with our shiny new callSubTests function. This change essentially doesn't change the behaviour of the subtests but rather exposes them as an attribute set instead of relying on a particular input argument. The useNetworkd argument still exists however. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @wkennington
* nixos/tests/networking: Add a test for loopbackaszlig2015-12-18
| | | | | | | | | | | | | | | | It serves as a regression test, because right now if you enable networking.useNetworkd the default loopback interface doesn't get assigned any IP addresses. To be sure, I have bisected this and it has been introduced with the update to systemd 228 in 1da87d4. Only the "scripted" networking tests have to succeed in order to trigger a channel update of nixos-unstable, so I'm leaving this test as broken and we have to figure out next what's the *exact* reason for the breakage. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* all tests: added meta.maintainers sectionJoachim Schiele2015-07-12
|
* nixos/tests/networking: Clean up and attempt to make more reliableWilliam A. Kennington III2015-04-10
|
* nixos/network: Remove debug output in testsWilliam A. Kennington III2014-11-30
|
* nixos/networking: More fixesWilliam A. Kennington III2014-11-29
|
* nixos/tests: Add networking tests for basic functionalityWilliam A. Kennington III2014-11-29