Ping/Request OK in LAN, but KO via WAN

7 views

Skip to first unread message

Namlu u

unread,

Nov 1, 2019, 12:22:29 PM11/1/19

to Vagrant

Hi !

Summary:

I have a virtual machine that hosts a website. The site is accessible anywhere in the local network, but neither to computers connected in VPN, nor in WAN interrogation with a correct port forwarding.

Technically:

- Vagrant version: 1.9.1

- Virtualbox version: 5.2.34

- Host and virtual OS: Debian 9

- The website is the default installation of a nginx installed on the host (for diagnostics) and the virtual machine

- Vagrantfile network configuration:

config.vm.network "public_network", bridge: "enp0s25", ip: "192.168.1.201"

- WAN forwarding port:

10080 > 192.168.1.100:80
20180 > 192.168.1.201:80

Tests:

From raspberry in LAN (192.168.1.88)

ping 192.168.1.100 [host] : OK
ping 192.168.1.201[vm] : OK
curl 192.168.1.100 [host] : OK
curl 192.168.1.201 [vm] : OK
curl mydomain:10080 [host] : OK
curl mydomain:20180 [vm] : OK

From my cellphone on VPN (192.168.1.52)
ping 192.168.1.100 [host] : OK
ping 192.168.1.201[vm] : KO
curl 192.168.1.100 [host] : OK
curl 192.168.1.201 [vm] : KO
curl mydomain:10080 [host] : OK
curl mydomain:20180 [vm] : KO

From my cellphone off VPN (192.168.0.3)

curl mydomain:10080 [host] : OK
curl mydomain:20180 [vm] : KO

Conclusion:
I concluded it's my configuration of Vagrant and / or Virtualbox that is problematic. Do you have an idea of what can happen?
Thanks for your help !

More data:

- Vagrant version 1.9.1

- Virtualbox version 5.2.34

- Host and virtual OS Debian 9

- ifconfig on host

enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
ether 00:15:17:e6:94:bc txqueuelen 1000 (Ethernet)
RX packets 10351311 bytes 12044849276 (11.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8569810 bytes 669605531 (638.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xc2b00000-c2b20000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Boucle locale)
RX packets 446809 bytes 51801204 (49.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 446809 bytes 51801204 (49.4 MiB)eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::a00:27ff:fe8d:c04d prefixlen 64 scopeid 0x20<link>
ether 08:00:27:8d:c0:4d txqueuelen 1000 (Ethernet)
RX packets 11678 bytes 15457601 (14.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5981 bytes 423088 (413.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

- ifconfig on virtual machine

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::a00:27ff:fe8d:c04d prefixlen 64 scopeid 0x20<link>
ether 08:00:27:8d:c0:4d txqueuelen 1000 (Ethernet)
RX packets 11678 bytes 15457601 (14.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5981 bytes 423088 (413.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.203 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2a01:e35:2f4d:7aa0:a00:27ff:fe91:41e5 prefixlen 64 scopeid 0x0<global>
inet6 fe80::a00:27ff:fe91:41e5 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:91:41:e5 txqueuelen 1000 (Ethernet)
RX packets 110921 bytes 149988100 (143.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 83255 bytes 8211893 (7.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 8 bytes 540 (540.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 540 (540.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Alvaro Miranda Aguilera

unread,

Nov 25, 2019, 4:14:16 PM11/25/19

to vagra...@googlegroups.com

you may be missing a router in this ip

whats the output of route print ?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6c5c2365-653f-4fba-9096-6bf6bce31bb2%40googlegroups.com.