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
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
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
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 :-)
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.
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
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.
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
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.
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
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.
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
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
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
> 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
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
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
* 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
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
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
20 matches
Mail list logo
