No internet in standaloneVM

No internet connection through sys-vpn, sys-firewall, sys-whonix, or sys-net. I tried manually entering the IP, mask, gateway, and DNS from sys-vpn and sys-firewall settings - connection was established, but there was no internet. I am using a Wi-Fi USB adapter. Internet issue is only in standaloneVM - I tried installing Ubuntu and Arch. I know about templates, but I need linux on standaloneVM as well. I couldn’t find a solution to the problem. Please help

it’s certainly the network mask that is not good, use /8 (or 255.0.0.0 dependely on the notation)

It doesn’t work. The mask 255.255.255.255 also doesn’t work :neutral_face:

mask 255.255.255.255 does not make sense here :wink:

Make sure in network manager to disconnect and reconnect the network to be sure the changes were applied. The configuration in the screenshot looks good to me.

Can you ping 10.138.18.209 from that qube?

can you share the output of ip a and ip r?

Looks like something is wrong, ping is trying to use 127.0.0.1 :thinking:

The network device enX0 is not configured here

What do I need to do for the configuration?

What exactly should I do? The device is connected, and the connection settings are specified. I don’t quite understand what I need to do. Please help :pray:

This may or may not be helpful or related to your issue:

I also had a similar problem as ajsonx.
It seems we both ended up with the same conclusion in order to get internet to work in our standalone.

:grimacing:

You would need to ask someone who knows more in depth how/why it works that way.

Like I said, this may or may not be helpful or related…but is something to try??

Good luck :slightly_smiling_face:

Thank you, friend. I will try it today. Maybe Solene will explain the cause of the problem in more detail.

Worked! I changed network data to random and the internet came back, then I set the correct data and the internet continued to work! Now only sys-whonix does not work in hvm, but sys-firewall and sys-vpn are working! Thank you and have a great day!

This is super weird, looks like a bug :confused:

I try to install a debian13 HVM and had the same problem. I put a random gateway and all was all right…

It seems that this is the case

Glad it worked for you. :slightly_smiling_face: :thinking: It’s been awhile but seems if you changed it back it only worked until a reboot. And then I had to put something random in again and left it. Just so it resembled something more appropriate I used sys-firewall ip. However, if it’s still working after reboot, great!! Thought I’d mention it just incase…

Could you check if you have anything special in the system logs about networking while trying a ping or setting up network?

Maybe something ARP related or IP conflict, I’m not sure what to look for there.

No after reboot i must give a random gateway. In fact, it’s just work with random

Everything was working fine for me after reboot. I no longer needed a random gateway

Out of curiosity, was just re-reading the previous guidance on hvm networking under:

specifically under: “Setting up networking for HVMs”

and there is a reference stating " The Qube Settimgs shows a netmask of 255.255.255.255. This is not suitable for most standalones, and you will need to use a different value."

so I decided to check this out by setting the NIC GW as specified (not random) and try different netmasks. I tried 255.255.255.255; 255.255.255.0; 255.255.0.0 and 255.0.0.0 as suggested and none of these netmasks changed the outcome. No internet. Only changing the GW to random works. The netmask did not seem to matter as was suggested in the article. When using a random GW, still had networking and internet.

However, the doc mentioned the netmasking near the same time as referring to “disposables” so perhaps the netmask has an effect there when using these for disposable templates?? :thinking: Not doing that at the moment but may be something to keep in mind if someone does that…

So if you’re researching this issue, it doesn’t seem related to netmasking anyway…Hope you find the answer to this behavior! :crossed_fingers: