I am running Boot2Docker in Virtual Box on Windows, using VB bridged networking. The IP address of my PC (192.168.2.2) and of the VM (192.168.2.30) is determined by the DHCP server.
I have configured the docker bridge as follows:
File /var/lib/boot2docker/profile:
EXTRA_ARGS='--bip=192.168.2.192/25 --fixed-cidr=192.168.2.224/27'
From my Windows PC I can successfully ping the folloing IP addresses:
192.168.2.30 (ip address of eth1 in the Docker Host)
192.168.2.192 (ip address of docker0)
However I cannot ping any container that I start. E.g. for container IP 192.168.2.226,
I get a reply from 192.168.2.2 (my PC address) that the Desitination Host is unreachable.
How can I get this to work?
I figured it out in the meantime:
On Windows 7, from an elevated cmd shell do:
route add 192.168.2.224/27 192.168.2.30
This way the IP packets find their way to the containers!
I have Windows 10 as host with a Manjaro installation as Guest on Virtualbox.
I have set a Debian server on another house with ssh installed. I have setup a dyndns on Debian's network so I can access it remotely.
For example..
From address 12.34.56.78 I ssh to foo.dyndns.org:1234. This port redirects me to 192.168.1.5:22 always as this is my Debian machine and the connection is established. I am able to do this from Windows 10 as well as my android and any other device in 12.34.56.78 or by 3G.
But..
When I try to do this
$ ssh foo.dyndns.org:1234
from the Manjaro Guest in Virtualbox I get the following error:
ssh: Could not resolve hostname foo.dyndns.org:1234: Name or service not known
So I did ifconfig and I saw my inet address was 10.0.2.15. I changed virtualbox's network adapter from NAT to Bridged so I can get a lan ip and I got the host's ip, 192.168.2.4. So I gave it another try and still didn't work.
Also, if i try to connect from vm to server while I'm in the same network
$ ssh user#192.168.2.5:22
it works. In this case virtualbox's network adapter was NAT.
This command works if I try from my android (connectbot).
I can connect the same way from PuTTY from Windows.
So my questions are:
Can it be done?
If so, how? (and why?)
Can a VBox Guest get lan ip that's not the same as the host's?
Is there any more information I should provide?
I have searched for a couple of days in here and on google and all I found where solutions on how someone can ssh INTO a vm. No one (from what I saw) asked the opposite.
Checking manual page for ssh reveals the format of command-line options:
ssh [...] [-p port] [...] [user#]hostnamessh
This simply describes, that you need to change
ssh foo.dyndns.org:1234
to
ssh -p 1234 foo.dyndns.org
if the domain resolves correctly to the ip address.
I have linux server installed with RHEL. My network is configured with natted IPs.
I am confused how can I set the RDNS.A public IP is bonded with server but ifconfig shows only privet natted IP 10.1.... like that
I have set up a pgpool in replication mode with watchdog having a Virtual IP (unused one).
The pgpool and watchdog startup completes successfully.
Virtual eth0:0 interface is created with the specified IP 192.168.143.95. pgPool is configured to run at port 5432
When trying to connect to the virtual IP:port the psql command psql -h 192.168.143.95 -p 5432 -l says
psql: could not connect to server: Connection refused
Is the server running on host "192.168.143.95" and accepting
TCP/IP connections on port 5432?
apparently, there is no listening socket on any port for the virtual ip address.
Does anybody have a similar working configuration?
Are there some unspecified requirements for the Virtual IP address (like same subnet with pgpool interface) ?
I will be thankful for any suggestions as to why this may not work.
Thanks a lot
You need to have the netmask of the virtual IP as the same range as pg instance. Also make sure you don't have firewall opened.
I'm trying simple port forwarding with VirtualBox and it appears VirtualBox.exe is listening on the host to the port, but not actually forwarding the connection to the guest. I've tried on multiple ports, and I've restarted VirtualBox several times. Guest to host connectivity, on the other hand, is fine. Here's the info:
Host: Win7 x64
Guest: Win7 x64
VirtualBox version: VirtualBox 4.2.10
Firewalls: All firewalls on host and guest disabled.
Virtual Box > Machine Settings > Network
Adapter 1:
Attached to: NAT
Cable Connected : True
Port Forwarding:
Rule 1: TCP, HostIP=127.0.0.1, HostPort=8081, GuestIP=127.0.0.1, GuestPort=8081
On Host:
[VirtualBox.exe] TCP 127.0.0.1:8081 IBM-6KT5OPCF76P:0 LISTENING
On Guest:
I never get the connection request on port 8081 or any others I've tried.
Any ideas? I'd like to avoid using VirtualBox's bridged adapter for multiple reasons. I was under the impression that NAT port forwarding was relatively straightforward with VirtualBox.
Thanks!
Paravirtualized Network* (virtio-net) is the key
select your vm that you want for port forwarding.
NOTE: Make sure the vm is in stop mode.
Select “Settings"
Select “Network"
Select any free Adapter. Lets say "Adapter 2"
Enable "Enable Network Adapter"
In Attached to dropdown, select "NAT"
Select "Advanced"
In Adapter Type: Select “Paravirtualized Network (virtio-net)” [ This is important ]
Select “Port Forwarding"
In Right hand part of the “port forwarding” dialog box, select “+"
Provide the
Name: Anything you want. example for ssh, say “ssh"
Protocol: Type of protocol [ for ssh: TCP ]
Host IP: provide hostname from which host you want to connect to [ over here: 127.0.0.1 ]
Host Port: On what port of that Host you want to connect to remote port [ example: 60022 ]
Guest IP: Leave it Blank
Guest Port: To what port you want to connect from the above host. [ for ssh, the default 22 ]
You've pointed guest ip in wrong manner it should be ip of guest (if you're statically assign ip address to guest) or leave it empty. Note you're pointed host ip as 127.0.0.1 it means that port you're forwarding will be accessible only from port (if it isn't what you're desired it should be empty as well).
VBoxManage modifyvm "win" --natpf1 ",tcp,,8081,,8081"
perhaps this is something you've wanted to do. (please look here for more details)
It is not clear which guest OS you are using.
I have faced the same problem.
My host was MAC PC and guest was CentOS 7 on VirtualBox.
I enabled the NAT port forwarding from guest to host at VirtualBox level for both ssh port 22 and http port 80.
However I found that I could not connect to the Apache HTTP server on Centos 7 guest from my MAC PC host on http connection.
To fix it, I have to set the firewalld service to allow port 80 connections.
Faced similar issue on Mac host, Fedora guest setup. Was trying to access http web server running on port 8000 of guest machine from host machine. Opening port 8000/tcp with firewall-cmd on guest machine solved problem.
sudo firewall-cmd --zone=public --add-port=8000/tcp
I faced a similar issue and it turns out to be unsigned drivers in the network stack installed by some corporate proxy interception software called proxycap that were causing virtualbox to error when setting up port forwarding. Check you VM machine logs for the error message while setting up port forwarding and listing the unsigned drivers and uninstall the corresponding application.
I connect to my Centos7 like this:
Virtual Box > Machine Settings > Network
Adapter 1:
Attached to: NAT
Cable Connected : True
Port Forwarding:
Rule 1: TCP, HostIP=127.0.0.1, HostPort=8081, GuestIP=10.0.2.15, GuestPort=8081
$> ssh -p8081 [change]#127.0.0.1
In case someone else met same problem with me, I wrote my mistake here:
I am using CentOS 7 as host and Windows as guest.
The only problem block me was: I forgot to disable Windows firewall settings in guest machine. Once disable it, everything works fine.
If anyone is having same issues, try to uninstall redirectors such as ProxyCap, proxifier, etc. VirtualBox NAT doesn't work with them. You won't find any error message in the logs and you won't see anything in the pcap file if you try to trace VirtualBox networking. Disabling ProxyCap is not enough, it has to be uninstalled or you need to reset your network config with "netsh winsock reset" but ProxyCap won't work for you anymore.
For GNU/Linux users, don't forget the first 1024 ports are restricted to the root user…
If you try forwarding a port lower than 1024, it won't even appear as LISTENING with netstat.
In my case the guest OS is CentOS8, the host OS is Ubuntu 22.04, the forwarded port was 1022 on the host, I changed it to 10022 then it worked.