#lan

Belåna Fastighet @belanafastighet@mastodon.nu · Aug 05, 2026

https://xn--belnafastighet-nib.se/lan-pa-hus-och-lagenhet-sa-paverkar-rantan-manadskostnaden/ #lan #ranta #hus #fastighet

0

gadgetChecks.de @gadgetchecks@burningboard.net · Jul 21, 2026

UGREEN NAS: WLAN VS. 2,5-GBE-LAN (DH4300 PLUS) – TUTORIAL https://gadgetchecks.de/ugreen-nas-wlan-vs-25-gbe-lan-am-dh4300-plus-tutorial/ . . . #ugreen #ugreennas #nas #nasync #dh4300plus #homeserver #raid5 #smb #lan #wlan #25gbe #ethernet #netzwerk #networking #homelab #datenspeicher #fileserver #crystaldiskmark #grafana #tutorial

0

Carl Liebold 🚀 @VintageVeloce@techhub.social · Jul 03, 2026

Today it is Sophie guarding the old network equipment! #cats #catsofmastodon #caturday #network #LAN

31

0

14

0

JdeBP @JdeBP@mastodonapp.uk · Apr 26, 2026

Replying to @keefeglise@mastodonapp.uk

@keefeglise@mastodonapp.uk The DHCP server running on that router won't give anyone else that same address whilst it has leased it to your NAS machine. But it's not actually *static*. It's dynamic. It's just dynamic over and over with *usually* the same result. It's a convenience feature that the DHCP client and server, after either one has restarted, will attempt to lease the same IP address that was used before. So most people don't experience things shifting a lot, because *usually* this feature keeps the address lease the same as prior to the restart. @stroz@infosec.exchange @dzwiedziu@mastodon.social @gavin57@toot.wales #LAN #NetworkAdministration #DHCP

0

1

0

JdeBP @JdeBP@mastodonapp.uk · Apr 26, 2026

Replying to @JdeBP@mastodonapp.uk

@keefeglise@mastodonapp.uk To make it *actually* static, either the DHCP server has to be explicitly told that network card A always gets a lease for IP address P when it asks, or the machine with network card A has to be told to not use DHCP at all and to instead always use IP address Q. In the latter case, there are anti-collision mechanisms, but in theory the DHCP server can lease another machine IP address Q, causing a conflict, *unless* that address is outwith the range of IP addresses that the DHCP server will hand out leases for. So if the DHCP-leasable IP address range is (say) 192.168.1.100 to 192.168.1.253, address Q would have to be somewhere in the range 192.168.1.2 to 192.168.1.99. (Simple example. Real world can get more complex. May contain traces of nuts.) @stroz@infosec.exchange @dzwiedziu@mastodon.social @gavin57@toot.wales #LAN #NetworkAdministration #DHCP

0

JdeBP @JdeBP@mastodonapp.uk · Apr 26, 2026

Replying to @keefeglise@mastodonapp.uk

@keefeglise@mastodonapp.uk If it's the EE 5G Smart Hub, I've just had quick shufti of its user guide. It's a pretty feature-poor router, compared to (say) even off-the-shelf TP Link kit, and does not present the capability that people are talking about. So you cannot fix this by telling the DHCP server inside your router to always hand out the same address to your NAS machine. You have to fix this by telling your NAS machine to not autoconfigure by using a DHCP client. Which means putting in a bunch of settings on your NAS machine. The UI on your EE hub will at least tell you what IP address range to avoid, and let you carve out some space for statically allocated IP addresses. https://ee.co.uk/content/dam/help/user-guides/smart5g-ug.pdf#page=41 @stroz@infosec.exchange @dzwiedziu@mastodon.social @gavin57@toot.wales #DHCP #EE #LAN #NetworkAdministration

3

4

0

Wydamn @wydamn@social.linux.pizza · Feb 20, 2026

After looking at what hostnames I'm using on my LAN, I realized it's a pretty basic setup. What are some good setups or recommendations for setting/using hostnames in a #linux home #LAN with a #homelab setup? I'm not really trying to mimic a corporate setup though there might be some useful lessons to learn there too. I'm looking using TLDs for my hostnames that could not be used in the wild, but whenever I look for banned or reserved TLDs it's always in respect to certification, and not the TLDs themselves being prevented from use.

0

About This Hashtag

Related