Linux

48684 readers

387 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Introduction to Linux interfaces for virtual networking | Red Hat Developer [2018-10-22] (developers.redhat.com)

submitted 2 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

Do you use any of the mentioned virtual network interfaces? What for?

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 14 points 2 months ago (1 children)

Handy primer, but also out of date, especially for RHEL and RHEL-adjacent. For one thing, they’re all in on NetworkManager. The commands outlined in the article aren’t permanent, and it doesn’t go over ways to make them permanent. Secondly, teaming is deprecated by RH since the guy who maintained the driver quit.

[–] [email protected] 3 points 2 months ago (1 children)

Do you happen to know any more recent documentation that would have similar diagrams?

[–] [email protected] 2 points 2 months ago

I don’t. I usually search for, e.g., nmcli bridge setup

[–] [email protected] 3 points 2 months ago* (last edited 2 months ago)

I use macvtaps in my homelab for vulnerable VMs because no matter how I set up the bridges or what guide I followed it just broke networking every time on a headless server that's a massive pain to fix.

Wish I knew about macvtaps from the get-go, it was a dead giveaway that bridges are some demonic shit on Linux as every guide was different, and for every guide there was always some people on Reddit saying how it didn't work for them at all.

I haven't found myself missing hard-corpo software in a while but in that moment I really wished I was just using VMware on windows where creating a bridge interface takes one click instead of janky virsh syntax and messing with ifconfig etc.