3 ms·

Don’t fib

• Hikikomori 7mo ago
  No fibbing. Network devices don't use brackets.
  • tonymet 7mo ago
    curl URL Format curl -6 "[2001:db8::1]:8080/" wget URL Format wget "[2001:db8::1]" ssh Standard Login ssh user@2001:db8::1 ssh Specified Port ssh -p 2222 user@2001:db8::1 scp Remote Path scp file.txt [2001:db8::1]:/tmp/ rsync Remote Path rsync -av file.txt [2001:db8::1]:/tmp/ nc (netcat) Positional nc -6 2001:db8::1 80 telnet Positional telnet 2001:db8::1 80. nmap Target nmap -6 2001:db8::1
    • BenjiWiebe 7mo ago
      This is kinda arguing semantics, but: The address doesn't use brackets.You include brackets to delineate the address, if the address-containing string could include colons already. So any place that can only take addresses, not some sort of URL, should/can (of course, the program author can do whatever he/she wants!) accept addresses without delineation.
      • tonymet 7mo ago
        List all of the network CLI tools that need brackets or even shell escapes for ipv4 addresses. 90% of HN replies are debating trivialities to attempt to skirt the point. The point is that ipv6 usability is worse. CLI usability is a good example. There are many benefits to ipv6, but let’s at least admit the faults so they can be addressed and encourage further adoption.