Setting up a NAT virtual network in KVM

[altman]

@Molski

Did you boot a Manjaro live image on the default network?

I set up a Manjaro guest on KVM with NAT as default network. Same problem. It is not able to connect.

[Molski]

@a-sassermann

When you’re using virt-manager you have to start the default network using the play button

We did that, and verified through virsh above, and it’s set to auto-start.

---

@altman

One more thing, I realized I have had ufw active and running all this time. Could it be a problem?

I can’t say %, but my first instinct is, hell yes!

@altman

sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW OUT   Anywhere                  
443/tcp                    ALLOW OUT   Anywhere                  
192.168.1.1 123/udp        ALLOW OUT   Anywhere                  
192.168.1.1 53/udp         ALLOW OUT   Anywhere                  
22/tcp (v6)                ALLOW OUT   Anywhere (v6)             
443/tcp (v6)               ALLOW OUT   Anywhere (v6)   

I believe the default policy for ufw is to drop input and forward traffic.

And these are very restrictive outbound rules, but we don’t even care about those ones. But this is most likely blocking all forwarding.

I believe we need ufw status verbose to see. (I don’t have ufw atm.)

We could configure ufw to work with this. But it would be all manual down to every last rule.

I would rather rip out ufw.

[altman]

@a-sassermann

You have to right-click the host line, not the indiviudal vm:

Oh, found! I would have never guessed that .

Right now this is what I see

@a-sassermann

When you’re using virt-manager you have to start the default network using the play button whilst it is not set to auto-start:

Do I have to uncheck On Boot? I did but the start button stays grayed out, either I check or uncheck On Boot.

[a-sassermann]

No, the way it is now is perfectly fine. The start button is grayed out as it is started already (state: Active). Did you check in the meantime, if the network source, as in your very first screenshot, is still showing (Inactive)? That would be really strange. This should be the same as the state indicator in the virtual networks state.

[altman]

@Molski

I can’t say %, but my first instinct is, hell yes!

It was ufw all along
I disabled it and it connected so fast it made my head spin. God!!

@Molski thanks a lot for you patience