Re: FreeBSD's ping Integrates IPv6
On 7/5/21 16:19, Saku Ytti wrote: EVO doesn't have a hypervisor, just flat linux. It is very different to classic Junos under the hood. All modern classic Junos boot Linux but run Freebsd in KVM, but it's the same architecture as Junos always. Yes, this bit I'm aware of, which is why I was asking if it was Evolved, because despite booting Linux to launch a FreeBSD VM, the userland would still be FreeBSD. Mark.
Re: FreeBSD's ping Integrates IPv6
On Mon, 5 Jul 2021 at 17:15, Mark Tinka wrote: > > Some Juniper gear is Linux hypervisor :-) > > Isn't this that Junos Evolved thing? Never played with it :-). EVO doesn't have a hypervisor, just flat linux. It is very different to classic Junos under the hood. All modern classic Junos boot Linux but run Freebsd in KVM, but it's the same architecture as Junos always. -- ++ytti
Re: FreeBSD's ping Integrates IPv6
On 7/5/21 12:54, Baldur Norddahl wrote: Some Juniper gear is Linux hypervisor :-) Isn't this that Junos Evolved thing? Never played with it :-). Cisco's "ping" did not need a protocol option before they even had a Linux underbelly :-). lg-01-jnb.za>ping yahoo.com Translating "yahoo.com"...domain server (2C0F:FEB0::2) [OK] Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:4998:24:120D::1:0, timeout is 2 seconds: ! Success rate is 100 percent (5/5), round-trip min/avg/max = 300/303/304 ms lg-01-jnb.za> lg-01-jnb.za>sh ver | i Cisco Cisco IOS Software, 7200 Software (C7200P-ADVENTERPRISEK9-M), Version 15.2(4)S7, RELEASE SOFTWARE (fc4) Copyright (c) 1986-2015 by Cisco Systems, Inc. BOOTLDR: Cisco IOS Software, 7200 Software (C7200P-BOOT-M), Version 12.4(15)T10, RELEASE SOFTWARE (fc3) use. Delivery of Cisco cryptographic products does not imply A summary of U.S. laws governing Cisco cryptographic products may be found at: Cisco 7201 (c7201) processor (revision B) with 1966080K/65536K bytes of memory. lg-01-jnb.za> Juniper have also supported "ping" with no options for a while now. I can't remember a time when it wasn't the case, but I've only been running Junos since release 8.x. That said, since Junos 17.4R1, hardware-based platforms (including vMX and vSRX) have been on FreeBSD-11, which I believe defaults "ping" to IPv4 without the Juniper modifications. Mark.
Re: FreeBSD's ping Integrates IPv6
søn. 4. jul. 2021 12.45 skrev Mark Tinka : > > > On 7/4/21 05:51, Owen DeLong wrote: > > > Linux did this quite some time ago. I guess BSD is just now catching up. > > Been nearly 14 years since I last operated a Linux machine. > Some Juniper gear is Linux hypervisor :-)
Re: FreeBSD's ping Integrates IPv6
On 7/4/21 19:25, John Levine wrote: I've run it on an android phone. I have not... and I am sure of that, despite all the wine I drink :-). Mark.
Re: FreeBSD's ping Integrates IPv6
It appears that Mark Tinka said: > > >On 7/4/21 17:42, Justin Streiner wrote: > >> I think he meant that the underlying OS on lots of network gear is >> either some variant of Linux or BSD. > >I know what he meant... > >I've never ran "ping" on a TV or fingerprint scanner... I've run it on an android phone. R's, John
Re: FreeBSD's ping Integrates IPv6
On 7/4/21 17:42, Justin Streiner wrote: I think he meant that the underlying OS on lots of network gear is either some variant of Linux or BSD. I know what he meant... I've never ran "ping" on a TV or fingerprint scanner... Mark.
Re: FreeBSD's ping Integrates IPv6
I think he meant that the underlying OS on lots of network gear is either some variant of Linux or BSD. Thank you jms On Sun, Jul 4, 2021, 11:40 Mark Tinka wrote: > > > On 7/4/21 17:15, Bjørn Mork wrote: > > > I seriously doubt that. You're just not aware of it. > > I think I'd know if I've run "ping" on a box. > > Mark. >
Re: FreeBSD's ping Integrates IPv6
On 7/4/21 17:15, Bjørn Mork wrote: I seriously doubt that. You're just not aware of it. I think I'd know if I've run "ping" on a box. Mark.
Re: FreeBSD's ping Integrates IPv6
Mark Tinka writes: > Been nearly 14 years since I last operated a Linux machine. I seriously doubt that. You're just not aware of it. Bjørn
Re: FreeBSD's ping Integrates IPv6
On 7/4/21 05:51, Owen DeLong wrote: Linux did this quite some time ago. I guess BSD is just now catching up. Been nearly 14 years since I last operated a Linux machine. Mark.
Re: FreeBSD's ping Integrates IPv6
Linux did this quite some time ago. I guess BSD is just now catching up. Owen > On Jul 2, 2021, at 7:30 AM, Mark Tinka wrote: > > > > On 7/2/21 16:22, Niels Bakker wrote: > >> >> Yes, this broke some of my home network monitoring. Sadly there is no >> 'ping4' in the system, you have to add -4 to the commandline to return to >> the common BSD behaviour. > > This is a good point, as it's the same reason I discovered this today. A > transient IPv6 issue on a specific host broke NTP, and when I tried to ping > the NTP time servers during troubleshooting, it hang for a while because IPv6 > was broken. > > Mark.
Re: FreeBSD's ping Integrates IPv6
On 7/3/21 02:04, Thomas Fragstein wrote: Hi Mark, I think its time to make this switch. So one argument is that when I use the default ping (or other tools) it should be handle the actual protocol version in default. So IPv6 is the actual ip protocol version :) I don't mind it. I was just surprised by it. Which also speaks to what Randy and others have said... it could break tooling if folk aren't aware. Not a drama; can be fixed. Mark.
Re: FreeBSD's ping Integrates IPv6
I just noticed (although it appears to have come in version 13.0) that FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6: * ra...@psg.com (Randy Bush) [Fri 02 Jul 2021, 18:48 CEST]: pola breakage. especially fun if you have tools which run on both sides of the koolaid. On the one hand, yes. On the other hand, Linux had already made this change for ping specifically. Almost all other tools you'd use regularly are dual-stack by default that follow what's configured for the system to prefer (for FreeBSD that's ip6addrctl_policy): tools like telnet, ssh, mtr all follow the system default with -4 and -6 command-line options to override the default if situationally needed. ping and traceroute were the only odd ones out, and now only traceroute is. I think this was an unavoidable change worth the temporary discomfort while tools using these tools are adjusted. -- Niels.
Re: FreeBSD's ping Integrates IPv6
> I just noticed (although it appears to have come in version 13.0) that > FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6: pola breakage. especially fun if you have tools which run on both sides of the koolaid. randy --- ra...@psg.com `gpg --locate-external-keys --auto-key-locate wkd ra...@psg.com` signatures are back, thanks to dmarc header butchery
Re: FreeBSD's ping Integrates IPv6
On 7/2/21 16:12, Patrick Cole wrote: Mark, iputils-ping on linux seems to behave the same for quite some time... [z@tyl][~] % host ns0 ns0.spirit.net.au has address 27.113.240.197 ns0.spirit.net.au has IPv6 address 2403:3600:8002::100 [z@tyl][~] % ping ns0 PING ns0(2403:3600:8002::100 (2403:3600:8002::100)) 56 data bytes 64 bytes from 2403:3600:8002::100 (2403:3600:8002::100): icmp_seq=1 ttl=63 time=0.344 ms 64 bytes from 2403:3600:8002::100 (2403:3600:8002::100): icmp_seq=2 ttl=63 time=0.447 ms Thanks for the feedback, Patrick. This is great! This led me to test the same on the family Windows 10 (21H1 version) machine, and Microsoft are doing the same, which is great to see. Mark.
Re: FreeBSD's ping Integrates IPv6
On 7/2/21 16:22, Niels Bakker wrote: Yes, this broke some of my home network monitoring. Sadly there is no 'ping4' in the system, you have to add -4 to the commandline to return to the common BSD behaviour. This is a good point, as it's the same reason I discovered this today. A transient IPv6 issue on a specific host broke NTP, and when I tried to ping the NTP time servers during troubleshooting, it hang for a while because IPv6 was broken. Mark.
Re: FreeBSD's ping Integrates IPv6
* mark@tinka.africa (Mark Tinka) [Fri 02 Jul 2021, 16:02 CEST]: I just noticed (although it appears to have come in version 13.0) that FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6: Yes, this broke some of my home network monitoring. Sadly there is no 'ping4' in the system, you have to add -4 to the commandline to return to the common BSD behaviour. -- Niels.
Re: FreeBSD's ping Integrates IPv6
Mark, iputils-ping on linux seems to behave the same for quite some time... [z@tyl][~] % host ns0 ns0.spirit.net.au has address 27.113.240.197 ns0.spirit.net.au has IPv6 address 2403:3600:8002::100 [z@tyl][~] % ping ns0 PING ns0(2403:3600:8002::100 (2403:3600:8002::100)) 56 data bytes 64 bytes from 2403:3600:8002::100 (2403:3600:8002::100): icmp_seq=1 ttl=63 time=0.344 ms 64 bytes from 2403:3600:8002::100 (2403:3600:8002::100): icmp_seq=2 ttl=63 time=0.447 ms -PC Fri, Jul 02, 2021 at 04:00:16PM +0200, Mark Tinka wrote: >Hi all. > >I just noticed (although it appears to have come in version 13.0) that >FreeBSD's "ping" app now defaults to IPv6, i.e., no need for ping6: > > https://www.freebsd.org/cgi/man.cgi?query=ping=8=html > >Does anyone know whether other *nix systems are doing this now? > >My Mac (Catalina) still requires ping6, and I don't have any recent Linux >systems handy. > >#ThisIsGood > >Mark. -- Patrick Cole Chief Architect Spirit Technology Solutions 19-25 Raglan St, South Melbourne VIC 3205 Desk:0385541391 Mobile: 0410626630
