Not sure if it was a software update the week or just a thing that sometimes happens. But the air-conditioning was on. I dont use the air-conditioning, but one other person who hates the air-conditioning, rather irrationally, accused me of turning it on. Does it ever turn on on its own?
I plugged into a believe point via zapmap last night for 2 hours. it took the £30 hold 3 times over. 3 times! I'm perplexed now, how on earth did my bank not notice this happening, the entire banking system in the UK is just pants, but that's another issue altogether. This morning, the hold has still not been reversed, and Zapmap only work weekdays. So I figure, I'm £90 in I may as well charge the car the rest of the way in the morning before I go on the long trip - I only use a slow charger at home you see. I plug in, I tap the RFID card from zapmap and my bank instantly pings me a 4th hold has been taken. I'm apoplectic with disbelief now, as a software engineer myself I'm really trying to figure out what kind of people work at that place and how on earth do the banks not bar them from taking a hold. Oh yeah I forgot banking is broken, another topic. So this, error, means every time I tap my zapmap card I'm charged a hold again while I'm on holiday? That's just abelist thinking on the part of the software testers at zapmap or believe everyone has a spare £0 for every time they, oops, make a mistake in their platform. and no I do not care if the "oops" is a bad internet connection, that's never an excuse.
I'm finding it hard to believe that I'm the only person who this has happened to. I'm pretty sure that after 24 hours the hold on my card will be released. And no I do not want platitudes about a bank hold not being real money, it isif that's all you happen to have. It's a poor show. Mostly disappointed, that this kind of thing happens to me only ever when I go on my holidays, which is maybe 3 times a year. I have had the car 1 year and already had one hiccough in Norfolk on their network. If I used a public charger 3 times a week that would be a lot of support tickets raised. I understand that the problem is me making some mistake in how I use the system, and would actually stop happening if I was a frequent user. But all that tells me is that out-of-box-failure of poor first-time-user experiences are probably common. If nobody speaks, this will never be fixed.
/edit : Icing on the cake, after posting this, I unplugged my car and guess what happened? I now have 5 holds. This is not a thing you can make up.
This old thread seems to indicate that letting users of the platform create a draft and then resume working on it later, is not an ad revenue generator for Meta. So the feature seem to be hidden according to https://www.reddit.com/r/facebook/comments/yfqqfp/where_the_hell_do_i_find_post_drafts/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button . Is this still the case?
68 characters for a title stretched my focus muscle, sorry.
I'm a bit confused by the gaps in snmp documentation, for all languages and the entire stack itself, so I figured, hey Powershell will be easier than C++. But it seems it's just not. I read amongst others this posthttps://vwiki.co.uk/SNMP_and_PowerShell , and it's still clear as mud, how do docs for the "open" function
$SNMP.open($IPAddresses[1], "public", 2, 3000)
What on earth is 2 ?
3000 is as far I can figure a timeout, but where are the Powershell docs?
I call Get, and I just get an error
> $SNMP.Get(".1.3.6.1.2.1.2.1")
Unknown Error
At line:1 char:1
+ $SNMP.Get(".1.3.6.1.2.1.2.1")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [], COMException
+ FullyQualifiedErrorId : System.Runtime.InteropServices.COMException
I'm querying my local interface I assume, and it's all guesswork as to what that error means because I was expecting an interface ID back, a simple number?
I have been asked to measure network utilization when connected to various network devices running different versions of our app. Is there a way to automatically extract the throughput numbers somehow from a pcap log? Kind of like a speed test of sorts on a 2.5Gig LAN. My test is anything from 1 to 5 minutes long and I can run it multiple times in order to get good averages. I've only used Wireshark to troubleshoot, but it does draw a nice graph showing how much our app is able to shove down the network. I'm also assuming that I need to not capture the actual packets, not looked for any way how to do that either. I assume a pcap session will add CPU load and disk I/O overhead and skewing. I could run the capture on a separate host, but initially I would prefer a single-computer way to start and learn the basics.
I'm asking how easy this might be to do, because it feels like adding up all the packets in the log is one way, but not ideal for someone who almost flunked math anyway, to make mistakes and just omit one byte everywhere of overhead and then get a wildly wrong number. TCP only, no UDP. Where should I start? ATM I have this pcap file which I gathered using -a duration:300 -b duration:300 on commandline . I don't believe I need to filter it too much because it's a dedicated LAN, what tips do people have in terms of approach to automate gathering data points? I have seen many ideas from using a duckdb tool that opens the pcap file via python, to writing a dissector (I can write C code easily) but all feels like a lot of lifting if all I need is a very rough 1 second-granularity throughput graph. I do not need timing detail, just the time it took to push the data, which runs into many gigs, and to show roughly how many seconds before the protocol we use starts to block.
The real reason I am asking is that Windows perfmon (I'm trying to not limit this to Windows capture, because I have to support Ubuntu anyway) is NOT producing the same throughput as what our app is reporting for transmissions. (Perfmon also reports bytes not bits/sec, which is damn annoying) I'm aware that framing is an overhead, but am keen to learn what that overhead is, and how that varies for different workloads. Turnaround times are the thing I am trying to test for too. Like for smaller and larger DATA chunks. I clearly do need to learn how to calculate what the frame and packet overhead is too still. What kind of speed comparison things can I manipulate and extract via the tshark command-line? Or do I need/want to spend a day looking directly into the API, or dissectors, or other ways. What is most efficient for a simple speed graph?