schizo @ schizo @forum.uncomfortable.business

Posts

11

Comments

1,437

Joined

1 yr. ago

My nas isn't running fedora and thus isn't using whatever fedora uses for network definitions, but is netplan under ubuntu.

I mean, probably the same thing, but it was shockingly trivial to configure:

    
network:
  ethernets:
    enp0s31f6:
      dhcp4: no
      dhcp6: no
  version: 2
  bridges:
    br0:
      interfaces: [enp0s31f6]
      addresses: [x.x.x.x/24]
      gateway4: x.x.x.x
      nameservers:
        addresses: [x.x.x.x, 8.8.8.8]
      parameters:
        stp: true
        forward-delay: 0
      dhcp4: no
      dhcp6: no

  

Disabled addresses on the physical interface, added the bridge section and told it which interface(s) to bridge - in this case it'd be the real interface and whatever gets added later by qemu/kvm, and then defined the IP address info.

the virsh network xml file was also straightforward, just make a xml file similar to:

    
<network>
  <name>host-bridge</name>
  <forward mode='bridge'/>
  <bridge name='br0'/>
</network>

  

and then it's just

    
virsh net-define your.xml.file.here
virsh net-start the-name-you-used-in-the-xml
virsh net-autostart the-name-you-used-in-the-xml
virsh net-list --all

  

Should show up in the net list, and be selectable by name when making a VM

That's a configuration problem you've made somewhere: you shouldn't be assigning an IP to the bridge and it's constituent interfaces.

You should take a look at your network config, and run (I'm assuming) dhcp only for br0.

Once you define the bridge network in virsh, and use that to make your VMs, kvm/qemu will assign unique MAC addresses to the VMs, so all you really need to sort out is getting your host OS to only assign an IP for the bridge.

Edit: also checked and yeah, eno2 and br0 and virbr0 are all different MAC addresses; did you maybe pick an option that forces them to inherit a MAC or something?

Wonder what the ICD code for 'Healthcare provider induced molestation' is.

Yeah you don't say.

They're at like a minimum of $80 a fight at this point.

Of course people are going to pirate that shit, because that's far far too expensive.

Interesting. I had assumed it went like the other 133 that source mentions.

Wonder if there's just an extremely over-sized overlap between conservatives who were going to be offended about and willing to boycott and people who drink cheap beer that led to that statistically unusual outcome.

Also maybe cheap beer is cheap beer and there's limited enough brand loyalty that other types of products don't?

My favorite failure was when someone used solid-core cabling for all their patch cables instead of stranded and kept bitching about how unreliable everything was.

Which, of course, it is when you use the wrong cable and it keeps breaking as you move it around.

I was hoping the seditionist traitors would get an extended stay vacation in Kansas courtesy of the Feds.

Instead, they only got half a cookie and a frowny-face sticker.

Pretty clear our judicial branch is utterly worthless and probably needs to be completely tossed out and rebuilt. (I mean, more than what the Supreme Court has been doing, even.)

Ah yes, a boycott which will impact the company much like all the previous ones which were uh, wait no, they didn't do shit did they?

Yawn.

You have to wonder how many other things are out there with effectively worthless encryption because some old document or default option told them to/allowed them to implement it without any 'hey! some 14 year old with a TI-83 could crack this key!' warnings.

It's living at https://firefish.dev/firefish/firefish now. I don't think Naskya got the domains when they got the code maintainership, so all the previous domains are in the hands of who knows.

Firefish isn't quite dead yet. There's a new maintainer and they're doing a pretty good job of keeping security patches, bug fixes, and progress to cleaning up and making the code more maintainable happen.

I've kept my instance up and it's like... fine?

Pfft please. He's temu.com Tony Stark at best.

It's more about the quality of the content: you posted more than a couple hundred characters and thus were able to clearly outline what you wanted, why, and how you thought that would improve things.

Mastodon has the twitter problem where it's short-form hot-takes and basically no good long-form content, other than like, to link to somewhere else for the good content.

I don't have a lot of use for that kind of content especially in a format where it's hard to respond to and have an actual conversation. Most twitter-clone UIs don't do a good job of threading and nesting comments in a way that you can easily follow along and have conversations with the people engaged in discussion.

I'm old and like the forum-style interface where people can write out a complete thought, engage in a formatted discussion that's easy to follow along with, and does so in a way that lets other people easily hop in at any point.

So I'd say it's less about the idea of unifying platforms on a single identity (which I think is a great idea and firmly agree that having some sort of Fediverse SSO would make this a lot easier of a sell for less technical users) but more that dumping a pile of low-quality content into a place with reasonably good content isn't actually improving anything.

(I would also qualify this with a comment that I'm old enough that my first "fediverse service" was FidoNet, so I'm reasonably sure I have a different opinion on the value of a well-designed platform for a single specific task vs making one that can do everything for everyone.)

It's funny how this keeps happening, and mostly keeps happening in the same way.

You'd think after the hundredth time it happens people would start fixing it so you can't simply exploit smart contracts via proxy, but I'm a simple computer janitor so what do I know.

As long as it's something you can turn off and remove, that seems like a weird 'I want everything in one place' thing but not utterly destructive of the Lemmy experience.

It sounded more like stuffing a firehose into your Lemmy UI, at which point all you've really done is just make Lemmy a mastodon client, and I've already got several better options for that anyway.

SA is, without any doubt, the best $10 I've ever spent or will ever spend in my life.

If you want to follow Mastodon hashtags, you should just use Mastodon. It has the UX to support this, and all you'd end up by shoving this into lemmy is a lot of noise in a UI that's designed for replies to a single thread and not just hundreds and hundreds of threads.

I'd 2nd this: you're using it for downloading media, so presumably one of the computers is the one running the actual software that's doing that. Just share the drive over the network from there, and pick the best-supported FS on that platform.

Yeah it turns out that's what nonsense this is.

Worse, I sure as crap never opted into this, but at least you can turn it off.

What a stupid decision some product manager made.

I mean, there's also this thing called a "blog" that I swear about 50% of people that use mastodon would be happier using and is probably what they ACTUALLY want to be doing anyways.