Bridged Networking Doesn't Seem to Work

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Bridged Networking Doesn't Seem to Work

scervera
I am relatively new to Vagrant. Configuration of bridged networking seems painfully simple, and yet I can't seem to get it to work. I am trying to access my server from other hosts on my network, so I need the bridged networking option vs host only. After vagrant up, I ssh into the VMs no problem. When I run ifconfig it shows the en0 has an IP address of 10.0.2.15. I have confirmed that DHCP is running on my network and that my host is getting an address. I have tried giving my host both a static and dynamic address. I have tried to put in a static address into my Vagrantfile, but that has not worked.

Here is my current Vagrant file. I would appreciate any help that can be offered to fix this.

Thx
Steve


Vagrant::Config.run do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  config.vm.define :web do |web_config|
web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory", "512"]
web_config.vm.box = "ubuntu1204_ruby193"
web_config.vm.host_name = "web"
web_config.vm.forward_port 22, 2222, :auto => true
web_config.vm.forward_port 80, 4567, :auto => true
web_config.vm.network :bridged, :bridge => "en0: Ethernet"
web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end

  config.vm.define :stage do |stage_config|
stage_config.vm.customize ["modifyvm", :id, "--name", "stage", "--memory", "512"]
stage_config.vm.box = "ubuntu1204_ruby193"
stage_config.vm.host_name = "stage"
stage_config.vm.forward_port 22, 2222, :auto => true
stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end
end


--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

Daniel Kuffner
ifconfig should show you two network devices. Eth1 is the bridged network and should have a IP adresse of you external network. As far as I know there is possibility to assign a static ip adress to the bridged network interface.

regards,
Daniel



On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
I am relatively new to Vagrant. Configuration of bridged networking seems painfully simple, and yet I can't seem to get it to work. I am trying to access my server from other hosts on my network, so I need the bridged networking option vs host only. After vagrant up, I ssh into the VMs no problem. When I run ifconfig it shows the en0 has an IP address of 10.0.2.15. I have confirmed that DHCP is running on my network and that my host is getting an address. I have tried giving my host both a static and dynamic address. I have tried to put in a static address into my Vagrantfile, but that has not worked.

Here is my current Vagrant file. I would appreciate any help that can be offered to fix this.

Thx
Steve


Vagrant::Config.run do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  config.vm.define :web do |web_config|
web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory", "512"]
web_config.vm.box = "ubuntu1204_ruby193"
web_config.vm.host_name = "web"
web_config.vm.forward_port 22, 2222, :auto => true
web_config.vm.forward_port 80, 4567, :auto => true
web_config.vm.network :bridged, :bridge => "en0: Ethernet"
web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end

  config.vm.define :stage do |stage_config|
stage_config.vm.customize ["modifyvm", :id, "--name", "stage", "--memory", "512"]
stage_config.vm.box = "ubuntu1204_ruby193"
stage_config.vm.host_name = "stage"
stage_config.vm.forward_port 22, 2222, :auto => true
stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end
end


--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

scervera
When I run ifconfig command I am shown only en0 (10.0.2.15) and the loopback address. It doesn't appear that there is an eth1. Though when I look at the GUI in VirtualBox, I am showing two adapters. Adapter 2 is showing bridged. But there is no IP address assigned by DHCP and it doesn't show up in ipconfig.

vagrant@web:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:49:be:f3  
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe49:bef3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:382 errors:0 dropped:0 overruns:0 frame:0
          TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:40011 (40.0 KB)  TX bytes:34314 (34.3 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)


On Sunday, February 3, 2013 8:18:07 AM UTC-5, Daniel Kuffner wrote:
ifconfig should show you two network devices. Eth1 is the bridged network and should have a IP adresse of you external network. As far as I know there is possibility to assign a static ip adress to the bridged network interface.

regards,
Daniel



On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
I am relatively new to Vagrant. Configuration of bridged networking seems painfully simple, and yet I can't seem to get it to work. I am trying to access my server from other hosts on my network, so I need the bridged networking option vs host only. After vagrant up, I ssh into the VMs no problem. When I run ifconfig it shows the en0 has an IP address of 10.0.2.15. I have confirmed that DHCP is running on my network and that my host is getting an address. I have tried giving my host both a static and dynamic address. I have tried to put in a static address into my Vagrantfile, but that has not worked.

Here is my current Vagrant file. I would appreciate any help that can be offered to fix this.

Thx
Steve


Vagrant::Config.run do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  config.vm.define :web do |web_config|
web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory", "512"]
web_config.vm.box = "ubuntu1204_ruby193"
web_config.vm.host_name = "web"
web_config.vm.forward_port 22, 2222, :auto => true
web_config.vm.forward_port 80, 4567, :auto => true
web_config.vm.network :bridged, :bridge => "en0: Ethernet"
web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end

  config.vm.define :stage do |stage_config|
stage_config.vm.customize ["modifyvm", :id, "--name", "stage", "--memory", "512"]
stage_config.vm.box = "ubuntu1204_ruby193"
stage_config.vm.host_name = "stage"
stage_config.vm.forward_port 22, 2222, :auto => true
stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
  end
end


--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

Mike
Where'd you get your basebox?

On Sun, Feb 3, 2013 at 9:25 AM,  <[hidden email]> wrote:

> When I run ifconfig command I am shown only en0 (10.0.2.15) and the loopback
> address. It doesn't appear that there is an eth1. Though when I look at the
> GUI in VirtualBox, I am showing two adapters. Adapter 2 is showing bridged.
> But there is no IP address assigned by DHCP and it doesn't show up in
> ipconfig.
>
> vagrant@web:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 08:00:27:49:be:f3
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::a00:27ff:fe49:bef3/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:382 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:40011 (40.0 KB)  TX bytes:34314 (34.3 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)
>
>
> On Sunday, February 3, 2013 8:18:07 AM UTC-5, Daniel Kuffner wrote:
>>
>> ifconfig should show you two network devices. Eth1 is the bridged network
>> and should have a IP adresse of you external network. As far as I know there
>> is possibility to assign a static ip adress to the bridged network
>> interface.
>>
>> regards,
>> Daniel
>>
>>
>>
>> On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
>>>
>>> I am relatively new to Vagrant. Configuration of bridged networking seems
>>> painfully simple, and yet I can't seem to get it to work. I am trying to
>>> access my server from other hosts on my network, so I need the bridged
>>> networking option vs host only. After vagrant up, I ssh into the VMs no
>>> problem. When I run ifconfig it shows the en0 has an IP address of
>>> 10.0.2.15. I have confirmed that DHCP is running on my network and that my
>>> host is getting an address. I have tried giving my host both a static and
>>> dynamic address. I have tried to put in a static address into my
>>> Vagrantfile, but that has not worked.
>>>
>>> Here is my current Vagrant file. I would appreciate any help that can be
>>> offered to fix this.
>>>
>>> Thx
>>> Steve
>>>
>>>
>>> Vagrant::Config.run do |config|
>>>   # All Vagrant configuration is done here. The most common configuration
>>>   # options are documented and commented below. For a complete reference,
>>>   # please see the online documentation at vagrantup.com.
>>>
>>>   config.vm.define :web do |web_config|
>>> web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory",
>>> "512"]
>>> web_config.vm.box = "ubuntu1204_ruby193"
>>> web_config.vm.host_name = "web"
>>> web_config.vm.forward_port 22, 2222, :auto => true
>>> web_config.vm.forward_port 80, 4567, :auto => true
>>> web_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>>
>>>   config.vm.define :stage do |stage_config|
>>> stage_config.vm.customize ["modifyvm", :id, "--name", "stage",
>>> "--memory", "512"]
>>> stage_config.vm.box = "ubuntu1204_ruby193"
>>> stage_config.vm.host_name = "stage"
>>> stage_config.vm.forward_port 22, 2222, :auto => true
>>> stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>> end
>>>
>>>
> --
> 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 [hidden email].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.


Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

scervera
I got one from vagrantbox.es and just downloaded one from https://github.com/mitchellh/vagrant/wiki/Available-Vagrant-Boxes.

Do you have a Vagrantbox running with bridged networking working?

On Sunday, February 3, 2013 2:08:07 PM UTC-5, miketheman wrote:
Where'd you get your basebox?

On Sun, Feb 3, 2013 at 9:25 AM,  <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ptjyXdSEzXoJ">scer...@...> wrote:

> When I run ifconfig command I am shown only en0 (10.0.2.15) and the loopback
> address. It doesn't appear that there is an eth1. Though when I look at the
> GUI in VirtualBox, I am showing two adapters. Adapter 2 is showing bridged.
> But there is no IP address assigned by DHCP and it doesn't show up in
> ipconfig.
>
> vagrant@web:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 08:00:27:49:be:f3
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::a00:27ff:fe49:bef3/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:382 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:40011 (40.0 KB)  TX bytes:34314 (34.3 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)
>
>
> On Sunday, February 3, 2013 8:18:07 AM UTC-5, Daniel Kuffner wrote:
>>
>> ifconfig should show you two network devices. Eth1 is the bridged network
>> and should have a IP adresse of you external network. As far as I know there
>> is possibility to assign a static ip adress to the bridged network
>> interface.
>>
>> regards,
>> Daniel
>>
>>
>>
>> On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
>>>
>>> I am relatively new to Vagrant. Configuration of bridged networking seems
>>> painfully simple, and yet I can't seem to get it to work. I am trying to
>>> access my server from other hosts on my network, so I need the bridged
>>> networking option vs host only. After vagrant up, I ssh into the VMs no
>>> problem. When I run ifconfig it shows the en0 has an IP address of
>>> 10.0.2.15. I have confirmed that DHCP is running on my network and that my
>>> host is getting an address. I have tried giving my host both a static and
>>> dynamic address. I have tried to put in a static address into my
>>> Vagrantfile, but that has not worked.
>>>
>>> Here is my current Vagrant file. I would appreciate any help that can be
>>> offered to fix this.
>>>
>>> Thx
>>> Steve
>>>
>>>
>>> Vagrant::Config.run do |config|
>>>   # All Vagrant configuration is done here. The most common configuration
>>>   # options are documented and commented below. For a complete reference,
>>>   # please see the online documentation at vagrantup.com.
>>>
>>>   config.vm.define :web do |web_config|
>>> web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory",
>>> "512"]
>>> web_config.vm.box = "ubuntu1204_ruby193"
>>> web_config.vm.host_name = "web"
>>> web_config.vm.forward_port 22, 2222, :auto => true
>>> web_config.vm.forward_port 80, 4567, :auto => true
>>> web_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>>
>>>   config.vm.define :stage do |stage_config|
>>> stage_config.vm.customize ["modifyvm", :id, "--name", "stage",
>>> "--memory", "512"]
>>> stage_config.vm.box = "ubuntu1204_ruby193"
>>> stage_config.vm.host_name = "stage"
>>> stage_config.vm.forward_port 22, 2222, :auto => true
>>> stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>> end
>>>
>>>
> --
> 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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ptjyXdSEzXoJ">vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

Mike
Are you saying a with the base box fom vagrantup.com you are not getting bridged networking?
Run it in debug mode and gist/paste in your Vagrantfile and output, and send links to those.

On Thursday, February 7, 2013, wrote:
I got one from vagrantbox.es and just downloaded one from https://github.com/mitchellh/vagrant/wiki/Available-Vagrant-Boxes.

Do you have a Vagrantbox running with bridged networking working?

On Sunday, February 3, 2013 2:08:07 PM UTC-5, miketheman wrote:
Where'd you get your basebox?

On Sun, Feb 3, 2013 at 9:25 AM,  <[hidden email]> wrote:

> When I run ifconfig command I am shown only en0 (10.0.2.15) and the loopback
> address. It doesn't appear that there is an eth1. Though when I look at the
> GUI in VirtualBox, I am showing two adapters. Adapter 2 is showing bridged.
> But there is no IP address assigned by DHCP and it doesn't show up in
> ipconfig.
>
> vagrant@web:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 08:00:27:49:be:f3
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::a00:27ff:fe49:bef3/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:382 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:40011 (40.0 KB)  TX bytes:34314 (34.3 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)
>
>
> On Sunday, February 3, 2013 8:18:07 AM UTC-5, Daniel Kuffner wrote:
>>
>> ifconfig should show you two network devices. Eth1 is the bridged network
>> and should have a IP adresse of you external network. As far as I know there
>> is possibility to assign a static ip adress to the bridged network
>> interface.
>>
>> regards,
>> Daniel
>>
>>
>>
>> On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
>>>
>>> I am relatively new to Vagrant. Configuration of bridged networking seems
>>> painfully simple, and yet I can't seem to get it to work. I am trying to
>>> access my server from other hosts on my network, so I need the bridged
>>> networking option vs host only. After vagrant up, I ssh into the VMs no
>>> problem. When I run ifconfig it shows the en0 has an IP address of
>>> 10.0.2.15. I have confirmed that DHCP is running on my network and that my
>>> host is getting an address. I have tried giving my host both a static and
>>> dynamic address. I have tried to put in a static address into my
>>> Vagrantfile, but that has not worked.
>>>
>>> Here is my current Vagrant file. I would appreciate any help that can be
>>> offered to fix this.
>>>
>>> Thx
>>> Steve
>>>
>>>
>>> Vagrant::Config.run do |config|
>>>   # All Vagrant configuration is done here. The most common configuration
>>>   # options are documented and commented below. For a complete reference,
>>>   # please see the online documentation at vagrantup.com.
>>>
>>>   config.vm.define :web do |web_config|
>>> web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory",
>>> "512"]
>>> web_config.vm.box = "ubuntu1204_ruby193"
>>> web_config.vm.host_name = "web"
>>> web_config.vm.forward_port 22, 2222, :auto => true
>>> web_config.vm.forward_port 80, 4567, :auto => true
>>> web_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>>
>>>   config.vm.define :stage do |stage_config|
>>> stage_config.vm.customize ["modifyvm", :id, "--name", "stage",
>>> "--memory", "512"]
>>> stage_config.vm.box = "ubuntu1204_ruby193"
>>> stage_config.vm.host_name = "stage"
>>> stage_config.vm.forward_port 22, 2222, :auto => true
>>> stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>> end
>>>
>>>
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
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 <a href="javascript:_e({}, &#39;cvml&#39;, &#39;vagrant-up%2Bunsubscribe@googlegroups.com&#39;);" target="_blank">vagrant-up+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Bridged Networking Doesn't Seem to Work

scervera
That is correct. I discovered what the issue is. Please see this thread:

 https://github.com/mitchellh/vagrant/issues/1351

The issue reportedly manifests itself specifically with Ubuntu VMs on Mac OS X 10.8 hosts. I have not verified this with any other type of VM. I can only verify that the fix works and is pretty simple.

It is recommended to edit the /etc/udev/rules.d/70-persistent-net.rules or delete the rules altogether because Linux will rebuild them on the next boot. I have confirmed that deleting the rules AFTER the Mac address is changed in VirtualBox works on both the NAT interface (adapter 1) and the Bridged interface (adapter 2).


On Friday, February 8, 2013 4:22:21 AM UTC-8, miketheman wrote:
Are you saying a with the base box fom vagrantup.com you are not getting bridged networking?
Run it in debug mode and gist/paste in your Vagrantfile and output, and send links to those.

On Thursday, February 7, 2013, wrote:
I got one from vagrantbox.es and just downloaded one from https://github.com/mitchellh/vagrant/wiki/Available-Vagrant-Boxes.

Do you have a Vagrantbox running with bridged networking working?

On Sunday, February 3, 2013 2:08:07 PM UTC-5, miketheman wrote:
Where'd you get your basebox?

On Sun, Feb 3, 2013 at 9:25 AM,  <[hidden email]> wrote:

> When I run ifconfig command I am shown only en0 (10.0.2.15) and the loopback
> address. It doesn't appear that there is an eth1. Though when I look at the
> GUI in VirtualBox, I am showing two adapters. Adapter 2 is showing bridged.
> But there is no IP address assigned by DHCP and it doesn't show up in
> ipconfig.
>
> vagrant@web:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 08:00:27:49:be:f3
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::a00:27ff:fe49:bef3/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:382 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:40011 (40.0 KB)  TX bytes:34314 (34.3 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)
>
>
> On Sunday, February 3, 2013 8:18:07 AM UTC-5, Daniel Kuffner wrote:
>>
>> ifconfig should show you two network devices. Eth1 is the bridged network
>> and should have a IP adresse of you external network. As far as I know there
>> is possibility to assign a static ip adress to the bridged network
>> interface.
>>
>> regards,
>> Daniel
>>
>>
>>
>> On Sunday, February 3, 2013 6:47:10 AM UTC+1, [hidden email] wrote:
>>>
>>> I am relatively new to Vagrant. Configuration of bridged networking seems
>>> painfully simple, and yet I can't seem to get it to work. I am trying to
>>> access my server from other hosts on my network, so I need the bridged
>>> networking option vs host only. After vagrant up, I ssh into the VMs no
>>> problem. When I run ifconfig it shows the en0 has an IP address of
>>> 10.0.2.15. I have confirmed that DHCP is running on my network and that my
>>> host is getting an address. I have tried giving my host both a static and
>>> dynamic address. I have tried to put in a static address into my
>>> Vagrantfile, but that has not worked.
>>>
>>> Here is my current Vagrant file. I would appreciate any help that can be
>>> offered to fix this.
>>>
>>> Thx
>>> Steve
>>>
>>>
>>> Vagrant::Config.run do |config|
>>>   # All Vagrant configuration is done here. The most common configuration
>>>   # options are documented and commented below. For a complete reference,
>>>   # please see the online documentation at vagrantup.com.
>>>
>>>   config.vm.define :web do |web_config|
>>> web_config.vm.customize ["modifyvm", :id, "--name", "web", "--memory",
>>> "512"]
>>> web_config.vm.box = "ubuntu1204_ruby193"
>>> web_config.vm.host_name = "web"
>>> web_config.vm.forward_port 22, 2222, :auto => true
>>> web_config.vm.forward_port 80, 4567, :auto => true
>>> web_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> web_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>>
>>>   config.vm.define :stage do |stage_config|
>>> stage_config.vm.customize ["modifyvm", :id, "--name", "stage",
>>> "--memory", "512"]
>>> stage_config.vm.box = "ubuntu1204_ruby193"
>>> stage_config.vm.host_name = "stage"
>>> stage_config.vm.forward_port 22, 2222, :auto => true
>>> stage_config.vm.network :bridged, :bridge => "en0: Ethernet"
>>> stage_config.vm.share_folder "puppet", "/etc/puppet", "../mdn_ops"
>>>   end
>>> end
>>>
>>>
> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.