Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › bgp.he.net updates
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

bgp.he.net updates

SwiftnodeSwiftnode Member, Host Rep
edited October 2023 in General

Looks like HE has rolled out some new updates to their bgp toolkit.

It has a handy traceroute tool that supports RIPE Atlas probes, PERFSonar probes, Globalping probes, and NLNOG rings. You can select an AS and traceroute/ping from them.

Not sure why they decided to center the content for searches though.

Thanked by 2host_c Calin

Comments

  • jimaekjimaek Member

    They added Globalping, nice :) Hopefully more similar websites will add us as well

    Thanked by 8iKeyZ 0xC7 BasToTheMax _MS_ fluffernutter MikePT PulsedMedia Ganonk
  • fiberstatefiberstate Member, Patron Provider

    HE is run by engineers that have no design aesthetic. Their site is from 1996 and has stayed that way since, It's what you want from a global IP backbone provider. :*

    Thanked by 2SirFoxy Calin
  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @fiberstate said:
    HE is run by engineers that have no design aesthetic. Their site is from 1996 and has stayed that way since, It's what you want from a global IP backbone provider. :*

    They need to restore it to the previous left aligned. This 'flex' style or whatever is terrible.

    Francisco

    Thanked by 3fiberstate MannDude let_rocks
  • fiberstatefiberstate Member, Patron Provider
    edited October 2023

    @Francisco said:

    @fiberstate said:
    HE is run by engineers that have no design aesthetic. Their site is from 1996 and has stayed that way since, It's what you want from a global IP backbone provider. :*

    They need to restore it to the previous left aligned. This 'flex' style or whatever is terrible.

    Francisco

    Adding one new feature shifted the entire page

  • JasonMJasonM Member

    hard to view on mobile screen!!! >:)

    Thanked by 2tentor jimaek
  • MikePTMikePT Moderator, Patron Provider, Veteran

    @jimaek said:
    They added Globalping, nice :) Hopefully more similar websites will add us as well

    Love it. Our probe is rocking 👌

    Thanked by 1jimaek
  • Daniel15Daniel15 Veteran
    edited October 2023

    @jimaek said:
    They added Globalping, nice :) Hopefully more similar websites will add us as well

    I was going to test my Globalping probe on the HE site (it's the only Globalping probe on AS46375) but it's not appearing on the HE site nor the Globalping site even though I still have it plugged in and turned on. I need to figure out why it's gone.

  • doghouchdoghouch Member
    edited October 2023

    @Daniel15 said:

    @jimaek said:
    They added Globalping, nice :) Hopefully more similar websites will add us as well

    I was going to test my Globalping probe on the HE site (it's the only Globalping probe on AS46375) but it's not appearing on the HE site nor the Globalping site even though I still have it plugged in and turned on. I need to figure out why it's gone.

    Likewise. I have mine plugged in and haven't touched the VLAN it's on since I got it. Hasn't shown up on GlobalPing for a while now.

    It appears to be online (I'll try SSH'ing into logs@[probe] later), so idk?

    Edit #2: Can't seem to SSH in. Power cycled it and still nothing - maybe the SD card is toast? Time to check!

  • jimaekjimaek Member

    Please don't use he.net to debug your probes :) I don't know how they build those lists and they also probably cache them making them unreliable.

    The best way is to check your logs. You can also try and find your probe here https://api.globalping.io/demo/ based on your city and asn. That list is actually real time.

  • doghouchdoghouch Member

    @jimaek said:
    Please don't use he.net to debug your probes :) I don't know how they build those lists and they also probably cache them making them unreliable.

    The best way is to check your logs. You can also try and find your probe here https://api.globalping.io/demo/ based on your city and asn. That list is actually real time.

    I checked the API demo page for the probe list earlier -- not quite sure what's gone wrong with mine.

    Even when I put it on a completely open network (i.e. no VLAN, no firewall restrictions), I can't seem to SSH into logs@[probe_dhcp_ip]. Given that it is able to request an IP from a DHCP server still, I'm inclined to say that it's not a SD card issue, but maybe a USB brick issue (I'm using a 4-port charger to run this and a RPi 3B as well).

  • GSBRTGSBRT Member, Patron Provider

    I miss the old design...

  • Daniel15Daniel15 Veteran
    edited October 2023

    @jimaek said:
    Please don't use he.net to debug your probes :) I don't know how they build those lists and they also probably cache them making them unreliable.

    The best way is to check your logs. You can also try and find your probe here https://api.globalping.io/demo/ based on your city and asn. That list is actually real time.

    When I ssh to logs@ on mine, it says "Could not chdir to home directory /home/logs: No such file or directory" then shows a segfault:

    Could not chdir to home directory /home/logs: No such file or directory
unexpected fault address 0x281bf7c
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x2 addr=0x281bf7c pc=0x281bf7c]

goroutine 1 [running, locked to thread]:
runtime.throw(0x1b6c5c5, 0x5)
        /usr/lib/go/src/runtime/panic.go:1117 +0x60 fp=0x321f63c sp=0x321f628 pc=0x7e6a78
runtime.sigpanic()
        /usr/lib/go/src/runtime/signal_unix.go:741 +0x1d0 fp=0x321f654 sp=0x321f63c pc=0x8000f8
github.com/docker/cli/vendor/k8s.io/api/apps/v1.init.0()
        /home/compiler/globalping-hwprobe/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/docker-ce/20.10.8-ce+gitd24c6dc5cf5e68dfb30027b2db454099566a9b9e-r0/git/src/import/.gopath/src/github.com/docker/cli/vendor/k8s.io/api/apps/v1/generated.pb.go:835 +0x4ec fp=0x321f658 sp=0x321f658 pc=0x174490c
github.com/docker/cli/vendor/k8s.io/api/apps/v1.init.0()
        /home/compiler/globalping-hwprobe/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/docker-ce/20.10.8-ce+gitd24c6dc5cf5e68dfb30027b2db454099566a9b9e-r0/git/src/import/.gopath/src/github.com/docker/cli/vendor/k8s.io/api/apps/v1/generated.pb.go:835 +0x4ec fp=0x321f658 sp=0x321f658 pc=0x174490c
runtime.doInit(0x2c53490)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321f784 sp=0x321f658 pc=0x7f8fec
runtime.doInit(0x2c58ab0)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321f8b0 sp=0x321f784 pc=0x7f8fec
runtime.doInit(0x2c55688)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321f9dc sp=0x321f8b0 pc=0x7f8fec
runtime.doInit(0x2c58280)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321fb08 sp=0x321f9dc pc=0x7f8fec
runtime.doInit(0x2c59d98)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321fc34 sp=0x321fb08 pc=0x7f8fec
runtime.doInit(0x2c55420)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321fd60 sp=0x321fc34 pc=0x7f8fec
runtime.doInit(0x2c55af8)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321fe8c sp=0x321fd60 pc=0x7f8fec
runtime.doInit(0x2c550b0)
        /usr/lib/go/src/runtime/proc.go:6292 +0x50 fp=0x321ffb8 sp=0x321fe8c pc=0x7f8fec
runtime.main()
        /usr/lib/go/src/runtime/proc.go:208 +0x278 fp=0x321ffe4 sp=0x321ffb8 pc=0x7e978c
runtime.goexit()
        /usr/lib/go/src/runtime/asm_arm.s:841 +0x4 fp=0x321ffe4 sp=0x321ffe4 pc=0x81dcc0

goroutine 8 [chan receive]:
github.com/docker/cli/vendor/k8s.io/klog.(*loggingT).flushDaemon(0x2cbf958)
        /home/compiler/globalping-hwprobe/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/docker-ce/20.10.8-ce+gitd24c6dc5cf5e68dfb30027b2db454099566a9b9e-r0/git/src/import/.gopath/src/github.com/docker/cli/vendor/k8s.io/klog/klog.go:1010 +0x70
created by github.com/docker/cli/vendor/k8s.io/klog.init.0
        /home/compiler/globalping-hwprobe/poky/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/docker-ce/20.10.8-ce+gitd24c6dc5cf5e68dfb30027b2db454099566a9b9e-r0/git/src/import/.gopath/src/github.com/docker/cli/vendor/k8s.io/klog/klog.go:411 +0x13c
Connection to 10.30.2.2 closed.

    I rebooted it but it's still the same.

    Edit: Opened a GitHub issue since I guess that's a better place. https://github.com/jsdelivr/globalping-hwprobe/issues/26

    Thanked by 1jimaek
  • jimaekjimaek Member

    Everyone having issues please PM me or open a GitHub issue :)

    I will try to help debug and when possible to replace any broken hardware

Sign In or Register to comment.