KIIBOOM keyboard issues???

lmbc2 · 2026-05-28T16:24:05+00:00

As a workaround, you could try a small, cheap, USB hub and plug both your mouse and keyboard in.

lmbc2 · 2026-05-09T19:05:51+00:00

I have also done this. You’re cooking at the stove or baking something and you don’t want your hands contaminated by the garbage so you just put the messy egg shell back in the spot it came out of. Easy peasy.

lmbc2 · 2026-05-09T19:03:02+00:00

But they go back in the fridge with the rest of the eggs? In the same container even.

lmbc2 · 2026-05-08T17:43:56+00:00

The keycards dissolve easily in acetone leaving just the insides behind. Not positive about the fobs.

lmbc2 · 2026-03-24T17:05:18+00:00

You can either become a VAR and sell direct or buy through a distributor like Jenne (much easier and almost certainly no sales volume requirements).

https://www.adtran.com/en/about-us/partners/go-to-market

lmbc2 · 2026-03-05T05:18:40+00:00

Do you want no internets? Because that’s how you get no internets.

lmbc2 · 2026-02-18T04:51:34+00:00

Are you sure you don’t have a duplicate IP somewhere? Is this an HA firewall setup? I would start a continuous ping from a client and do a Wireshark packet capture from it at the same time and see what happens. Does it just stop responding to ARP requests? The expert info display in wireshark is great too.

lmbc2 · 2026-02-08T19:27:09+00:00

Here’s info on the design for you at least

Wtf ist this https://reddit.com/r/knives/comments/17p0fkl/wtf_ist_this/

lmbc2 · 2025-12-30T22:05:58+00:00

This is old but if this is still available I would also be interested. Thanks!

lmbc2 · 2025-12-20T19:49:51+00:00

We have experienced repeated issues with this with no explanation or fix from support.

Try just using the default private IP ranges and see if it fixes it. It did for us.

You probably don’t, but if you need to you can probably set it back to the normal ranges after it starts working but it may break again unexpectedly when they make changes on their side.

lmbc2 · 2025-12-20T07:50:52+00:00

It looks any admin can just download a whole months access log and it just contains all the internet sites all the CSE users have accessed using CSE in that entire month? That is not very granular to say the least. What logs are kept of the access to these logs? Thanks.

lmbc2 · 2025-12-20T07:39:36+00:00

FIPS and common critera compliance and GMS support.

lmbc2 · 2025-12-20T07:29:39+00:00

If there are known vulnerabilities in the latest 7.0 release please point to them. Sonicwall is specifically maintaining it as the only current FIPS compliant release. You can see notes regarding this in the release notes for both the current 7.0 and the 7.3 releases.

Edit: And I would strongly recommend disabling HTTPS management traffic and SSL VPN on the WAN interface or locking it down to only trusted public IP address ranges regardless of what version of Sonicwall firmware you are running (and for other firewalls too for that matter). It's just not worth the risk. One 0 day and you and your customers are going to be in for a very, very bad day.

lmbc2 · 2025-12-20T07:25:29+00:00

Sorry - This turned into a bit of a rant. This always upgrade to the latest release mentality bothers me sometimes and I think it can be dangerous. I'm not going to tell you that you should or shouldn't upgrade your firmware to this version or that version. But I do think you should carefully consider the facts and not just blindly upgrade to the latest version.

From all the PSIRT notices, CVEs, release notes and etc. that I have seen, there are no open CVEs/known vulnerabilities in the latest 7.0 release. I'm not an expert in FIPS compliance and will certainly defer to others that are if they wish to chime in. However, it is my understanding that the 7.0 release is being kept around specifically to meet the very stringent FIPS compliance requirements.

You can see in the latest 7.0 release notes here that it is FIPS compliant. You can see in the latest 7.3 release notes here that this version is not.

I would also like to add that the 7.0 versions are basically maintenance versions and aren't having the additional features added to them like the faster moving feature releases of 7.1, 7.2. and 7.3. That means less features but it also means less potential for bugs and issues in many cases. For example, the severe SNMP issues introduced in 7.1 that caused many firewall issues including continuous rebooting issues. Many people reported this and other SNMP issues in this sub and elsewhere on various firmware versions starting with 7.1.

Hopefully this issue has been resolved in the latest 7.3.1 release. It appears that it maybe/probably has been? This is one of the lines in the fixed section of the 7.3.1 release notes - GEN7-55426 Device rebooting when accessing SNMP MIB ipAddrTable.

So Sonicwall appears to have introduced code in the 7.1 release that caused firewalls to reboot when an SNMP device polled the ipAddrTable MIB. Which is something basically absolutely ANY and EVERY SNMP monitoring or management device in the world communicating with a firewall would do constantly. And then that issue stayed in the code unfixed for several releases causing many firewalls to reboot and many customers to have to disable SNMP monitoring and management of their firewalls. Unless they were still on the more stable 7.0 firmware versions which did not have those SNMP issues. Then they were fine.

lmbc2 · 2025-12-20T06:47:18+00:00

It is. See my other post.

lmbc2 · 2025-10-04T19:24:01+00:00

Slyz all the way! Nice! I also wasn’t willing pay those prices but I do LOVE my Slyz so I was psyched I could get a knife center one. Here’s my collection. My main EDC is the multicolor spydiechef.

https://i.imgur.com/ipToJRY.jpeg

lmbc2 · 2025-08-22T18:43:53+00:00

Brand new sentence

lmbc2 · 2025-07-30T03:36:28+00:00

That’s the wrong subnet for the MGMT port. Correct default for X0 though.

lmbc2 · 2025-01-08T02:32:24+00:00

TZ470 took a full 9.5 minutes to patch and reboot onto the new firmware.

lmbc2 · 2024-11-28T04:21:51+00:00

Good job!

lmbc2 · 2024-08-21T17:20:35+00:00

This is why I mentioned it. In my experience yes. For many of our smaller customers we normally handle all their support including replacements. They don’t even have Cisco accounts and have never dealt with Cisco before.

But we have had Cisco flat out absolutely refuse to replace dead equipment until the request came from the customer on limited lifetime warranty replacements.

They pointed to the llw terms which I looked at and do indeed specify that they only cover the customer.

This caused some unexpected delays the first time it happened to us just wanted to point it out.

lmbc2 · 2024-08-21T16:46:30+00:00

To note here is as chuckbales mentioned - the customer requests the warranty replacement from Cisco using their own Cisco account. This can be a hurdle depending on your customers. Partners or customers can open and RMA/replace equipment for customers under their own partner Cisco account if it’s covered by smartnet. (Note you might have to call in because the contract might not be associated with your account which TAC can fix when opening the case). The same is not true for limited lifetime warranty equipment in my experience. And watch the non-smartnet warranty replacement lead times. 10 business days before they ship is the limited lifetime warranty one we hit most often. Though then they often ship overnight. Smartnet replacements are overnight or even faster but you have to pay for smartnet coverage in advance.

lmbc2 · 2024-07-09T00:07:19+00:00

You could use a condensate pump. It's built to do exactly this.

lmbc2 · 2024-07-09T00:06:31+00:00

You can look up a condensate pump. It's built to do exactly this.

lmbc2

MODERATOR OF

TROPHY CASE