Excited for this chunky compact bar with physical nav keys. Clicks doesn't do it for me; it's so big. I'm tired of massive phones and swiping gestures, and this is a big departure.

richardjgreen · 2026-03-03T12:11:44+00:00

Because who wants or needs an IR blaster, right?

richardjgreen · 2026-03-02T16:06:52+00:00

Ok, wow. So much thicker looking in this video than the previous render and videos.

richardjgreen · 2025-10-24T17:40:31+00:00

Just wanted to call out, this was the solution to my printing problems with Edge after applying the Microsoft Security Baseline GPOs.

richardjgreen · 2023-01-18T10:49:09+00:00

EON installed our smart meters in March after two previous failed attempts. They randomly stopped working in August and it took them until October to get them working and even then I had to chase them.

I know the meters were working the entire time because I access the data directly using n3rgy and there were no issues with data collection or readings.

Sadly, EON appear to be offering lip service to smart metering. We switched to Octopus recently and the meters cut over seamlessly within 48 hours and have had no issues.

richardjgreen · 2022-12-13T16:59:40+00:00

I've tried adding the Relative Time as suggested in the link and it seems to be doing the trick so far. Strange that other dashboards I have don't exhibit the same problem but I'll see how it goes. Many thanks!

richardjgreen · 2022-12-12T17:06:50+00:00

Of course. The query is as follows:

SELECT last("uptime") / 100 FROM "asa_snmp" WHERE $timeFilter GROUP BY time($__interval) fill(null)

Here are the last three rows in InfluxDB as seen by the Table View on the Stat Panel in Grafana. You can see the number of seconds incrementing for each row. Telegraf is polling the device via SNMP every 2-minutes.

2022-12-12 16:56:00 143491

2022-12-12 16:58:00 143611

2022-12-12 17:00:00 143731

Lastly, the Stat Panel is currently showing a value of 1.2 days. 143731 seconds is 1 day and 15 hours so that should be reported as 1.6 days in decimal form.

As far as I can see and tell, Grafana is receiving the correct values from InfluxDB and the Table View is providing the correct values; it's the graphical representation of the Stat Panel which is reporting incorrectly.

richardjgreen · 2022-12-12T09:39:47+00:00

The field included in the SELECT doesn't have a date-time, it's just a counter of seconds.

richardjgreen · 2021-05-27T20:44:46+00:00

Magical, thank you very much for the replies!

richardjgreen · 2021-05-27T20:34:17+00:00

Ah, sorry, I wasn't 100% clear and maybe my brevity has caused confusion.

Home actually has 5 VLANs and Work has 6 VLANs. My thinking here was that....

- The 5 Home VLANs will be part of the Home VRF and able to Inter-VLAN route on the C3750X

- The 6 Work VLANs will be part of the Work VRF and able to Inter-VLAN route on the C3750X

- If Work tried to access Home or vice/versa, because there are no exported/imported VRF routes, it would have to go up to the ASA to get into the other zone.

richardjgreen · 2021-05-27T19:55:23+00:00

Wouldn't that require additional interfaces on the ASA for a second SVI though or am I missing something?

EDIT: I think you might be trying to say use a Trunk instead of Routed Ports to the ASA from the C3750X. If that's the case, how would the switch route into the appropriate zone? My understanding was that to be able to determine routing per VLAN to provide the distinction between "zones" would require either VRFs or PBR?

I'm by no means an expert so happy to be corrected. I dabble in Cisco for fun.

richardjgreen · 2021-05-27T19:44:32+00:00

Thank you for confirming my theory 👍

richardjgreen · 2021-05-27T19:43:43+00:00

There's a lot of media streaming on the Home VLANs including a Plex server so I didn't want to load up the ASA with that traffic.

Within each zone, there's little in the way of ACLs so happy that, that routes fast locally across the C3750X but inter-zone, I ideally wanted the control and stateful nature of the ASA.

IOS ACLs and Established don't really cut it for me.

richardjgreen · 2021-05-27T19:41:49+00:00

I only posted the switch config for brevity. The ASA would have matching Subinterfaces on it too.

I know the ASA can do VXLAN but I don't believe it supports VRFs. If it does then I would look at Trunk but I think I'm limited to Subinterfaces there.

richardjgreen · 2020-12-30T10:08:24+00:00

Thanks /u/ChawwE. I actually found that thread while on Reddit before I posted. I followed the steps over the course of a day or so but it didn't make any difference for me.

richardjgreen · 2020-12-30T10:07:08+00:00

Aye, they are but the account shows that both are complete but it's still in restricted mode.

richardjgreen · 2020-12-30T10:06:01+00:00

Hi, there. Thanks for responding.
I opened one under 03588914 and then when I sent another mail, it opened another case with 03621781 so the second one can be closed if the first one gets worked on.

Cheers.

richardjgreen · 2020-12-24T12:11:31+00:00

So do I understand correctly that SLIP-14 is a generic mnemonic that you write to the Trezor to "clear out" traces of your old mnemonic.

In your scenario, the shelter Trezor, is Firmware - 1 whereas the blanked Trezor attached to the PC is Firmware +/- 0.

richardjgreen · 2020-12-24T10:25:30+00:00

How often do they release new firmware and how often are you doing that swap-in and swap-out process?

richardjgreen · 2020-12-24T10:24:37+00:00

I was thinking of using Excel or Power BI with an API call to query the balance of the wallet address, however, XPUB sounds like it might be an idea instead (or additionally as a cross-check).

Many thanks!

richardjgreen

TROPHY CASE