eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

224
active users

#dhcp

2 posts2 participants0 posts today

Wenn wer Ärger mit dem #NetworkManager im #AccessPoint Mode hat oder #DHCP, #DNS upstream, DNS port usw. individuell einstellen will...
...ich kann jetzt qualifiziert helfen...🙈

Kein Witz - ich habe sowohl im NetworkManager als auch #dnsmasq jede verfluchte Zeile im Code gelesen und verstanden die das Zusammenspiel beider Dienste im AP-Mode betrifft...

#piSpot...
(minimalistischer, mobiler #HotSpot #WLAN #WWAN #ETHERNET #VPN #Tor #AdBlock #ChildProtection #RaspberryPi #Raspberry #PiZero2)

For those that run a homelab with DNS and DHCP, are you using IPv6? I'm running BIND and debating if I need to configure IPv6 just to future-proof myself. I'm not seeing any issues, at least any that I notice.

Also, I know little about IPv6, so I admit I need to do some learning.

#homelab#dns#dhcp

So I recently used a #sledgehammer where a #scalpel was needed.

I've got an #HP DL80 Gen9 with the iLO license, but without the #FlexibleLOM card... so to access the iLO I have to have an ethernet cable plugged into the first ethernet port.

Problem is, no matter what I tried in #Webmin or #NetworkManager, every reboot would re-enable that port... which would then get a IP via DHCP (even when I'd disabled it in nm...), which would mean #Zabbix would pick it up as a client and add it.. meaning every time a disk got a little "backed up", I'd get two alerts, and this machine has 12 very old SATA drives in it.

Tired of messing with the damned thing, I finally got out the sledgehammer....
....and blacklisted HP's #OUI from the #DHCP server.

No IP, no extra client created in Zabbix, and only the normally-annoying amount of alerts.

I'll #fsck with it for real, later...

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?

@mwl I’m reading Absolute #FreeBSD and thought I’d ask you for your current opinion on #DHCP for servers: when you wrote the book you didn’t seem excited about it, but - with few exceptions - it is a convenient way to keep an updated list of server IP addresses, to ensure DNS stays up-to-date and to propagate some network changes across a fleet of computers: replacing a router or DNS servers comes to mind. The obvious drawbacks are if DHCP doesn’t work or is maliciously overridden.

Wie kann ich in /etc/network/interfaces in #Debian es einstellen, dass auf allen Interfaces #DHCP gemacht wird, auch wenn ich jetzt noch nicht weiß, wie das Interface in Zukunft heißen wird?

Jetzt steht da halt:
iface enp1s0 inet dhcp

Aber auf einer anderen Hardware heißt das Ding ja vielleicht eth0 statt enp1s0...

Also was tun?
Brauch ich ein Startupscript, dass die Config generiert?