Zum Inhalt der Seite gehen

mastodon
thread, devlog maybe, computer, agressive?

Sensitiver Inhalt

#linux #selfhosted #selfhosting #qemu #DEVLOG #networking
Dieser Beitrag wurde bearbeitet. (3 Monate her)
Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •

So this is how i want to do this:

  • Devices in my network can interact with the VM as if it was another computer, mainly for testing with jellyfin, caddy, dns (pihole)
  • It can be done on a wireless interface
  • The VM has a wireless
  • The virtual interface uses dhcp
Dieser Beitrag wurde bearbeitet. (3 Monate her)
Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •
So far i have managed to setup an IPVTAP on my wireless interface and it works onlye one way: can ping devices on my LAN but they can't ping the virtual machine itself; it just doesn't expose the ports on the ip
Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •

i am indeed that fucking stupid holy shit.

Ok so it now works and with internet access too! with the exception of my host pc, i can't ping my router form my host no more and ports are still not working on the host and honestly im not gonna bother, im probably going to route ssh through a unix socket and be done with it.
I also stopped using dhcpcd because i'm to lazy to sync the vm ip and the host ipvtap ip

Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •
ok, day 2.
I'm going to mess with the vm a bit more and then i'm going to study for finals.
Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •
ok i gave up with the unix socket and tried to fix communicationg host-guest but came across this which explains that macvtap and ipvtap just don't allow host-guest communication by nature so I'll need to user another interface to communicate with the vm which actually comes in pretty handy for testing dns resolution with pihole for requests on different interfaces

Guest and host cannot see each other using linux-kvm and macvtap

I'm migrating a kvm virtual machine from an old host (both hardware and OS) to a new one. For networking, virt-manager proposed me a new option: macvtap. This looked a good alternative to setting ...
Super User
Als Antwort auf [MIGRATED]

[MIGRATED]
mastodon
[MIGRATED]
• •

finally have time for this again

got the interface for host-vm communication up and running with the libvirt nat bridge, i mean i have it at hand why not use it? (this totally wont come back to torment me).

Weird thing is that by using -netdev bridge... qemu doesn't assign an ip to the tap in the host and idk if it is a requirement cuz i did setup the ipvtap interface with an ip on the host and an ip on the vm.
Idk how qemu sets up the tap interface behind scenes, maybe because of iptables shenanigans and the NAT thing

Can someone explain how it works? I guess not having an IP on the host tap interface makes more sense than having one

#networking #qemu #kvm

#qemu #networking #kvm
Als Antwort auf [MIGRATED]

Altbot
mastodon
Altbot
• •

The image shows a terminal window displaying network scan results. The top section shows Nmap scan results indicating one IP address (192.168.122.2) is up, with latency of 3 seconds. It also lists open ports 22 (ssh) and 9090 (zeus-admin), along with many filtered ports. The scan took 81.33 seconds. The bottom section shows network interface information for interfaces "wlp0s20f3" and "tap0", including IP addresses, MAC addresses, and other network configuration details. Timestamps are visible in both sections.

Provided by @altbot, generated using Gemini

@Altbot

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos

⇧