/explore
|
You are here 
|
blog.cyphermox.net | ||
| | | | |
zwischenzugs.com
InAnatomy of a Linux DNS Lookup - Part II covered: nsswitch /etc/hosts /etc/resolv.conf pingvshoststyle lookups and inAnatomy of a Linux DNS Lookup - Part III covered: systemdand itsnetworkingservice ifupandifdown dhclient resolvconf and ended up here: A (roughly) accurate map of what's going on Unfortunately, that's not the end of the story. There's still more things... |
|
| | | | | ||
| | | | |
www.enricozini.org
|
|
| | | | | ||
| | | | |
blog.daknob.net
[AI summary] The article details a comprehensive setup of a VyOS router configured as an IPv6-First LAN, connecting to an ISP via PPPoE, requesting a /56 IPv6 prefix using DHCPv6-PD, and creating two VLANs with IPv4 and IPv6 capabilities. It includes NAT64, DNS64, SLAAC, and firewall configurations to ensure IPv6 connectivity and IPv4 fallback, while promoting IPv6 usage over IPv4 where possible. |
|
| | | | | ||
| | | | |
abstractexpr.com
Tracing a program with strace generates a lot of output because of the sheer number of syscalls every program calls during its runtime. This can become overwhelming very quickly, making it hard to analyze the trace and find what you are looking for. Fortunately, strace has several features that allow you to limit which syscalls... |
|
| | | |||
