4 ms·
Even easier on macOS. Something like this should work: ifconfig enX inet6 fd42:dead:beef::1 prefixlen 48 No ned to bring it up as it should already be up.
by sgt 1mo ago
Even easier on macOS.
Something like this should work:
ifconfig enX inet6 fd42:dead:beef::1 prefixlen 48
No ned to bring it up as it should already be up. enX should be your USB/thunderbolt ethernet adapter, e.g. en6.
Then you can go ahead and transfer with socat to your other machine, even if it's a Linux machine. I tend to use nc but socat will definitely be faster.
Why the deadbeef network one might wonder? It's private space so won't conflict with public addresses.
That being said though, in 99% cases of big files I'll just airdrop the files!
- Steltek 1mo agoifconfig still probably works on Linux too but it's discouraged because, frankly, it sucks compared to ipconfig2. Most of macOS' CLI feels old and crusty. Which makes sense when you realize it's a fossilized niche BSD from the early 00's.
- sgt 1mo agoifconfig(8) is meant for low level stuff. What Linux did was replace ifconfig with another low level (e.g. ipconfig2), which makes more sense there I suppose. But don't get the impression that ifconfig is the easiest way in macOS on the CLI, it's networksetup(8).
- ButlerianJihad 1mo agoIt seems quite strange to me that hackers have adopted "0xdeadbeef" as some sort of generic hex string to use in production. AFAIK, "0xDEADBEEF" originated as a "magic number" in systems like IBM RS/6000 and Solaris, and it was a red-flag number! It meant something in your system was wrong and you'd better check it out! https://en.wikipedia.org/wiki/Magic_number_(programming)#Debug_value https://en.wikipedia.org/wiki/Magic_number_(programming)#Deb... Surely there are more pleasant, vegan hex strings to use, if you want to indicate an ephemeral IPv6 address?