Linux

47948 readers

2021 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

No internet in virtual machine (suppo.fi)

submitted 5 months ago* (last edited 5 months ago) by FrostyPolicy@suppo.fi to c/linux@lemmy.ml

7 comments fedilink hide all child comments

I have on the host machine two network interfaces. One is lan and the other is a wlan. For libvirt I have created a nat network which is bound to the wlan. From the guest I can access other machines in the network host wlan is connected to. Also DNS lookup works. The problem is that there's no connection to the internet at all, e.g. pinging something gives "Destination network unreachable". ~~This only happens when both network connection on the host are active.~~ Running qemu/libvirt on OpenSuse Tumbleweed.

The nat network in question:

<network>
  <name>natToWlan</name>
  <uuid>a44c939c-e6bf-44d0-8f86-376056d418a4</uuid>
  <forward dev="wlp19s0f4u1u1" mode="nat">
    <nat>
      <port start="1024" end="65535"/>
    </nat>
    <interface dev="wlp19s0f4u1u1"/>
  </forward>
  <bridge name="virbr1" stp="on" delay="0"/>
  <mac address="52:54:00:1f:64:95"/>
  <ip address="192.168.100.1" netmask="255.255.255.0">
    <dhcp>
      <range start="192.168.100.128" end="192.168.100.254"/>
    </dhcp>
  </ip>
</network>

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world 4 points 5 months ago* (last edited 5 months ago) (1 children)

Your routing table on the host changes when you have both networks active because the OS is preferring the NIC I'm guessing. You're using a static config for only one interface here.

Either switch to a static setup for NIC and Wlan, or create two interfaces for the VM that cover both host interfaces. A simpler setup would be host networking (macvtap) vs a bridged nat with only one path.

[–] FrostyPolicy@suppo.fi 1 points 5 months ago* (last edited 5 months ago)

This sounds reasonable. Curiously now that I tried again with both host lan & wlan active there was no problem. I have a hunch the routing depends on which interface networkmanger starts first.

$route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.102.1   0.0.0.0         UG    600    0        0 wlp19s0f4u1u1
default         RT-AC86U-6D60   0.0.0.0         UG    20100  0        0 enp15s0
192.168.2.0     0.0.0.0         255.255.255.0   U     100    0        0 enp15s0
192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr1
192.168.102.0   0.0.0.0         255.255.255.0   U     600    0        0 wlp19s0f4u1u1
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0_