What is the IPv6 equivalent of 127.0.0.1
The IPv4 address 127.0.0.1 is for the local/current client. What is the opposite of the address in IPv6? I already searched for it, but only found ::1 . Is this the correct one?
ReadMeFeed / Community knowledge
DNS, routing, load balancing and hybrid cloud connectivity.
The IPv4 address 127.0.0.1 is for the local/current client. What is the opposite of the address in IPv6? I already searched for it, but only found ::1 . Is this the correct one?
I need to create a persistent network bridge for Virtual machines ( libvirt ) So this bridge does not need any physical ports, connections will be routed for this bridge. If I set this up manually, it works as I described. However I can't get this to persist between reboots. I have created the bridge in /etc/network/interfaces : auto vm-bridge iface vm-bridg
I'm experimenting with lxc/lxd in Vagrant, but i'm quite new to it. I managed to create running container, but I cannot ping anything (including 8.8.8.8) from inside of it. I can ping its IP from my top-level non-virtual system, but it refuses SSH connections. I can enter the container only directly from the direct container's host (Vagrant) by using lxc exe
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
In our system, there are three hosts all connected to the same Ethernet switch, which is illustrated below: A (192.168.0.21, WIN10_1809) <-> Switch <-> B (192.168.0.100, Debian Linux 9) ^ | C (192.168.0.201, WIN10_1809) Between any two of these hosts, there are periodically network communications, both lower-level ping operations and upper-level
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
I pulled off my patch panel today to discover that I had originally punched down the green pair (3/6) incorrectly? I never noticed because it all just worked? If it matters, the wiring is CAT6, in a CAT6A patch panel. I pulled off one of the wall jacks to ensure it’s wired correctly... and it is. I just want to know why it worked? The panel in question:
I've written a custom jail and filter in fail2ban for logging into my service. The log file is located in /var/log/motion/motion.log and a failed login generates a line like this: [0:ml1] [ALR] [STR] [Nov 02 11:42:59] handle_basic_auth: motion-stream - failed auth attempt from <ip> My jail in /etc/fail2ban/jail.local looks like this: [motion-auth] enab
I have a DB server running as a Compute Engine VM, and an API running on Cloud Run. Both are part of the same project. I want the DB VM to only be accessible from the Cloud Run code. At first I thought this should just work because the firewall has a "default-allow-internal" rule that should apply to every machine in the project. However I was still getting