summaryrefslogtreecommitdiffstats
path: root/roles/network
AgeCommit message (Collapse)AuthorFilesLines
2026-02-12Handle avahi removal in network role onlyAhmed Abdelhalim1-0/+5
Since it can cause problems (following the archlinux wiki recommendations) we keep the handling of that in the network role and ignore idempotence testing failures in other roles too
2026-01-24Fix ansible 2.20.1 deprecation warning about ansible_varsAhmed Abdelhalim2-9/+9
2026-01-09Test fixing idempotent test failure on archlinuxAhmed Abdelhalim1-4/+4
Co-authored-by: claude.ai
2025-12-16Remove company from the roles metaAhmed Abdelhalim1-1/+0
2025-09-22Attempt fixing avahi test by pinning versionsAhmed Abdelhalim1-8/+0
2025-09-22Attempt fix of avahi/dhcpcd uninstall in debian/ubuntuAhmed Abdelhalim1-1/+9
2025-09-21Disable connectivity detectionAhmed Abdelhalim1-1/+1
2025-09-20Migrate to the new loop syntaxAhmed Abdelhalim1-4/+4
2025-09-15Update network role to remove dhcpcd dependencyAhmed Abdelhalim6-6/+15
Fix install on ubuntu not having networking service stated by default on ubuntu
2025-09-10Add recommended argument_specsAhmed Abdelhalim1-0/+2
2025-09-10Follow the ansible recommendation of using systemd_serviceAhmed Abdelhalim2-5/+5
2025-09-10Refactor role dependencies to be more module modularAhmed Abdelhalim3-6/+7
This modularity means that each role can be installed in a playbook by itself as long as the other roles exist around it. This also straps the ensure dependency packages exist in any of the roles tasks, they should be moved to their own roles and configured properly if needed.
2025-09-03Fix archlinux failureAhmed Abdelhalim1-0/+1
The root causes why the idempotence test to fail is that Docker bridge creation sends netlink events to socket Socket activation starts systemd-networkd.service despite disabled state Idempotence test finds service running when expecting stopped
2025-09-02Add dig and nslookup deps for debugging networking issuesAhmed Abdelhalim2-1/+2
2025-09-02Refactor the network fix for piholeAhmed Abdelhalim1-14/+4
2025-09-02Fix pihole and network manger DNS when VPN isn't activeAhmed Abdelhalim3-6/+12
2025-09-01Fix networking issues when VPN isn't activeAhmed Abdelhalim5-5/+33
2025-09-01Fix wireguard_gateway role being slowAhmed Abdelhalim1-2/+4
The pihole lookup DNS queries when the VPN connection is up was slow. One of the culprits was the quad9 servers were taking long time when using VPN The other issue was the previous routing tables that used to work with the fritzbox (with DHCP) which wasn't fully working was conflicting with the VPN route tables and causing loops and delays. Now most of the VPN queries are working fast but some requests are taking some time, probably due to the VPN trying to check/block ads and malware! Also minor fixing to the pre tasks and documentation
2025-08-31Allow network role to configure ipv6Ahmed Abdelhalim3-0/+18
2025-08-21Fix the wireguard installAhmed Abdelhalim1-6/+0
The conflict was due to resolvconf was removing the systemd-resolved configuration and that was causing the network to go down and the fallback on the statically managed resolv.conf (which wasn't able to resolve the DNS) due to how network manager requiring the DNS resolution to happen through systemd-resolved
2025-08-21Fix network role to install via chrootAhmed Abdelhalim2-4/+6
The removal of the resolv.conf DNS configuration is required by the wireguard not to have conflicting DNS configuration resolvers between the static system fallback and the NetworkManager resolver (using systemd-resolved) and the VPN DNS
2025-08-21Add wireguard role and fix testingAhmed Abdelhalim1-0/+2
The testing was failing because the use of the example files with the same domain names, resulted in the files and the molecule variable were being merged and therefore running tasks that would fail on test (example, setting a fake VPN connection that wouldn't start).
2025-08-19Fix install ubuntu and wifi configsAhmed Abdelhalim2-1/+1
2025-08-19Fix meta strings quotingAhmed Abdelhalim1-9/+8
2025-08-19Fix pihole install to work on raspberry and simplify on archAhmed Abdelhalim1-2/+5
2025-08-16Refactor network role to remove NetworkManager/dhcpcd/networkd conflictAhmed Abdelhalim7-67/+43
2025-08-16Fix conflicting NetworkManger/systemd-networkdAhmed Abdelhalim4-3/+16
2025-08-11Add network ipv4 configurationsAhmed Abdelhalim4-1/+26
2025-08-11Refactor: move hostname into its own roleAhmed Abdelhalim3-27/+0
2025-08-11Use quad9 as the main DNS with cloudflare/google fallbacksAhmed Abdelhalim1-3/+2
2025-08-11Clean up the archlinux network roleAhmed Abdelhalim1-3/+1
2025-08-11Refactor playbook to simplify package installs for different OSsAhmed Abdelhalim2-7/+6
2025-08-11Ensure package cache is updated in playbook pre-taskAhmed Abdelhalim2-2/+0
2025-08-11Simplify playbook by requiring the required_for_boot tag on rolesAhmed Abdelhalim3-11/+0
Instead of optimizing for task execution for boot, it's simpler and almost as equally safe (if not even more) to require the role for boot instead of requiring each of it's needed tasks. This will also prevent having internal bugs because a set fact wasn't required for boot and didn't add the info (similar to the fix in commit: 9f72c58)
2025-08-11Replace avahi with systemd-resolved/systemd-networkdAhmed Abdelhalim6-9/+75
2025-08-11Refactor to simplify debian network roleAhmed Abdelhalim6-35/+36
2025-08-11Fix when running from distro-install playbook and fix testingAhmed Abdelhalim2-0/+2
2025-08-11Add network roleAhmed Abdelhalim13-0/+280