Hello, i have a machine with a VM, i have create a brigde network that allow me see the external machine, and can connect by ssh, but the external machine can’t see the VM, if someone can help me pls, and thank you.
all the machine use leap 15.1, and the VM is using Libvirt/KVM
Hi
How is the bridge attached to the virtual machine, sounds like it might be using NAT so not on the same network. On the virtual machine what is the ip address?
I use tap’s attached to the bridge… On my host machine I have;
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000
link/ether dc:fe:07:51:20:cf brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether dc:fe:07:51:20:ce brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether a6:59:24:06:8f:9b brd ff:ff:ff:ff:ff:ff
5: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000
link/ether 9e:82:71:61:6a:95 brd ff:ff:ff:ff:ff:ff
Host uses wicked (and YaST2 lan to configure), br0 is attached to en02, the tap0 device is attached to br0, the vm then picks up the address from the local network dhcp server.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:e1:f1:ad brd ff:ff:ff:ff:ff:ff
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:a2:30:d5:c7 brd ff:ff:ff:ff:ff:ff
Host
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether 68:b5:99:ec:e8:7a brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:24:d7:8e:1a:14 brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:ae:40:17 brd ff:ff:ff:ff:ff:ff
7: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:ae:40:17 brd ff:ff:ff:ff:ff:ff
10: virbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:c5:76:c7 brd ff:ff:ff:ff:ff:ff
11: virbr1-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr1 state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:c5:76:c7 brd ff:ff:ff:ff:ff:ff
12: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master virbr1 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:54:00:e1:f1:ad brd ff:ff:ff:ff:ff:ff
i don’t know nothing of network, so i dont know what is tap. I want to use the wireless because i am using a laptop and not have the facilities to use lan.
i am trying this:
A Rasppi 3B+ see a VM.
The VM can see the Rasppi 3B+.
i want the Rasppi 3B+, but i need to still use the wlan0 to navigate on my host.
not find that command, is late for my side, tomorrow i will try if using 2 interface for the VM, one isolate and one with the option of route on virt-manager.
thank you for the help, after the changes i will reply if work or not.
You need to define what you mean by “see.”
So, for example, if your virbrX bridge device is set up as a bridging (transparent) device, then your VM should enjoy access to your physical network like any other physical machine on your network.
When you test network connectivity, you need to ping first by IP address and then by name.
From your diagram, you should be able to ping IP addresses between hosts in both directions, but unless you set up a LAN DNS, you will not be able to ping hostnames in either direction.
So, here is the procedure you should follow to determine where your problem is…
First determine network connectivity of your Guests,
Launch 2 Guest VMs, each should be able to ping the other by IP address. Unless you set up a LAN DNS (or set up /etc/hosts entries) you cannot test ping hostnames.
Ping between at least one VM and the HostOS by IP address.
If you succeed in the above, then you have network connectivity locally on the HostOS.
Now,
As you described, ping from one of your VMs and another Host (likely physical) on your network by IP address. If that succeeds, you can test hostname if you set up a LAN DNS or enter /etc/hosts entries.
Then,
Execute the reverse which you say you did and failed… From the physical host ping your virtual machine by IP address, and if that succeeds you can test hostname if you set that up as described above.
If you still can ping by IP address in only one direction, then it’s not the fault of your virtual machine setup, it’s something in your router… Because you established network connectivity on your local machine.
If you are able to ping in one direction only using hostnames, then that is a problem in your name resolution.
i have not problem pinging on the hostname from VM to another host on the lan.
I want other host can ping or connect by ssh to the VM, but i had set up all type of network that virt-manager allow me and never connec to the VM from another host.