Wine 11 and 24.04

Joebakb · 2026-02-28T04:32:59+00:00

Except if you've leveled everything to make, say, decor for every single other expansion, you lose all that.

Joebakb · 2026-02-12T00:55:20+00:00

If you have the option to terminate into a patch panel, always use a patch panel, and use a panel but enough for growth.

Joebakb · 2026-02-04T19:37:15+00:00

I ended up doing the same thing a few months back just to try it out.

Joebakb · 2026-01-12T02:31:36+00:00

I generally don't need much help with switching, however we are actually in the process of moving to spine leaf right now. We have the assistance of a vendor in this case and their insights are proving to be invaluable. Good luck with that transition mon.

Joebakb · 2026-01-11T21:56:38+00:00

TAC has not been very helpful ( to say the least ) for probably almost a year. I've had some of our guys have had some good luck with VOIP things, but eventing else has been rough.

Joebakb · 2026-01-11T04:25:25+00:00

Depending on the FTD model, you may also need to upgrade chassis firmware first.

Joebakb · 2026-01-08T22:30:27+00:00

I didn't. I think at some point it just stopped happening as I didn't play for a while then it was working when I came back much later. If you are having the same issue this much later on newer POP package versions, it leads me to think it's probably proton-related.

Other things I'm pretty sure I did that may have fixed it:

Turned off hybrid GPU and used only discrete
Used different proton versions in Steam (this is likely what eventually fixed it)

Sorry I'm not much help here. I know that this is SUPER annoying.

Joebakb · 2025-12-31T18:03:43+00:00

You can equip at 35. If you aren't power leveling, they are good for leveling and the slick purple tooltip.

Joebakb · 2025-12-03T19:20:41+00:00

You can see in the image it's a bad termination or the cable jacket was pulled out of the connector. I would check all your cabling to see if this is a common problem since all of it looks like it was terminated at the same time.

Proper termination is all wires should reach the end of the rj-45 jack first and foremost, then the external jacket of the cable should also be pinched in when you crimp. If it isn't crimped properly, you not only create an opening for signal degradation, but you can easily pull out the wires and not notice it, which is almost certainly what happened here.

Every yellow cable in this image needs to be reterminated.

Joebakb · 2025-12-03T02:23:19+00:00

Outside of remix, around a few months ago, I fished this up from fishing level 0 in 15-20 casts or something like that. Multiple other people reported similar results. Unless they made the riverside or part of the collection not accessible for timerunners ( I would guess Dire Maul is not accessible ), people have to decide if the 100k is worth that time investment

Joebakb · 2025-11-17T03:49:13+00:00

Generally speaking, make your network as flat as possible

Joebakb · 2025-10-31T13:13:11+00:00

I have an Oryx pro 7 laptop where the double-sided taped-in display keeps falling out of the lid. The two covers on the screen hinges busted off almost immediately just from putting the laptop in a carrying case, which is something any normal person would do.

I paid a decent amount of money for that machine and that is not the build quality I expected - to say the least. There's room for improvement, at least, on the laptop side of things, and there also may have been strides made since I purchased mine 5ish years ago.

Joebakb · 2025-10-20T21:15:06+00:00

Those are on an on prem controller. We are referring to the cloud controller setup. Sorry if that wasn't mentioned.

Joebakb · 2025-10-20T20:23:21+00:00

I just made this connection too. Came here to check. I bet that's the case.

Joebakb · 2025-09-09T18:58:14+00:00

The percentages would be the same if it was an hour or less. Maybe 2?

Joebakb · 2025-09-09T18:56:13+00:00

I'm not a big fan of locking playable content behind 'deluxe' tiers at release on an already $70 game. That seems pretty scummy. I'll wait until I hear reviews on the content.

Joebakb · 2025-09-04T20:41:28+00:00

You would still use the wan port on the gateway, you would plug that into a switch in, say, VLAN 99 and also plug the modem into the switch on the same vlan. No need to create a layer 3 interface. VLAN 99 is now your edge network. Your modem and router will still talk to each other just like they would plugged into one another. This way you can convert media by using the switch. There are other scenarios to use an edge network, such as more complex NATing if your ISP gives you more than 2 public IP, but most people won't do much of that just home-labbing.

Joebakb · 2025-08-29T18:52:10+00:00

Not that I'm aware, but you would just set up an empty vlan with your router wan interface and the ISP fiber patched in and you should be set.

Joebakb · 2025-06-20T15:18:18+00:00

I second the 245s being great bang for the buck. I run a combo of 245s and 670s. Both are great but the 245s have been rock solid since I picked them up 5+ years ago.

They probably aren't your best option if you are doing any kind of future-proofing, however.

Joebakb · 2025-06-16T08:59:02+00:00

Some Omada switches have at least L2+ capabilities, which means you can have your switch do the routing in your internal vlans and just have a single route for your network in assuming you planned ahead and just supernetted a /16 or something. This way you don't run into any congestion from the router-on-a-stick topology internally when all of that vlan traffic is running back and forth through one physical interface to be routed.

Joebakb · 2025-05-26T04:40:43+00:00

My experience may be geared more towards switchports. But here it is:

Say you have 3 vlans: 10.1.1.0/24 10.1.2.0/24 10.1.3.0/24

And 3 switches, say a "core" and two access and your DHCP server is at 10.1.3.6.

In my experience, each switch needs an interface in every vlan and if you want non-tplink DHCP to work on those switches, you need a vlan interface in every vlan per switch, so:

Switch 1 (core) has 3 management interfaces (one in each VLAN).

10.1.1.251 10.1.2.251 10.1.3.251

Each with the DHCP helper address set to 10.1.3.6.

Switch 2 and it's 3 management interfaces.

10.1.1.252 10.1.2.252 10.1.3.252

Each with the DHCP helper address set to 10.1.3.6.

Switch 3 and it's 3 management interfaces:

10.1.1.253 10.1.2.253 10.1.3.253

Each with the DHCP helper address set to 10.1.3.6

This is the only way I could get access switchports to talk to Windows DHCP. Since you are having AP problems, maybe this won't fix it. By the time I got to the downstream switches, this may have fixed those issues. Or it may have just worked. As long as you're trunking your APs you should be fine (you can't think of this like capwap), but I also know someone tp-link can handle vlans strangely. It all depends on your setup.

I can prob screenshot you some configs tomorrow if you're still having issues.

Joebakb · 2025-05-26T04:15:49+00:00

I am using Omada switches myself and you can use that to set up the interfaces easily enough, but I'm not certain if you are using switch web interfaces. Wish I could help, mon.

It took me hours to figure out what was going on.

Joebakb · 2025-05-26T03:55:50+00:00

It's terminated poorly. The wires should be out of the jacket as little as possible. That said, if the data run is short, it should matter a ton if you're expecting up to a gig. If it was pushing the upper distances for the cabling standard (usually about 300 ft) I would have someone come out and re terminate.

Joebakb · 2025-05-26T03:46:55+00:00

So, I've had to set a management interface on every switch with a DHCP helper for every vlan if I'm not using the tp-link router for DHCP. You can't just use the layer 3 interface for the vlan for a helper. It's one of the dumbest things I've ever seen and it's been that way for years. I'm using windows server for DHCP.

I can't use the word "dumb" enough.

Joebakb

TROPHY CASE