Hello Alvaro,
Thanks for your help. I changed the Vagrantfile as you suggested and I got
the following output:
1
172.17.8.101
But here is the output of ifconfig:
core@core-01 ~ $ ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.16.22.178 netmask 255.255.255.0 broadcast 172.16.22.255
inet6 fe80::20c:29ff:fe53:9481 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:53:94:81 txqueuelen 1000 (Ethernet)
RX packets 465 bytes 61721 (60.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 325 bytes 49313 (48.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet *172.17.8.168* netmask 255.255.255.0 broadcast 172.17.8.255
inet6 fe80::20c:29ff:fe53:948b prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:53:94:8b txqueuelen 1000 (Ethernet)
RX packets 5 bytes 892 (892.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 32 bytes 2600 (2.5 KiB)
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 0 (Local Loopback)
RX packets 200 bytes 15089 (14.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 200 bytes 15089 (14.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I don't know where the .168 came from, but it didn't come from the
Vagrantfile! I can't tell, however, whether the problem lies in VMware
Fusion or in the Vagrant VMware plugin.
On Monday, January 19, 2015 at 3:37:32 PM UTC-7, Alvaro Miranda Aguilera
wrote:
>
>
> On Tue, Jan 20, 2015 at 11:07 AM, Tony Perez <[email protected]
> <javascript:>> wrote:
>
>> ip = "172.17.8.#{i+100}"
>> config.vm.network :private_network, ip: ip
>>
>
>
> Try to replace this
>
> ip = "172.17.8.#{i+100}"
> config.vm.network :private_network, ip: ip
>
> with this:
>
> ip = "172.17.8.#{i+100}"
> puts i
> puts ip
> config.vm.network :private_network, ip: ip
>
>
> if the correct value is shown in the command line, then the vagrant logic
> is fine, and the issue is coming from vmvware.
> if the incorrect value is shown on the first run, then something is wrong
> inside the Vagrantfile
>
> this is a basic/simple approach, but will help to see where the error is
> coming from.
>
>
> alvaro.
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
