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!
Related
I have computer with self hosted WireGuard VPN in docker container. When I'm in local network and I'm not connected trough VPN, it's possible to connect with machine using hostname instead ip address:
ssh username#computer_name
but when I'll connect trough VPN from external network then I have to use local ip addresess like
ssh username#xxx.xxx.x.x
because when I try use hostname I receive message:
ssh: Could not resolve hostname computer_name: Unknown host.
The machine with the VPN is the same machine I am trying to connect to via ssh using hostname.
i have network issue from using vm.
This is ifconfig info of vm ubuntu 16.04.
This is ipconfig info of my host machine.
And this is the network settings of vm.
I able to ping vm ip addr from host machine.
I able to ping phone ip addr from vm.
I unable to ping vm ip addr from phone under same network.
Im bad in networking. Any of you have good clue can help me solve this issue?
Appreciate your help & Thanks in advance.
NAT has four different types, and it always works as a firewall. That is why we need UDP traversal and hole-punch sometime. If you want other devices like host and phone build a connection to vm, you need firstly connect from vm to thoses deivces to build a "hole" as a path.
I am setting up a virtual machine via virtual box and after setting it up with an installed ubuntu. I want to be able to ssh on the my machine. I don't know which network setting to use.
I tried to change the adapter1 from NAT to Bridge Adapter, but after doing that I couldn't start my vm disk.
In the VirtualBox settings press network, then adapter 1. Select NAT, then press advanced. Here you can press Port Forwarding and you can add a new port forwarding rule. The default for SSH is 22. I would suggest using localhost IP (127.0.1.1) on for example port 2222 and then you can ssh using the command.
Just to be clear port forward setup:
name 'port-fwd', protocol TCP, host IP 127.0.0.1 host port 2222 guest IP 10.0.2.15 guest port 22. Then you can run:
ssh -p 2222 user#127.0.0.1
In GNS3, I have configured the DHCP pool on the router R1, and I have a vmware VM (Ubuntu 16.04), another router R2 and VPCs are connected to R1. The R2 and VPC can get their IP address without a problem, however, the vmwareVM can't receive the IP address.
Note that:
the station is configured as host-only
the connect a host virtual adapter to this network is checked
the VMware Workstation DHCP Server is turned OFF
No configuration on my local PC Network Connections (DHCP)
Once I type the command dhclient eth0 to get the IP address from dhcp, it freezes and returns nothing and no IP address is assigned.
I want to know what is the problem that causes that issue and how to solve it.
Thank you.
My mistake was in the configuration of my VMware network adapter (VMnet2) in my network adapter in my host.
so in order to get the IP address from the DHCP router: I did the following steps:
Create a virtual network (VMnet2) in the virtual network editor
of VMware.
I checked the "Host-only" option
I checked the
"connect a host virtual adapter to this network" option
Uncheck the "use local DHCP service to distribute IP address to VMs".
Do not change the default configuration of the VMnet from your
network connexion options.
I hope that will help someone has the same issue as me
I in a remote Server (I call it host machine) setup the OpenStack Ocata.
And in the OpenStack Ocata I created a VM, the VM use the Security Group (named allow ping & ssh), which is created by myself:
Now, I can use my Mac ping the VM. but can not ssh connect to the VM.
And in the VM(it's IP is 192.168.1.4 and floating IP is 103.35.202.3), I can ping 192.168.1.1 and 103.35.202.1(the host machine's public IP), but can not ping google.com or other public IP.
Why in my Mac I can ping the VM but can not ssh to it?
Why in the VM I can ping the host machine, but can not ping other public IP?
where is the issue?
Currently the only Egress traffic allowed out is for ICMP. Egress is missing for TCP/UDP. Add in Egress rules for both UDP (should help resolve the DNS issue) and TCP (should resolve the SSH issue.)
After adding in the Egress rules for TCP - test ssh again.
After adding in the Egress rules for UDP - test DNS resolution, if you are still running into issues then you may want to verify the DNS servers used when configuring the network.