mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

598
comptes actifs

#dhcp

1 message1 participant0 message aujourd’hui

Well my #DHCP problem is even more perplexing.

One #macmini running #Debian13 connects okay, but the other two get as far as asking for the WiFi password from the #RPi4 but never ask for an IP address as far as I can see from the #dnsmaq logs.

The Mac have different Wifi devices, but the two that won't connect to the Pi will connect to my household WiFi. All Macs running the same version of Debian.

Stumped for the moment!

For those who specialize in DHCPv6 and systemd: Is there a way to tell the DHCPv6 server "If this IP is available, just give me it, don't give me anything else", or at least get systemd to do that? I'm trying to make an oracle cloud instance running Arch+systemd-networkd that uses DHCPv6 for IP configuration only use one of two IPs assigned to the oracle instance, but leave the other one unused so I can do NDP proxying and route it to my laptop over wireguard, giving my laptop a public IPv6 address as a result, but it appears that oracle is forcing my VPS to use both IPv6 addresses, which is not what I want.
Redacted logs, for context:

Jun 18 06:08:27 somewhere systemd-networkd[-1]: eth0: DHCPv6 address 2000::4201/128 (valid for 1d 5
9min 59s, preferred for 23h 59min 59s)
Jun 18 06:08:27 somewhere systemd-networkd[-1]: eth0: DHCPv6 address 2000::1337/128 (valid for 1d 5
9min 59s, preferred for 23h 59min 59s)

Feel free to boost this for increased visibility if you wish, and if you know of any mailing lists or IRC channels I should ask on, please let me know.
Relevant tags to try to help people who might know something see this:
#dhcp #ipv6 #systemd #oracle #dhcpv6 #networking #systemdnetworkd #systemd-networkd

At IT club today a woman had a #Windows laptop that wouldn't pick up a valid #DHCP setting from the club WiFi and then refused to DNSlookup common French ISPs and obvious Antivirus websites. It was happy to connect to a website it had never seen before.

It's either exceptionally badly configured or it has #malware on it. I don't use Windows myself so I was a bit at a loss as to what to look for. Windows Defender found nothing, but I don't trust it if the machine has been compromised.

I'm planning to (eventually) do some network overkill on my small home LAN. Specifically, I'm planning to offload my #dns and #dhcp to my Protectli Vault.

I have a number of options available for both, but I'm leaning towards BIND9 for DNS and either Kea DHCP or ISC DHCP server. Yes, I know the latter is deprecated. What would push me towards Kea would be DDNS that's not too insane to set up.

Thoughts?

If you were setting up your home #network, and wanted to make sure that important, foundational, yet lightweight services Just Kept Going, how would you run them?

For example, I'm thinking about #DNS and #DHCP for the hosts that actually provide the more user-visible network #services ... so "run them as #VM/#containers on your #homelab hosts" isn't a viable option: what provides the DNS *for* those hosts?

I quite like the idea of a pair of low-cost & low-spec mini-PCs.

What would you choose?

Next step testing #IPv6only operation in my local network, I wanted to give #dhcp "option 108" (IPv6-only preferred) a try.

I'm running #ISC #dhcpd on my #FreeBSD router/firewall, so I looked at the manuals:

man.freebsd.org/cgi/man.cgi?qu

Ok, added "option option-108 00:00:00:00;" based on that, which dhcpd rejected 🤔

From finding random different examples for custom options and with some trial and error, I found I have instead to declare the option:

option v6only code 108 = integer 32;

... and then use it like this:

option v6only 0;

Ok, what's up with documentation here? 🙄

At least it works, verified on my phone running #Android 14. No #IPv4-address from my pool any more. Instead, 192.0.0.4 appeared, seems it automatically configures a #clat...

man.freebsd.orgdhcp-options