Philip Paeps writes:
>
> If someone does succeed in creating a port, I'd be happy to commit it to
> the FreeBSD ports tree.
>
I once started to do so, but nebver finished becuse $WORK started
to interfere so ran out of time. Maybe I should pick it up again.
jaap
--
ripe-atlas ma
Anand Buddhdev writes:
> ... So we
> decided to use UN Locodes, as we do with RIPE Atlas anchors. The UN
> Locode for Fremont is "us-fnc". Unfortunately, we used just the location
> part of it, and did not include the country code, so the bare "FNC"
> looks like an IATA code.
For detail
Robert Kisteleki writes:
> It's good to have your probe back! We have this entry in the FAQ for v3
> leds:
> https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-probe-mean
>
> - which may or may not be (or have been) helpful in your case.
As I complained, it doesn't
Philip Homburg writes:
> On 2022/01/18 10:35 , Jaap Akkerhuis wrote:
>
> The LEDs on V1 and V2 probes are regular ethernet activity LEDs. I think
> one is link status and the other activity, but I'm not completely sure.
There used to be a list of "the other activitie
There used to be information telleing what the lights mean. It seems
to be gone. After a lot of searching around one finds some information
about blinking orage lights but all leds in version 2 are green
colored so I guess this cvers V3 (or V1?) probes.
have probes V2 been abandoned by Ripe-Ncc?
"Philip Paeps" writes:
> It should be fairly straightforward to run the software probe on FreeBSD
> under the Linux binary compatibility layer ("Linux personality
> disorder"). I've been meaning to poke at this but so many projects ...
> so little time.
When the software probe projects s
Daniel Karrenberg writes:
> At this time are 485 connected probes and two connected anchors in
> Russia. As far as I know Soekris boxes can be bought in Russia.
And there are regularly atlas ambassadors in Russia. I returned
with 3 probes from ENOG-10 because I couldn't get rid of them.
