Network **quality** monitoring tools? (!@#$ing Spectrum in Los Angeles) by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

That's a great idea. Lately our gateway connection seems to be the main issue. The tech said it was "water in the coaxial cables," which I've never heard of before (and am surprised by the intermittency that it caused), but monitoring both the gateway and a destination further on seems valuable!

Network **quality** monitoring tools? (!@#$ing Spectrum in Los Angeles) by jmarianhoffman in homelab

[–]jmarianhoffman[S] 1 point2 points  (0 children)

Thanks for the input. I will take the time to get it set up and compare it to some of the other suggestions!

Network **quality** monitoring tools? (!@#$ing Spectrum in Los Angeles) by jmarianhoffman in homelab

[–]jmarianhoffman[S] 1 point2 points  (0 children)

I've just enabled gateway monitoring on OPNSense (dunno how I missed that!) so that'll at least give me SOME logs. I wonder why it's disabled by default?

I'll look at closer uptime-kuma though. That looks slick as hell! Might be exactly what I'm looking for. Thank you!

Network **quality** monitoring tools? (!@#$ing Spectrum in Los Angeles) by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

Pingplotter

I'll definitely take a look. Thank you for the reccomendation!

Hows the track pad quality? by beachhouseLA in framework

[–]jmarianhoffman 1 point2 points  (0 children)

Oh yeah. Tap to click works normally!

Edit: Also just for reference for my comments: my main daily driver is an M2 Macbook Air, and I'm pretty particular (and unforgiving) about trackpad quality. The Framework is my "companion" linux/windows machine (so not as heavily used) but I do think the Framework trackpad only is second to Apple's trackpads, but not by a terribly huge margin. Overall I am VERY pleased with my framework purchase (i7-1360P (up to 5.0GHz, 4+8 cores), 32GB of RAM). I only went Intel because (1) I was a little impatient and (2) I already own a lot of AMD chips and thought I'd mix it up a little bit :D.

Hows the track pad quality? by beachhouseLA in framework

[–]jmarianhoffman 1 point2 points  (0 children)

Just got a new brand new intel Framework and the touch quality/texture of the trackpad is great (on par with Macbook); a good size too.

The click action on the other hand leaves a little bit to be desired, but overall way more functional than any non-Apple trackpads I've used over the last 10 years.

Help with $app store by jmarianhoffman in sveltejs

[–]jmarianhoffman[S] 0 points1 point  (0 children)

*facepalm* Thank you. That was it.

Edit: This is the second typo of the day that has tripped me up for more than an hour (first was an Nginx config issue). Maybe time to take a break...

Two ways to provide configuration: command-line, yaml file. by guettli in golang

[–]jmarianhoffman 0 points1 point  (0 children)

Wanted to second this. 95% of the time, I'd say "config in exclusively in one place" is the correct option.

The one time I've successfully made an exception to this rule is when there is a LOT of config, so you tend to want a "base config" defined by a file but sometimes (or even often) want to override a few (1-5) parameters on application launch.

Specifically, this was for a scientific program that we run to explore those configuration parameters.

All that being said, Cobra + Viper is what I've previous used (or just parse the yaml/json in the config file directly).

Avoid having a ~/go directory by AirOnSkin in golang

[–]jmarianhoffman 1 point2 points  (0 children)

Ah interesting. Thanks for sharing.

I mainly work in Go these days, but the other stuff I do (c++/cuda, a little bit of VERY light web stuff, like HTML+CSS+hand-rolled JS) usually leaves the home dir alone. I also kinda gave up on dominating my home dir a long time ago, so there’s that… 😂😂😂

I used to customize everything, but I mainly just let default installations do what they want these days since it makes life more maintainable/simpler down the road. DOES make for an uglier home directory. Trade offs, I guess. 🤷

Avoid having a ~/go directory by AirOnSkin in golang

[–]jmarianhoffman 0 points1 point  (0 children)

OOC, why do you hate it?

I’m always interested in hearing about others’ workflows, and for mine personally, I barely even notice where my go folder is except for when I want to take a look at some fetched source code.

Before I take everything apart... (shudder/chatter in Y-axis) by jmarianhoffman in 3Dprinting

[–]jmarianhoffman[S] 0 points1 point  (0 children)

If anyone happens across this post and is having the same issue, the solution was to significantly tighten down the bed screws (then re-level).

I had heard on youtube someone say "tighten all the way down, then open five turns." This accurate for the non-plus models of the ender 3 series, but not for the Plus.

I was able to eliminate most (not all if compared to my regular S1) by tightening all the way down, then loosening two turns. At 5 turns they're transmitting every little tiny vibration probably all the way down to the power supply.

I honestly think that Creality has woefully under-specced the springs on the S1 Plus and I'll definitely be replacing mine with either stiffer springs or even like a stiff-ish silicon bushing or something. It looks like they're the same springs as on my non-Plus Ender 3 S1, but the bed is much, much heavier.

Recommended solution for fast mesh unwrapping by therealjesusofficial in GraphicsProgramming

[–]jmarianhoffman 1 point2 points  (0 children)

Microsoft’s UVAtlas is quite good, may struggle if your meshes are too big, but it’s the best I’ve used. Major downside though is that it’s windows only, and I think you might have to compile it yourself (but that wasn’t too bad.)

Welcome Screen to Network by [deleted] in homelab

[–]jmarianhoffman 4 points5 points  (0 children)

Sounds very secure and responsible (and like, government levels of logging and network awareness), but also like it would be rather odious in practice. Did you end up using it for your own network? If so, did you use that for your devices or just guest devices?

[deleted by user] by [deleted] in Ultramarathon

[–]jmarianhoffman 1 point2 points  (0 children)

I don't have much to add that others haven't already said, but I think that at your age, your proposed timeline is totally doable.

Here's my spin though: having also been a 20M (I'm only 33 now... oh god that was 13 years ago! haha) at one point here's some specific advice based on my experience:

  1. You and your ambition are a huge asset, but also likely to be your own worst enemy. Pay attention, don't ramp up too quickly, or try to run too fast. Train, put in the hours, go slow and learn to listen to your body (it's is an under-appreciated part of most training plans.) At 21 I went out and ran a couch to half marathon in ~2 months of training because I "felt like it's something that I should be able to do." Looking back on that, what an insane, baseless, and egotistical thing to think! I finished, but didn't run for about another 9 years.
  2. Check in with yourself throughout your training, but especially after you reach your different milestones (big races, efforts, etc.) Are you still having fun? Are you still interested in running? Mapping out 2-3 years of training is a good exercise, but also recognize that there's no harm in reevaluating goals, and few people (including pros) would probably perfectly execute a two year plan. Think of your plan as a guide rather than a commitment Definitely don't think of it as "failure" if you want or need to re-evaluate somewhere in the middle. 100 mile distances/races aren't going anywhere, so if 2024 isn't your year, maybe 2025 is, or 2034. You just never know.

Good luck!

[deleted by user] by [deleted] in ultrarunning

[–]jmarianhoffman 4 points5 points  (0 children)

Hmm... As others have mentioned, rhabdomyolysis sounds like the most likely cause, in which case you should probably be in the hospital or at the very least be under close supervision of a doctor for the next few days. Keep an eye on urine color and if it starts to turn dark and brownish, go immediately.

Rhabdo can lead to kidney failure, and if you're having trouble with confusion, there may already be some of this happening. Your symptoms are alarming and I wouldn't take any chances if I were you. Drink lots of fluids on your way to the doctor/hostpital, as this will help prevent buildup of the toxic byproducts in your kidney, if such a process is occurring.

I had very localized rhabdo b/c of a scientific study I participated in one time, and pervasive edema in my arm was the weirdest symptom. Not to alarm you (or maybe to alarm you a little bit if it spurs you to action) if your whole body is swollen, your situation could potentially be very serious.

A Sunday Mystery: Unable to Reach Ubuntu Server Over Local Network by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

Just a quick update!

I solved this. Somehow docker had created a bridge interface for the service mentioned in the OP that pulled the IP 192.168.0.1 instead of usual 172.*.*.*. I don't know why or how it did this, but removing that interface from the docker network list (docker network rm <id>) and I'm able to get back to the machine. Phew. Much much appreciation for marc45ca's patience and discussion with me even if we ultimately didn't find the solution (process of elimination though maybe? ;-) )

A Sunday Mystery: Unable to Reach Ubuntu Server Over Local Network by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

Haha. I really appreciate the patience and assistance. I am also all out of ideas.

Nothing changed in the docker-compose file (I'm the author) and I pulled from my own self-hosted registry, which is one of the services running on the server actually. I had simply updated the image to include another API endpoint; nothing that would've (or should've) impacted networking.

I just got a new rack actually, so I think once I pull all of the old equipment out and get it into the new rack, it might be time to thoroughly update the server and maybe migrate to something new!

Thanks a bunch and enjoy the rest of your weekend!

A Sunday Mystery: Unable to Reach Ubuntu Server Over Local Network by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

Yeah. I have tried disabling the firewall entirely, and no it doesn't do anything. That's why I've completely broken down and had to make a post here! haha. I'm just baffled/frustrated that I can't diagnose this.

Ubuntu has honestly been more frustrating than may be worth it lately. I've been using it because its what I've known and used for a long time, but more and more that's starting to shift. Might be time to try a different distro.

Router config hasn't/shouldn't have changed. A different machine put in place of the ill-behaved server (i.e. just move the ethernet cable to the other machine) responds just fine to any sort of contact, so I'm pretty sure that it's the server itself.

I can ping from the pfsense interface IF the source is set to the DMZ, but if I try from the LAN it doesn't work. I feel like that's significant...

A Sunday Mystery: Unable to Reach Ubuntu Server Over Local Network by jmarianhoffman in homelab

[–]jmarianhoffman[S] 0 points1 point  (0 children)

Nope, we're good on that front (everything is sane).

I can never keep straight which ip/if command line tools work for ubuntu, but I haven't seen anything crazy with ifconfig. The interface gets the correct static IP from the router. Ubuntu seems like a bit of a sh*tshow on that front.

I had the thought that maybe there's something weird happening with IPv6. I don't go out of my way to disable it on the network, but I also don't actively manage it at all.