There is no 'vagrant up' that works. It only works when I boot it up via
VirtualBox and disabling the Nat in the VirtualBox config. The output for
the vagrant up that doesn't work is in the link I posted in the original
post.
*This is the ifconfig and route when booted up via vagrant.*
ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:cd:d6:98
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fecd:d698/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:545 errors:0 dropped:0 overruns:0 frame:0
TX packets:377 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:64103 (64.1 KB) TX bytes:48519 (48.5 KB)
eth1 Link encap:Ethernet HWaddr 08:00:27:97:13:b2
inet addr:10.0.24.118 Bcast:10.0.31.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:269 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31544 (31.5 KB) TX bytes:2058 (2.0 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 10.0.2.2 0.0.0.0 UG 100 0 0 eth0
10.0.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.0.24.0 0.0.0.0 255.255.248.0 U 0 0 0 eth1
*ifconfig and route via the VirtualBox bootup with NAT disabled.*
eth0 Link encap:Ethernet HWaddr 08:00:27:97:13:b2
inet addr:10.0.24.118 Bcast:10.0.31.255 Mask:255.255.248.0
inet6 addr: fe80::a00:27ff:fe97:13b2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4098 errors:0 dropped:0 overruns:0 frame:0
TX packets:178 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:481579 (481.5 KB) TX bytes:16702 (16.7 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:172 (172.0 B) TX bytes:172 (172.0 B)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
0.0.0.0 10.0.24.1 0.0.0.0 UG 0 0 0 eth0
10.0.24.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0
By the looks of things, I need to make the vagrant bootup use 10.0.24.1 as
the gateway and not 10.0.2.2 - Is there a way I can do that via the vagrant
file, or do I have to run a script to do it on start up?
On Wednesday, May 21, 2014 5:17:51 PM UTC-4, Alvaro Miranda Aguilera wrote:
>
> can you paste the following output from a vagrant up (which doesn't work)
> and one that work:
>
> ifconfig -a
> route -n
>
>
>
> On Thu, May 22, 2014 at 2:25 AM, synack <[email protected]
> <javascript:>>wrote:
>
>> My current setup is DHCP, eth0 is Nat and eth1 is Bridge. The DHCP
>> address which get's assigned is pingable from my host machine, from other
>> developers machines, but not from our dev boxes, which are on different
>> subnets.
>>
>> If I boot the machine up via VirtualHost and disable the Nat before
>> bootup in the config, it all works fine.
>>
>> On Tuesday, May 20, 2014 4:42:49 PM UTC-4, Alvaro Miranda Aguilera wrote:
>>>
>>> What I recall is, if you network have dhcp, you public network / bridge
>>> will get an IP and you will be able to use that ip to access from other
>>> network
>>>
>>> eth0 will be nat
>>> eth1 will be this bridged network.
>>>
>>> however, if you use public network / bridge for a fixed ip, then you
>>> need to check if the gateway can be set from vagrant, if I remember
>>> correctly at some point wasnt avaliable, and the option was left to do it
>>> on the guest side (say start up script rc.local, etc)
>>>
>>> http://docs.vagrantup.com/v2/networking/public_network.html
>>>
>>> Setup a bridge.
>>>
>>> Let me know if you have questions around this.
>>>
>>> Alvaro
>>>
>>>
>>> On Wed, May 21, 2014 at 4:08 AM, synack <[email protected]> wrote:
>>>
>>>> So in otherwords, vagrant isn't going to work correctly, or is there
>>>> something else I can do to get my dev box, which is on a different subnet,
>>>> to be able to connect/see the vagrant box?
>>>>
>>>> On Thursday, May 15, 2014 7:39:44 PM UTC-4, Alvaro Miranda Aguilera
>>>> wrote:
>>>>>
>>>>> Vagrant requires the first network to be nat, and connect over a
>>>>> forward port to setup the vm.
>>>>>
>>>>> So you have a chicken egg, with no nat on eth0, vagrant can't connect
>>>>> to the guest to setup the 2nd nic.
>>>>>
>>>>> Without the nat, vagrant will be able to only turn the guest on, and
>>>>> shutdown force.
>>>>>
>>>>> Alvaro
>>>>>
>>>>>
>>>>> On Fri, May 16, 2014 at 3:13 AM, synack <[email protected]> wrote:
>>>>>
>>>>>> Hi All
>>>>>>
>>>>>> I'm trying to get a Bridge only setup going, no NAT. I've posted my
>>>>>> question on superuser, but I thought I would post the link here for a
>>>>>> bit
>>>>>> more exposure as I'm really struggling to get this right.
>>>>>>
>>>>>> http://superuser.com/questions/752954/need-to-do-bridged-
>>>>>> adapter-only-in-vagrant-no-nat/753563?noredirect=1#753563
>>>>>>
>>>>>> Thanks for any help
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>>
>>>>>
>>>>> --
>>>> 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.
>>>>
>>>
>>> --
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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.
