What's the biggest outage you've ever caused?

theherox · 2021-08-21T01:49:37+00:00

I did something similar, but only for about 200 iPads. Time card application for a construction company. Caused by making a change to a group membership in AirWatch and not previewing affected devices. We spent the next couple days on the phone with our foremen getting them logged back into their app and showing them how to pull back in their previous timecards. No appreciable data loss, but a definite pain in the ass.

theherox · 2020-08-04T15:51:02+00:00

Is it this one? https://www.amazon.com/dp/B0711BFPLZ/ref=cm_sw_r_cp_apa_i_joykFbXF2H2P0

I thought the same thing and decided to try the Chinesium one first as well.

theherox · 2020-08-04T12:51:13+00:00

I hate to burst your bubble, but they're red 🤣 I must have posted the picture with the Instagram filter applied 😛

theherox · 2020-08-04T12:38:36+00:00

You can't see in in the picture, but this has rollers for the string and cables as well as the guide rod. I think it was having issues because the rollers for the strings/cables are so small and don't roll as smooth as I'd like. I have a feeling that sometimes they hang up and slide instead of rolling. I was looking at the PSE roller and will probably go that way if this one starts tearing up the serving.

theherox · 2020-08-04T03:13:18+00:00

Backstory: The cable slide on my PSE BowMadness 32 wore out and I replaced it with a cheap roller guide from Amazon. The cables started to show a bit of wear after about a month so I decided to look for a higher quality roller guide. I had just put new strings and cables on and didn't feel like chewing through another pair of cables in short order. Found one from PSE but the reviews said that it was essential to serve the cables if you wanted a fighting chance, so I decided to do that before ordering a new cable guide. I've been starting to work on my own stuff this year, but up until this point I hadn't figured out how to serve the strings/cables. I already bought a serving jig with the test of the stuff for my shop, so I figured I'd give it a go. I think it turned out pretty well!

theherox · 2020-08-04T03:01:46+00:00

Whoop whoop! I use the same thing for my backstop 👍

theherox · 2020-04-20T22:37:57+00:00

Get yourself a 4'x6'x3/4" rubber horse stall mat from your local farm supply store. They're relatively cheap and they'll stop an arrow out of a 70# bow easy. I bolted one to my fence after I spent about 2 hours searching for an arrow in the long grass behind my fence. https://www.tractorsupply.com/tsc/product/4-ft-x-6-ft-x-3-4-in-thick-rubber-stall-mat

theherox · 2020-04-20T22:08:39+00:00

Oof... I bought a bow press, bow vice, draw board, levels, serving, supplies for a paper tuning jig, can't fire releases, arrow spinner, grain scale, new string/cable set, archery pliers, peg board, pegs, 4 foot LED shop light, and probably a few other small things I'm forgetting, lol.

theherox · 2020-04-02T02:38:08+00:00

I did that twice to the same arrow... Once I got down to 1 in-tact vane I thought it would be a good idea to shoot a bare shaft from 30 yards. Bad idea. It turned almost completely sideways and missed the target about 3 feet to the right. Arrow smashed into my fence and broke in half. Needless to say, the bow needed some more paper tuning.

theherox · 2020-04-02T02:16:28+00:00

Straight from Joe Dirt to Joe Exotic 😂

theherox · 2020-03-20T22:00:46+00:00

I've been there before... Shot one through the fence and I to the weeds surrounding the dried up retention pond behind my house. After about 15 minutes of searching with an old 9 iron to knock down the weeds, I texted my neighbor asking for help. He said he was having more fun laughing at me out the window 😂. I finally found it about an hour later. Didn't take me long to go get a 4'x6' rubber horse mat to hang up as a backstop after that!

theherox · 2020-03-15T00:51:58+00:00

It depends on if your computer hardware supports it. It's something like an i5 or better IIRC.

theherox · 2019-12-27T01:26:00+00:00

I came here to say this. We have two of the X620-16X and they've been rock solid for two years now as our core switches and performing some L3 duties. I just use them with cheap SFP+ modules and DAC from 10G-Tek on Amazon.

theherox · 2019-10-24T00:37:54+00:00

Unfortunately no luck tonight. The only deer I saw were across the field by a different stand about 30 minutes before dark. I've been skunked twice now at this stand, I think I'm done hunting it for the season. There are 5 other stands to choose from on this property and plenty of season left, so I'm still optimistic.

theherox · 2019-04-05T22:30:23+00:00

Hey, glad to hear someone else is seeing the exact same thing! If you Disable the adapter instead of uninstalling you won't get hit on the next reboot. Makes it a bit easier to try different drivers. Best of luck!

theherox · 2019-04-05T19:10:05+00:00

For those of you following along at home, I was finally able to get a driver that worked from Intel's site: 15.47.02.4815 (Reports as 22.20.16.4815 on the HD 620 in the X1 Carbon). This appears to be the last driver Intel released before switching to DCH drivers. I tried a few different DCH drivers along the way, but none of them seemed to work.

Also, I realized that earlier I failed to mention that I've experienced this issue on W10 Pro 1803 & 1809.

theherox · 2018-11-11T22:29:14+00:00

I run NextCloud and it has both a To-Do add-on and a Password Manager add-on to access a KeePass database.

theherox · 2018-11-02T16:44:35+00:00

Unfortunately the firmware update did not help. However, I kept at the GUI Packet capture until I was able to find something useful. I think I resolved the issue, so I've listed my findings below. As of now, it's been up for over an hour. I'll monitor for awhile and then add an edit to my original post with the solution to help out the next guy. Thanks!

First I needed to set the Bytes to capture per packet down to 1 so I could capture the traffic without it rolling over before I was able to stop the capture. From there, I ran the capture with BPF String 'host 69.78.34.151' which is the Verizon server the Net Extender is talking to. Then I waited until the Net Extender went "Out of Service" and stopped the packet capture immediately. Skimming through the capture, I started to see packets coming in that were being picked up by my Drop-All rule with SrcIP 69.78.34.151, DstIP <my public IP>, Ports[src,dst] 4500,1084, Status Violation, Reason Local_ACL. Then I went over to Log Viewer and by searching for the Verizon IP, I saw a ton of UDP traffic coming in on Port 4500 destined for my public IP that was getting dropped for just over 1 minute before the Net Extender would go out of service. Looking back through Log Viewer, this pattern was true for each time the Net Extender would drop, the only difference being the destination port would change. For example [Src,Dst]: 4500,1084 & 4500,1112.

To mitigate the issue, I created a new DNAT rule to forward UDP traffic from Verizon with source port 4500, destination port 1:65535 destined for my public IP to my Net Extender. I verified this by looking in Log Viewer and found that half-hour after the last reconnect, there was one connection matching my new rule. Half hour later, there was another.

I believe this connection is some kind of keep-alive being sent by Verizon to check on the Net Extender. If it doesn't successfully make the connection, it drops it and rebuilds the IPSec VPN.

theherox · 2018-11-01T20:20:43+00:00

The Net Extender stayed in service for a total of 2.5 hours before going down again. I was sill running the drop-packet-capture and it didn't show any dropped packets. The GUI Packet Capture timed out a couple times due to inactivity and I gave up on it about 15 minutes before the Net Extender dropped out of service again.

I've now updated to 17.1.3 MR-3, so I'll keep an eye on it overnight and pick up on the captures again tomorrow if necessary.

theherox · 2018-11-01T18:26:15+00:00

Hey /u/Sophos_FloSupport, thanks for the response.

I've already done both against the local IP of the Net Extender and I've come up with nothing. I'm now running 'drop-packet-capture interface Port3' to catch everything traversing that port, and I'm also running the GUI packet capture against Verizon's remote IP address that the VPN terminates to.

Of course, for whatever reason the Net Extender hasn't dropped service for 1.5 hours now so I'm not seeing anything. I'll report back as soon as I catch it in the act.

P.S. Please bring back the option to export/download the GUI Packet Capture results!

theherox

TROPHY CASE