How to SSH to a VirtualBox guest externally through a host?

Question

I have a Ubuntu VM running on my Windows 7 machine. How do I set it up so that I can access the webserver externally through SSH?

I found steps (Setup SSH access between VirtualBox Host and Guest VMs) to be able to ssh to my guest from my host, but that still leaves me with the problem of accessing it through my router.

I suppose that I could install an SSH server on my Windows machine and then tunnel a few times (though I'm not 100% sure what to use in terms of local, dynamic, etc. or how to set up multiple tunnels?), but is there a way to make the VM directly accessible to my router so I could directly port forward to it?

There's a much easier way to do this, using Vagrant (which creates ready-to-go VMs (ssh-accessable, ip-accessable) from a config file or GUI). I don't know your use-case, but I've written a large tutorial on [How to create an ssh-accessable Ubuntu server VM with Vagrant](http://www.dev-metal.com/setup-virtual-machine-multiple-vagrant-puphpet/), useful when you want to setup a LAMP-based development machine. — Sliq, Sep 15 '13 at 16:30
Vagrant is a great tool, but it isn't compatible with the more recent versions of virtualbox — LizH, Mar 12 '16 at 14:16
Best answer is further down: http://stackoverflow.com/a/10410527/2214806 — Michael, Jul 26 '16 at 21:44
You can check this tutorial http://wiki.workassis.com/virtualbox-ssh-between-host-and-guest/ — Bikesh M, Nov 29 '16 at 06:45
Is think could be usefull to have a new, specifi, place where to speak about virtualization https://area51.meta.stackexchange.com/questions/28201/proposal-for-a-site-about-virtualization — realtebo, Aug 22 '18 at 22:00

score 1353 · Accepted Answer · edited Sep 01 '18 at 22:14

1353

The best way to login to a guest Linux VirtualBox VM is port forwarding. By default, you should have one interface already which is using NAT. Then go to the Network settings and click the Port Forwarding button. Add a new Rule. As the rule name, insert "ssh". As "Host port", insert 3022. As "Guest port", insert 22. Everything else of the rule can be left blank.

or from the command line

VBoxManage modifyvm myserver --natpf1 "ssh,tcp,,3022,,22"

where 'myserver' is the name of the created VM. Check the added rules:

VBoxManage showvminfo myserver | grep 'Rule'

That's all! Please be sure you don't forget to install an SSH server in the VM:

sudo apt-get install openssh-server

To SSH into the guest VM, write:

ssh -p 3022 user@127.0.0.1

Where user is your username within the VM.

edited Sep 01 '18 at 22:14

nbro

15,395
32
113
196

answered May 10 '12 at 10:39

vkostromin

14,188
2
17
7

1

What do I use as a host name or IP address? – Keyslinger Dec 03 '12 at 13:14
Keyslinger, just left blank, you don't need fill them – vkostromin Dec 03 '12 at 14:39
1

Note that you need to enable VirtualBox firewall access for both public and private networks. – Victor P. Dec 11 '12 at 05:47
26

@Keyslinger, is this what you were looking for? `ssh -p 3022 user@127.0.0.1` That was the one step that I was missing and just went to find on another site. – D. Woods Dec 21 '12 at 04:50
just want to give props to you guys. THis answer helped me with my own problems with the vm. which i now convert into my own solution at superuser http://superuser.com/a/527462/8184 – Kim Stacks Jan 03 '13 at 07:21
This helped me get a bit further but still having issues. If anyone could look at my issue here http://sqa.stackexchange.com/q/5399/4556 it would be very much appreciated!! – sfarbota Jan 04 '13 at 20:31
10

I also added the port redirect from 2020 to 80, so I can easily access Apache from the browser using http://192.0.0.1:2020. VBoxManage modifyvm myserver --natpf1 "ssh,tcp,,2020,,80" – Eduardo Russo Feb 28 '13 at 09:20
@AngeloR. first see if your guestVM can ssh into itself. I'm setting up a minimal dev environment, and as it turns out, minimal can mean not even an SSH server. – John Simon Apr 07 '13 at 18:11
I did this, restarted the VM, captured the IP address of the VM using `ifconfig`, tried `ssh `, still couldn't connect – amphibient Aug 19 '13 at 19:30
However, when I moved the Network Adapter to the `Bridged` mode, it worked. – amphibient Aug 19 '13 at 19:51
See VirtualBox networking docs: http://www.virtualbox.org/manual/ch06.html#network_nat – Ruslans Uralovs Oct 10 '13 at 20:20
1

Works great with ssh -p 3022 user@127.0.0.1, but how can I connect from another machine somewhere in the internet to my vbox via windows? I used the IP-address of windows and tried ssh -p 3022 user@mywindowsip, but got a connection timeout. If I use the same command on my host machine, it works. – Martin Kapfhammer Oct 27 '13 at 14:26
Thanks! Works great with the Cloudera Quickstart VM, too. – shoover Dec 12 '13 at 17:47
This worked for me, with guest OS SUSE 9.3 However I did have to modify the guest-OS firewall to allow SSH service (or, just disable the guest-OS firewall). These firewall changes are made using whatever firewall config tool the guest-OS provides (eg, YAST). – Darren Smith Jan 04 '14 at 17:38
1

Make sure you're not using `sudo VBoxManage` since it won't be your current user and make sure that the vm is stopped ;) – GabLeRoux Feb 10 '14 at 03:35
I used this along with starting the VM in headless mode: VBoxManage startvm "vmname" --type headless – Ray Hunter Feb 23 '14 at 00:16
4

thebigdog, you can headless directly: VBoxHeadless -s 'vmname' – vkostromin Feb 27 '14 at 19:19
How can I add the box's ip into the `/etc/hosts` file to create a link alias ? – Ateev Chopra Jul 07 '14 at 12:58
It should be "localhost" anyway. Otherwise add a line with "127.0.0.1 localhost" or similar. – Sebastian Höffner Jul 30 '14 at 17:36
This works. However, the problems are: 1. The connection is extremely slow. It takes a few seconds for the "enter password" prompt to show up. 2. The password is not buffered, i.e., you have to enter the password of the ssh key each time you ssh to the VM. – York Dec 21 '14 at 02:33
I've figured out the reason for not being able to buffer the ssh password. That was because I didn't add the public key to my VM. However, the login is still extremely slow and takes at least five seconds. – York Dec 21 '14 at 02:51
6

Why are we using port 3022 and not the default 22? – Seraphim Jul 22 '15 at 11:27
The comments weren't that clear - I logged into the guest OS (Ubuntu 14.04 in my case) and ran `sudo apt-get update` and `sudo apt-get install openssh-server`. After that I ran the VM headless on my Mac and was able to ssh in :) – Matt Kneiser Aug 10 '15 at 06:14
@York I use an `expect` script to automate an SSH session, including the password input. – Frerich Raabe Jan 29 '16 at 09:40
The ssh is not connecting saying Connection closed by 10.0.2.15 – AbdulBasit Mar 20 '16 at 14:12
Just as a helpful tip to list all virtual machines before you start this task, use `VBoxManage list vms` – enthusiasticgeek Apr 07 '16 at 15:56
4

To make life easier, open ~/.ssh/config, add the following `Host mybox HostName 127.0.0.1 User myuser Port 3022` to that file (add indent yourself), then you only need to `ssh mybox` each time :) – vancexu Apr 12 '16 at 06:07
If you do `route -n` in your linux VM, you'll find the IP to ssh into on the `default` line. On my windows it is: 10.0.2.2. (When adapter is NAT and with the port forwarding as above.) – not2qubit Nov 01 '16 at 12:28
I prefer https://stackoverflow.com/a/10410527/4200039 as it avoids messing around with port forwarding. – Ben Creasy Jul 22 '17 at 23:51
damn, tnx... I tried everything then simple port fordwarding works – Klemenko Mar 01 '18 at 08:49
2

@Seraphim, we are using Port `3022` because possibly the machine hosting the VM may already have an SSH daemon listening on port `22`. This extends the answer beyond Windows machines running VirtualBox, e.g. to a linux host environment. Point here is a) one port per service (can't listen on `22` if a service already uses it) and b) we need to use a non-privileged port [higher than `1024`](https://www.cyberciti.biz/faq/linux-unix-open-ports/). – raddaqii Apr 27 '18 at 13:10
I found this to be of enormous help for me to access a VM that did not allow to login graphically any more but that had an SSH server installed. Many thanks! – smoe Oct 21 '18 at 11:55
Ok with that, buy how can you ssh into your guest os via an external network..... I mean using PUBLIC IP ADDRESS !! – Panagiss Feb 29 '20 at 11:48
This is the most voted solution but it didn't work for me. VirtualBox 6.1 running on OSX Mountain Lion. Ubuntu Server 20.04 running as VM. I set up port forwarding as instructed, but when I try to ssh into the VM, it times out. Yes, sshd is running on the VM. – Bob Jun 04 '20 at 16:14
Very useful! I am wondering why `-p 3022` works, but if I try to append `:3022` to the hostname it says "Name or service not known" – mitchus Jul 03 '20 at 09:32

score 131 · Answer 2 · edited Feb 27 '13 at 18:44

131

Change the adapter type in VirtualBox to bridged, and set the guest to use DHCP or set a static IP address outside of the bounds of DHCP. This will cause the Virtual Machine to act like a normal guest on your home network. You can then port forward.

edited Feb 27 '13 at 18:44

Peter Mortensen

30,738
21
105
131

answered May 06 '11 at 03:37

JohnD

3,884
1
28
40

2

Any Idea how 2 adapter configuration will work? One on NAT and other on Host Only? – CantGetANick Mar 14 '12 at 11:47
16

In my opinion exposing the VM on the local network is not the best option (for instance in an office network), the solution proposed by @vkostromin keeps the encapsulation of the VM within the host. – Victor P. Dec 10 '12 at 23:17
2

@VictorP. can you please explain why it's not the best option in an office network? Is it due to security or? – mdo123 Aug 16 '17 at 18:02
1

Even knowing that is not the best option, in my current configuration set the adapter to bridged is the only solution that works. – James Mar 16 '18 at 20:49

score 70 · Answer 3 · answered May 02 '12 at 08:53

70

Keeping the NAT adapter and adding a second host-only adapter works amazing, and is crucial for laptops (where the external network always changes).

http://muffinresearch.co.uk/archives/2010/02/08/howto-ssh-into-virtualbox-3-linux-guests/

Remember to create a host-only network in virtualbox itself (GUI -> settings -> network), otherwise you can't create the host-only interface on the guest.

answered May 02 '12 at 08:53

orip

73,323
21
116
148

2

Only this answer worked for me, nothing else did. Also, I just added additional adapter and it worked, didn't need to edit the `/etc/network/interfaces`, Thanks! – brokenfoot Apr 09 '14 at 23:19
3

Agreed this is the best answer. Otherwise, you're jumping through hoops every time you want to access a common service (`ssh`, `sftp`, etc.) since you'd have to go through a non-standard port. – Kirk Woll Jun 01 '16 at 20:10
1

I prefer to link to Internet Archive: https://web.archive.org/web/20160523035053/https://muffinresearch.co.uk/howto-ssh-into-virtualbox-3-linux-guests/ - https://web.archive.org/web/20170701174835/http://christophermaier.name/2010/09/01/host-only-networking-with-virtualbox/ is another good explanation. – Ben Creasy Jul 22 '17 at 23:53
1

another good source on setting this up https://2buntu.com/articles/1513/accessing-your-virtualbox-guest-from-your-host-os/ – mdo123 Aug 16 '17 at 17:53
ping from the host to the guest works but ssh returns `port 22: Connection refused`. – Sparkler Feb 21 '18 at 15:19
1

@Sparkler is sshd running? Is there a firewall closing ports? – orip Feb 21 '18 at 19:56
Note that if the host-only adapter name (should be vboxnet0) is not shown, you have to create it first via: File – Host Network Manager – Create – [use defaults]. – ascendants Nov 18 '19 at 21:32

score 27 · Answer 4 · edited Sep 01 '18 at 22:22

27

You can also use a Bridged Network (or "Bridge Adapter", in newer versions) in network settings. This will put your VM in a VLAN with your machine. So you can just ssh into the VM like this.

ssh user@IP_OF_VM

edited Sep 01 '18 at 22:22

nbro

15,395
32
113
196

answered May 05 '14 at 04:33

Kashyap Kopparam

379
3
2

With this solution does the SSH connection go across the LAN? – user2233706 Jun 11 '18 at 01:39

score 24 · Answer 5 · edited May 23 '17 at 11:47

How to do host-only network (better than bridged) for Solaris 10 and Ubuntu 16.04

Add Host-only interface

Virtualbox > File > Preferences > Network > Host-only Networks > Add
Shutdown vm.
VM's Settings > Network. First adapter should be Nat, second Host-only.
Start cmd.exe and run ipconfig /all. You should see lines:
```
Ethernet adapter VirtualBox Host-Only Network:
   ...
   IPv4 Address. . . . . . . . . . . : 192.168.59.1
```
Second adapter in guest should also be in 192.168.59.*.
Start VM.

Solaris 10

Check settings ifconfig -a. You should see e1000g0 and e1000g1. We are interested in e1000g1.
ifconfig e1000g down
ifconfig e1000g 192.168.56.10 netmask 255.255.255.0 up
Check from host if this interface is reachable: ping 192.168.56.10

Preserve those settings upon reboot

# vi /etc/hostname.e1000g1
192.168.56.10 netmask 255.255.255.0
# reboot

Configure ssh service (administering) to login as root (not adviced)

Check if ssh is enabled

# svcs -a | grep ssh
online         15:29:57 svc:/network/ssh:default

Modify /etc/ssh/sshd_config so there is

PermitRootLogin yes

Restart ssh service

svcadm restart ssh

From host check it

ssh root@192.168.56.10

Ubuntu 16.04

List interfaces:

ip addr

You should see three interfaces like lo, enp0s3, enp0s8. We will use the third.

Edit /etc/network/interfaces

auto enp0s8
iface enp0s8 inet static
    address 192.168.56.10
    netmask 255.255.255.0

Then sudo ifup enp0s8. Check if enp0s8 got correct address. You should see your ip:

 $ ip addr show enp0s8
 ...
    inet 192.168.56.10/24 brd 192.168.56.255 scope global secondary enp0s8

If not, you may run sudo ifdown enp0s8 && sudo ifup enp0s8

https://superuser.com/questions/424083/virtualbox-host-ssh-to-guest/424115#424115

This doesn't work if your host-only network is on `192.168.59.1` and you specify `192.168.56.10` for the static guest IP. The entire class C subnet address must match exactly, so you would have to use something like `192.168.59.10` inside the guest instead. — Quolonel Questions, Sep 10 '17 at 11:15

Yuci · Answer 6 · 2018-02-10T23:23:56.457

18

In order to ssh to a Ubuntu VM running in VirtualBox from your host machine, you need to set up two network adapters for the VM.

First of all, stop the VM if not yet.

Then select the VM and click the Settings menu in the VirtualBox toolbar:

Set up Adapter 1

Set up Adapter 2

(Note: you don't need to set up any port forwarding.)

That's it. Once set up, you can start your VM. In your VM, the network configuration will look like below and you'll have Internet access too:

Also in your host machine, you can ssh to your VM:

Be sure that the SSH server has been installed and up running in the VM.

$ ps aux | grep sshd
root 864 0.1 0.5 65512 5392 ? Ss 22:10 0:00 /usr/sbin/sshd -D

If not, install it:

$ sudo apt-get install openssh-server

Also for your information:

My VirtualBox version: 5.2.6 r120293 (Qt5.6.2), 2018
My Ubuntu version: Ubuntu 16.04.3 LTS
My host machine: Windows 10

edited Feb 10 '18 at 23:23

answered Feb 10 '18 at 20:17

Yuci

27,235
10
114
113

1

If you don't have any host-only adapter, you can create one from: `File > Host Network Manager > Create` – Cirelli94 Mar 20 '20 at 15:52
1

It doesn't reach internet network sadly – Cirelli94 Mar 20 '20 at 16:06
This method is good in that you can also access your VM both from the HOST and from none-HOSTS machines. Awesome! – Laenka-Oss Jan 21 '22 at 11:30

score 5 · Answer 7 · edited Jul 22 '16 at 04:49

5

For Windows host, you can :

In virtualbox manager:
1. select ctrl+G in your virtualbox manager,
2. then go to network pannel
3. add a private network
  1. make sure that activate DHCP is NOT selected
In network management (windows)
1. Select the newly created virtualbox host only adapter and the physical network card
2. Right-Click and select "Make bridge"
Enjoy

edited Jul 22 '16 at 04:49

Giacomo1968

25,759
11
71
103

answered Dec 02 '13 at 21:27

Alexandre Mélard

12,229
3
36
46

NoobNet14 · Answer 8 · 2015-11-12T13:37:23.417

SSH Back to Your Home / Office VirtualBox Guest Machine From The INTERNET

The answers provided by other users here : How to SSH to a VirtualBox guest externally through a host?

... helped me to accomplish the task of connecting from out on the internet to my home computer's guest machine. You should be able to connect using computers, tablets, and smart phones (android, IPhone,etc). I add a few more step in case it might be helpful to someone else:

Here is a quick diagram of my setup:

Remote device ---> INTERNET --> MODEM --> ROUTER --> HOST MACHINE --> GUEST VM
Remote device (ssh client) ---> PASS THRU DEVICES ---> GUEST VM (ssh server)
Remote device (leave ssh port 3022) ---> INTERNET --> MODEM --> ROUTER (FWD frm:p3022 to:p3022)--> HOST MACHINE (FWD frm:p3022 to:p22) --> GUEST VM (arrive ssh port 22)

The key for me was to realize that ALL connections was PASSING-THROUGH intermediary devices to get from my remote PC to my guest virtual-machine at home --Hence port forwarding!

Notes: * Need ssh client to request a secure connection and a running ssh server to process the secure connection.

I will forward the port 3022 as used in the chosen answer from above.
Enter your IPs where needed (home modem/router, host IP, guest IP,etc.), Names chosen are just examples-use or change.

1.Create ssh tunnel to port 3022 on your modem's IP / router's external IP address.

ssh client/device possible commands: ssh -p 3022 user-name@home_external_IP

2.Port forward = we are passing thru the connection from router to host machine

Also make sure firewall /IPtable rules on router is allowing ports to be forward (open if needed)
Router's Pfwd SCREEN required entries: AppName:SSH_Fwd, Port_from: 3022, Protocol:both (UDP/TCP), IP_address:hostIP_address, Port_to:3022, everything else can be blank

DD-WRT router software resources / Info:

3.Host Machine Firewall: open port 3022 #so forwarded port can pass thru to guest machine

Host Machine: Install VirtualBox, guest additions, and guest machine if not done already
Configure guest machine and then follow the Network section below
I used VirtualBox GUI to setup guest's network- easier than CLI
If you want to use other methods refer to : VirtualBox/manual/ch06.html#natforward

4.Some suggest using Network Bridge adapter for guest = access to LAN and other machines on your LAN. This also pose an increase security risk, because now your guest machine is now exposed to LAN machines and possibly the INTERNET hackers if firewall not setup properly. So I selected Network adapter attached to NAT for less exposure to bridged security risks.

On the guest machine do the following:

Guest Machine VirtualBox Network settings: Adapter 1: Attached to NAT
Guest Machine VirtualBox Port Forwarding Rule: Name:External_SSH, Protocol:TCP, Host Port: 3022, Guest Port 22, Host&guest IPs:leave blank
click on advance in Network section then click on Port forwarding to enter rules
Guest Machine Firewall: open port 22 #so ssh connection can enter
Guest Machine: Make sure that ssh server is installed, configured properly, and running
LINUX test to see if ssh server running w/command: sudo service ssh status
Can check netstat to see if connection made to port 22 on the guest machine

Also there are different ssh servers and clients depending on platform using.

wikipedia/Secure_Shell
wikipedia/Comparison_of_SSH_servers
wikipedia/Comparison_of_SSH_clients

For Ubuntu Users:

ubuntu community: SSHOpenSSH/Configuring
ubuntu/community: OpenSSH/Keys

That should be it. If I made a mistake or want to add anything -feel free to do so-- I am still a noob.

Hope this helps someone. Good luck!

score 4 · Answer 9 · answered Feb 24 '15 at 19:00

You can also initiate a port forward TO your HOST, OR ANY OTHER SERVER, from your Guest. This is especially useful if your Guest is 'locked' or can't otherwise complete the ModifyVM option (e.g. no permission to VBoxManage).

Three minor requirements are 1) you are/can log into the VirtualBox Guest (via 'console' GUI, another Guest, etc), 2) you have an account on the VirtualBox HOST (or other Server), and 3) SSH and TCP forwarding is not blocked.

Presuming you can meet the 3 requirements, these are the steps:

On the Guest, run netstat -rn and find the Gateway address to the default route destination 0.0.0.0. Let's say it's "10.0.2.2". This 'Gateway' address is (one of) the VirtualBox Host virtual IP(s).
On the Guest, run ssh -R 2222:localhost:22 10.0.2.2 where "10.0.2.2" is the VirtualBox server's IP address -OR- any other server IP you wish to port forward to.
On the Host, run ssh 10.0.2.2 -p2222 where 10.0.2.2 is the default gateway/VBHost virtual IP found in step 1. If it is NOT the VirtualBox host you are port forwarding to, then the command is ssh localhost -p2222

score 4 · Answer 10 · answered Nov 30 '17 at 04:50

Follow below steps to login to your ubuntu VM running in virtual box from the host machine using putty (Without port forwarding):

On Virtualbox manager select the vm, click on settings icon. Then go Networks and enable two adaptors as below:
- Adaptor 1 (For internet access): Attached to -> NAT, Advanced -> Check the cable connected.
- Adaptor 2: Attached to -> Host only adaptor, Advanced -> Check the cable connected and Promiscuous mode -> Allow all.
Start the ubuntu vm.
Login to the VM as root.

Edit the file '/etc/network/interfaces' as below and save it:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

Restart the VM.
Login to the VM and run below command to check the IP allocated to eth1:
```
ifconfig
```
Use this IP to open putty session for the VM.

score 2 · Answer 11 · answered Mar 10 '13 at 11:55

2

A good explanation about how to configure port forwarding with NAT is found in the VirtualBox documents: http://www.virtualbox.org/manual/ch06.html#natforward

answered Mar 10 '13 at 11:55

rodrunner

1,860
4
23
34

DarckBlezzer · Answer 12 · 2019-11-05T17:16:09.137

Ubuntu 18.04 LTS

Configuration with bridged to see the server ip, and connect without "port forwarding"

VirtualBox > right click in server > settings > Network > enable adapter 2 > select "bridged" > Promiscuous mode: allow all > Check the cable connected > start server

On ubuntu server, edit sudo nano /etc/netplan/*init.yaml file,

My sample file:

network:
    ethernets:
        enp0s3:
            addresses: []
            dhcp4: true
        enp0s8:
            addresses: [192.168.0.200/24]
            dhcp4: no
            dhcp6: no
            nameservers:
               addresses: [8.8.8.8, 8.8.4.4]
    version: 2

Commands that will help you

nano /etc/netplan/file.yaml     # file to specify the rules of network
reboot now                      # restart ubuntu server right now
netplan apply                   # do after edited *.yaml, to apply changes
ifconfig -a                     # show interfaces with ip, netmask, broadcast, etc...
ping google.com                 # to see if there is internet

Configure Static IP Addresses On Ubuntu 18.04 LTS Server - with NetPlan

score 1 · Answer 13 · answered Sep 10 '13 at 01:15

1

Simply setting the Network Setting to bridged did the trick for me.

Your IP will change when you do this. However, in my case it didn't change immediately. ifconfig returned the same ip. I rebooted the vm and boom, the ip set itself to one start with 192.* and I was immediately allowed ssh access.

answered Sep 10 '13 at 01:15

boulder_ruby

38,457
9
79
100

This information I'm guessing is partially or even entirely inaccurate in some general sense, I have no idea. downvoter didn't bother to say. – boulder_ruby Jul 18 '14 at 00:21
To wit, "for some, it does not work." – boulder_ruby Jul 18 '14 at 00:24

score 0 · Answer 14 · edited Jan 09 '14 at 19:14

On secure networks setting your network to bridge might not work. Administrators could only allow one mac address per port or even worse block the port should the switches detect multiple macs on one port.

The best solution in my opinion is to set up additional network interfaces to handle additional services you would like to run on your machines. So I have a bridge interface to allow for bridging when I take my laptop home and can SSH into it from other devices on my network as well as a host only adapter when I would like to SSH into my VM from my laptop when I am connected to the eduroam wifi network on campus.

score 0 · Answer 15 · answered Jul 18 '16 at 10:44

0

Use NAT network adapter and Add port forward. Mention actual host ip.Do not use 127.0.0.1 or localhost.

answered Jul 18 '16 at 10:44

anunaki

989
9
16