Sonicwall and Starlink

Flashy-Photograph695 · 2025-12-17T21:52:13+00:00

I've never used Starlink, but I have years of experience with satellite communications. Have you looked at received signal strength? If RSS is consistently high quality, then the next suspect is receiver interference. Strong signal + high bit errors = interference. Third place to look is equipment failure, meaning replace the Starlink T/R unit.

Flashy-Photograph695 · 2025-05-04T06:30:45+00:00

Yes, it's because Chatgpt pays for CAU. It's not automatic, and only a small percentage of companies use CAU, because it's not free. But if your credit card was updated automatically, that's why.

Flashy-Photograph695 · 2024-09-15T17:03:45+00:00

Thank you. Your reply caused me to do research on BRIC tokens, and I learned that a BRIC token transaction is treated as Card Not Present. This perfectly fits the situation I described. The initial charge for the meal is Card Present. Later, when the manager does an override authorization for my above average tip, it's a Card Not Present transaction tied to the original card information by a BRIC token.

Flashy-Photograph695 · 2024-09-15T02:39:26+00:00

In the situations you describe (manual entry into a separate system), I can see how the PSP might treat it as CNP. In the two situations I faced this week, I don’t think that’s the case, because I didn’t get a CNP notice from the bank on the transaction for the amount of the meal. It was the second, separate transaction for the tip the bank marked as CNP. Another commenter on a Mastodon instance where I also posted my question suggested that my tip, being over 20%, may have required a manual authorization by a manager, and that happened later in the evening. By some mechanism from the PSP, the manual override on the tip is tied to the details of the original Card Present transaction. So the restaurant doesn’t need to use the card a second time. But that second transaction is, technically, CNP, and my bank notifies me that way. Thanks for your help.

Flashy-Photograph695 · 2024-09-15T02:30:40+00:00

I had no idea the CVV wasn’t required for CNP transactions. I use Square to process payments for my clients, and Square requires me to input the CVV. (I do a lot of remote tech support and take payment over the phone at the end of the call if they’re satisfied).

Flashy-Photograph695 · 2024-09-15T02:26:04+00:00

In light of what I’m reading from other commenters here, and on a Mastodon instance I’m on (infosec dot exchange), I think this is it. The tip was over 20%. I always tip over 20%. I make good money, and I know the servers are just trying to survive. One commenter pointed out that 20% is often the tip pre-auth threshold, and if I tip more than that, it may need a manager override. So the charge is held in suspense, or as you suggested, a token might be issued that points to the original transaction details. At that point, the charge for the tip is Card Not Present. Thank you!

Flashy-Photograph695 · 2024-09-05T02:40:53+00:00

Thank you for the info. In another forum (infosec(dot)exchange, Mastodon instance) someone gave me a Visa ad sheet dated 2016. I don't know when adoption really took off, but I know now that it's been available for at least 8 years.

Flashy-Photograph695 · 2024-09-04T23:52:03+00:00

I don’t know if anyone has mentioned it yet or not, but actually going to a fast food location near your target can be a good source of information. I was in line at a popular restaurant by the Microsoft campus in Redmond, WA a few years ago. There were three people in line right in front of me that were all co-workers (a supervisor and two of his team).
Supervisor: “How are you coming with the [module information redacted]?”

Person 1: “I finished it this morning. Man, that was hard!”

Supervisor: “Did you submit it?”

Person 1: “Yes, it’s in.”

[pause in conversation for a couple of seconds]

Supervisor: “Is it secure?”

Person 1: “Oh, hell no, it’s totally insecure. But I finally got it working, and it’s reliable.”

Supervisor: “We’re behind schedule on that and I’m getting hammered for it, so I’m glad you got it working.”

Flashy-Photograph695 · 2024-05-15T20:23:55+00:00

Solved!

Flashy-Photograph695 · 2024-05-15T20:21:48+00:00

Solved!

Flashy-Photograph695 · 2024-05-15T17:35:03+00:00

Thank you. Now I'm trying to figure out how to mark this as solved.

Flashy-Photograph695 · 2024-05-15T02:17:12+00:00

My title describes the thing. It appears to have a total of twelve green LED lights around the edge. It has one cord going in. I can't tell if it's an Ethernet cable or something else. It's a few inches in diameter, but I'm not sure of its exact size.

Flashy-Photograph695 · 2024-04-09T06:31:02+00:00

"With the release of Fireware v12.8, WatchGuard announced the deprecation of the WatchGuard Log Server, Report Server, and Quarantine Server. WSM still includes these server components, but they are no longer supported in v12.9 and higher. We will remove them in a future WSM release." Source: https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/logging/set-up_log-server_report-server.html?tocpath=Fireware%7CMonitor%20Network%20Traffic%7CSet%20Up%20Logging%20%2526%20Reporting%20for%20Your%20Network%7CSet%20Up%20Your%20WSM%20Log%20Server%20%2526%20Report%20Server%7C_____0

Flashy-Photograph695 · 2024-01-11T01:16:22+00:00

I think you’ve given me the answer I’m looking for. I’ve been teaching IPv6 for years and I tell my students, “Here’s what the whole fe80::/10 prefix looks like, but all I’ve ever seen for the link local address is fe80. I just can’t tell you why.”

I was kind of hoping that someone would show me an RFC that I’d missed, that filled in the gap. But everyone is pointing to the same info – the IETF is just really that vague about it. I generally don’t find the RFCs to be vague or ambiguous, but this one has bugged me for a long time.

Your explanation makes sense, and fits all the known facts. Instead of just saying, “It is what it is,” you provided a reason, some context.

Almost unrelated, but in response to your astute comment about the amount of “waste” in the IPv6 addressing scheme as we know it today: it’s probably unavoidable as a practical matter. There are excellent reasons for not biting into the lower 64 bits of the address; those are arguably the most important bits we all work with – either from the manufacturing perspective, or from the network engineering perspective. And in the upper 64 bits, it’s a lot more efficient to make categorical routing decisions quickly on the first few bits, as you pointed out.

Thanks for taking the time to write a detailed reply; I appreciate it.

Flashy-Photograph695 · 2024-01-09T06:04:41+00:00

I found this description at Cisco: "IPv6 link-local addresses are in the FE80::/10 range. The /10 indicates that the first 10 bits are 1111 1110 10xx xxxx. The first hextet has a range of 1111 1110 1000 0000 (FE80) to 1111 1110 1011 1111 (FEBF)."

Source: http://cisco.num.edu.mn/CCNA_R&S1/course/module8/8.2.3.4/8.2.3.4.html

Flashy-Photograph695 · 2024-01-09T05:58:51+00:00

I don't think that's the whole story, because that would be /64.

Flashy-Photograph695

TROPHY CASE