Ping ::1
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
ping g.co to test ipv6
Best ping is 127.0.0.1
It always resolves!
Try pinging 127.1 - it is the same, but shorter.
Just another tipp from someone who learned TCP/IP from reading the sources over three decades ago...
Voodoo! I had no idea.
It's all in the documentation. But people don't read anymore.
55555555
All addresses that that start in 555
were left open by the internet protocol developers just for movies and TV shows.
I don't get it, the first octet (?) max is 256.
Yes, but you can write it in different ways. If the numeric string contains a dot, left of it must be between 0 and 255, and is put in the highest byte of the address. If the rest also contains a dot, repeat, but put it into the second highest byte.
BUT: if the string does not contain a dot, the number is put into the remaining bytes.
So 123.256 is a valid address. The 123 goes into the top byte, the 256 goes into the remaining three bytes, so the address would be 123.0.1.0.
Most common example is 127.1, which is short for 127.0.0.1 - the localhost address.
255
Small correction, but an important one: 0 is a number too.
In terms of IP masking and broadcast addresses, the max is 255.255.255.255
Oof of course. 256 entries from 0 - 255.
It's been a long long time since my ccent
I prefer:
ping 133742069
(probably lands you on a list tho...it's a US DoD IP)
~~[https://iplocation.io/ip-whois-lookup/133.74.20.69](Looks like the Japanese Aerospace Agency) unless ~~I'm completely misunderstanding how entering a string of numbers without periods works in a ping
Ah yeah there's a little misunderstanding. IP addresses can be represented as 32-bit unsigned integer numbers, where each 8-bit chunk is separated by a dot.
So the conversion is: 133742069 (decimal) -> 00000111111110001011110111110101 (binary) -> 00000111.11111000.10111101.11110101 (8-bit chunks) -> 7.248.189.245 (resulting IP)
Thank you!!
ping 2130706433 for best results
There's no place like home
For those who are still confused, ping works with 32 bit unsigned integers. While there certainly are more uses, it's a much more convenient method for storing IP address in a database as it's easier to sort and index than 4 numbers separated by 4 periods
http://www.aboutmyip.com/AboutMyXApp/IP2Integer.jsp?ipAddress=1.1.1.1
it's so simple!
ping -c 4 $(mysql -u frodo -p keepyoursecrets -D /home/pingtargets.db -se "SELECT ip FROM servers ORDER BY RAND() LIMIT 1;")
ping 1.1
also works. It resolves to 1.0.0.1, which is Cloudflare's secondary DNS
Oh shit. Didn't know this either. Kind of like ipv6 in a way
IPv4 has some other features too.
$ ping 0x8.02004010
PING 0x8.02004010 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=22.8 ms
That'll be Google's root DNS server, using hexadecimal and octal representations.
Wow, thank you!
It sure is better then ping 194.204.152.34
which I used to use.
Prior to cloud flare and Google doing DNS, a common one was 4.2.2.2 which is a level 3 IP.
Okay, I'm learning networking but have no idea what this means
interesting . . In my head, I think of ip addresses like just decimal values or integers separated by periods, but clearly a decimal value isn't processed as such by a computer. To think that IP addresses are simply strings is pretty interesting to my amateur mind, because for all my life I thought of them as technical computer jargon that isn't the same as what I used to think strings were: words!
I don't want to go so far as to tell you how to think, but as long as we are talking about how to visualize IP addresses, you may want to check out subnets and subnet masking.
The notation of IP addresses starts to make sense when you think about the early days of TCP/IP when all IP addresses were public and NAT'ing wasn't really required yet. Basically, there needed to be ways for networks to filter traffic by IP blocks that were applicable. (It was [in part] a precursor to collision avoidance, but absolutely not the full story.) We still use addressing and masking today, but it's more obvious when it's local. (Like in data centers, where it's super practical to mask off a block of addresses for a row or rack of servers.)
To your point, yeah. IP addresses are probably more comparable to the Dewey Decimal System rather than actual numbers and thinking of them as strings is probably easier.
Oh no worries, I am writing a Cisco networking exam in about a month, so I've actually studied subnets and addressing a good amount, but I don't mind the refresher!
I was just speaking more generally, in terms of programming, where integers and strings are different data types, yet you can store numbers as a string, which I always found interesting.
Or, if you're me,
$ ping 16843009
PING 16843009 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=4.06 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=53 time=4.04 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=53 time=4.05 ms ^C
***
16843009 ping statistics
***
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 4.044/4.053/4.062/0.007 ms