[#33] Refactored existing network config #34
No reviewers
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fachschaft/nixConfig#34
Loading…
Reference in a new issue
No description provided.
Delete branch "nerf/nixConfig:nerf/networkConfig"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refactored existing network config, in a way that one only needs to supply an ip address.
No ipv6 support as of yet. (As if we would get v6 support in the next 15 years).
Also we need to get our interface names consistent in the Xen config. It shouldn't be
hard to extend this module by an optional setting to set the name though.
@ -0,0 +18,4 @@
;
cfg = config.vmNetwork;
in {
imports = [];
Ist es üblich oder notwendig, leere Imports mit hinzuschreiben?
I'm not sure if it is required (I would guess no). But I kind of find it idiomatic to put it there. We should agree if we do it or not and then enforce it across the whole codebase.
I don't mind. One precedent is https://nixos.wiki/wiki/NixOS_modules#Example which leaves it out. 🤷
@ -0,0 +41,4 @@
addrLastInt = builtins.toString (toInt (last addr) + 127);
in
concatStringsSep "." (addrInit ++ [addrLastInt]);
nameservers = ["130.83.2.22" "130.83.56.60" "130.83.22.60" "130.82.22.63"];
Hierzu sollten wir die Quelle https://www.hrz.tu-darmstadt.de/services/it_services/nameserver_dns/index.de.jsp verlinken. Aus dieser geht hervor, dass die Zeile in Reihenfolge der Hostnamen
lauten sollte. Der Server unter
130.83.2.22
hingegen liefert mir keine Antworten (mehr).bfc36a9a44
tocabd210aa6