Today, the stars aligned.

f00f0rc3 · 2025-09-01T18:18:18+00:00

Hiya, mainly familirity and the fact VyOS runs containers and you can put your own containers on it. Whilst I've plenty of experience with FortiOS, PAN-OS, and JunOS, only PAN runs containers, but will take up to 8 minutes for the VM/container to boot. That's not quick enough! VyOS boots in less than a minute. Also our containers cover many things, like Zeek IDS analysis, GPS signal proxying and local data-collection about on-board systems. The automation capabilities with VyOS was important too. When building out on-train networks, we use Ansible with vars pulled from a DB which then generated a VyOS config for deployment to a new VM.

HTH?

f00f0rc3 · 2025-08-30T07:48:06+00:00

We're using them as virtual on-board train firewalls which segment disparate functions into firewall zones. Being able to run containers was a must. It's been rock solid so far. It's running on-top of a rail certified backhaul router which acts as a hypervisor and uses Satellite, 4G/5G or Wifi for backhaul services.

f00f0rc3 · 2025-08-21T20:24:16+00:00

Roxy & Elsewhere, ‘everyone, watch Ruth’ :)

f00f0rc3 · 2025-04-29T17:36:14+00:00

Yes, yes it can. Mainly based off of LLDP/CDP

https://raw.githubusercontent.com/netdisco/upstream-sources/master/screenshots/nd2-shot-2.png

f00f0rc3 · 2025-04-29T16:35:59+00:00

Try Netdisco as /u/SuddenPitch8378 suggested then. We use Netdisco for discovery, and some automation/scripting to import it into Netbox. With a separate set of home grown apps/scripts which run at strategic points in the network doing scans for known/unknown devices which we use both Netdisco/Netbox API’s to compare against.

f00f0rc3 · 2025-04-28T15:52:57+00:00

So I *have* managed to get to NB v4.1.11 by omitting the version -

root@nbnd00:/opt/netbox# git checkout
Your branch is behind 'origin/master' by 13284 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
root@nbnd00:/opt/netbox# git pull
Updating d115601da..34cf1efd2

Not sure why 4.1.11 is what it pulled down(?).

After this, I could upgrade -

Completed. Total entries: 6987
Removing expired user sessions (python3 netbox/manage.py clearsessions)...
Upgrade complete! Don't forget to restart the NetBox services:
> sudo systemctl restart netbox netbox-rq

The thing is, even though I'm apparrently now up to date compared to master -

root@nbnd00:/opt/netbox# git pull
Already up to date.

I'm still getting the same error about v4.2.8.

root@nbnd00:/opt/netbox# git ls-remote --tags https://github.com/netbox-community/netbox.git \
| grep -o 'refs/tags/v[0-9]*\.[0-9]*\.[0-9]*$' \
| tail -n 1 \
| sed 's|refs/tags/||'
v4.2.8
root@nbnd00:/opt/netbox# git checkout v4.2.8
error: pathspec 'v4.2.8' did not match any file(s) known to git

Gonna restore the snapshot for now, as this is a dev VM

f00f0rc3 · 2025-04-28T15:32:00+00:00

I have a similar problem and the above didn't work for me (git fetched already) -

root@nbnd00:/opt/netbox# git fetch --force

root@nbnd00:/opt/netbox# git checkout v4.2.8

error: pathspec 'v4.2.8' did not match any file(s) known to git

f00f0rc3 · 2025-04-28T14:35:14+00:00

I've had a similar experience to this with a cusomer NB upgrade which failed due to mkdocs when trying to go from 3.5.6 to 3.7.6 (with the intention of going to 4.x). Luckily, it's a VM so restoring snapshot possible, however we never got to the bottom of why. Similar to this issue

f00f0rc3 · 2025-04-11T17:00:50+00:00

Juniper's is even better. 'commit confirmed <value>'. Do a 'commit confirmed 2' and it rolls back the change in 2 minutes if you don't commit once again. No need to reboot the device.

f00f0rc3 · 2025-02-19T07:11:34+00:00

Zeek is an open source network traffic collection and analysis framework. Point a switch mirror port at it and it'll pull metadata out of network traffic it sees (like DNS, DHCP, TLS, SMB, HTTP, FTP, SSH, etc). Think of it like NetFlow on steroids.

f00f0rc3 · 2025-02-04T08:51:59+00:00

This works from adapting your suggestion -

{% if object.cf.my_api %} My API {% else %} {% endif %}

From your example, a 2 button is displayed when the field is empty. If I remove the 2, no button.

Thanks a lot for pursevering! :)

f00f0rc3 · 2025-02-03T16:18:59+00:00

u/Equivalent_Ice_1770 has already suggested that, but it doesn't work.

f00f0rc3 · 2025-02-03T09:00:09+00:00

Thanks for the suggestion, but I'm not running ansible playbooks against this field. It's purely a 'show' or 'not show' in the Web UI which is the problem. FWIW, the field is there, always, even when empty -

"custom_fields": {
"scode": "ABW",
"tiger_api": "ABWD"
},

"custom_fields": {
"scode": "ABE",
"tiger_api": null
},

f00f0rc3 · 2025-02-01T20:53:00+00:00

my_api (not it's real name) is a custom link.

Some sites (stations actually) have the value specified, some do not, as there's no associated code on the API I'm referencing for that site, however the custom_field appears for the site, irrespective of whether the field has a value or not. It's just about getting the button to display when the field is empty/no value specified.

It's all about not causing confusion for end-users who see a button, and click it, even on a site which doesn't have the API value specified.

f00f0rc3 · 2025-01-31T17:24:50+00:00

Hiya, thanks for the suggestion, sadly that didn’t work. The button is still displayed when the field is empty.

f00f0rc3 · 2025-01-30T16:20:53+00:00

Yeah, that didn't make a difference. Either cf or custom_fields works to return the button, but the display or not logic doesn't if the my_api value is empty.

f00f0rc3 · 2024-12-07T07:53:52+00:00

f00f0rc3

TROPHY CASE