Re: FreeBSD on Virtualbox: No network access
On Dec 8, 2010, at 11:47 PM, Adam Vande More wrote: On Wed, Dec 8, 2010 at 10:34 PM, Weihang Wang weih...@vt.edu wrote: Hi, Could someone tell me how to enable Bridge mode? Seems like you already know how since you do it below. I just change the network settings of my virtual machine, change it to bridged mode. I also select the eth0, which is the physical interface of my system. Then in my virtual machine, I add one line: ifconfig_em0=DHCP in /etc/rc.conf file. I have changed each of the five virtual interfaces Intel and ..., but I could not get network access. ifconfig_em0=DHCP would only work for the intel adapters, not amd ones. If I use NAT mode, one of these five interfaces works fine. But now I do need the Bridged mode because one of my machine would be a server in my experiment. You do have a DHCP server correct? What happens when you do dhclient em0? Does bridged networking work with a different guest OS as maybe it's some problem with your host. -- Adam Vande More Hi, I do not configure a DHCP server. When my FreeBSD 6.0 is booting, there are several DHCPDISCOVERY messages, finally it shows no DHCPOFFER received. Do I need to configure a DHCP server myself? If I need a DHCP server? Where it should be? Now I only have one test machine, Ubuntu as the host OS, two VMs (both are FreeBSD 6.0) on this machine. I want this two VMs communicate with each other. Just go back to the DHCP stuff, when I use NAT mode, the guest OS FreeBSD 6.0 could get DHCPOFFER successfully. Who is the DHCP server then? When running dhclien em0, the results are similar to the DHCPDISCOVER results during booting. No DHCPOFFERS received. Thanks, W.W. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Thu, Dec 9, 2010 at 1:48 PM, Weihang Wang weih...@vt.edu wrote: Hi, I do not configure a DHCP server. When my FreeBSD 6.0 is booting, there are several DHCPDISCOVERY messages, finally it shows no DHCPOFFER received. Do I need to configure a DHCP server myself? If I need a DHCP server? Where it should be? Now I only have one test machine, Ubuntu as the host OS, two VMs (both are FreeBSD 6.0) on this machine. I want this two VMs communicate with each other. Just go back to the DHCP stuff, when I use NAT mode, the guest OS FreeBSD 6.0 could get DHCPOFFER successfully. Who is the DHCP server then? When running dhclien em0, the results are similar to the DHCPDISCOVER results during booting. No DHCPOFFERS received. It would appear that Ubuntu has not correctly installed the bridging adapter. Did you check out the links I provided on setting up a bridging device on Ubuntu w/ vBox? They worked for me, I set up an Ubuntu VM and in the VM setup a test VM of vBox to boot fbsd (8.1 in my case). NOTE: I do not recoomend setting up a VM within a VM, I did it strictly as a test to boot and get network access. Which it did. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Dec 9, 2010, at 3:40 PM, Chris Brennan wrote: On Thu, Dec 9, 2010 at 1:48 PM, Weihang Wang weih...@vt.edu wrote: Hi, I do not configure a DHCP server. When my FreeBSD 6.0 is booting, there are several DHCPDISCOVERY messages, finally it shows no DHCPOFFER received. Do I need to configure a DHCP server myself? If I need a DHCP server? Where it should be? Now I only have one test machine, Ubuntu as the host OS, two VMs (both are FreeBSD 6.0) on this machine. I want this two VMs communicate with each other. Just go back to the DHCP stuff, when I use NAT mode, the guest OS FreeBSD 6.0 could get DHCPOFFER successfully. Who is the DHCP server then? When running dhclien em0, the results are similar to the DHCPDISCOVER results during booting. No DHCPOFFERS received. It would appear that Ubuntu has not correctly installed the bridging adapter. Did you check out the links I provided on setting up a bridging device on Ubuntu w/ vBox? They worked for me, I set up an Ubuntu VM and in the VM setup a test VM of vBox to boot fbsd (8.1 in my case). NOTE: I do not recoomend setting up a VM within a VM, I did it strictly as a test to boot and get network access. Which it did. __ Hi, I am sorry I don't know which page you refer to... I am confusing now cause first, I don't know which mode could be best for my needs. What I need is two VMs on a real machine, these two VMs could communicate with each other. It seems bridged mode is suitable here. But there is no network access for bridged mode. BTW, when I use NAT mode, two VMs get the same IP address, and they could not get to each other. Thanks, W.W. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Thu, Dec 9, 2010 at 12:48 PM, Weihang Wang weih...@vt.edu wrote: I do not configure a DHCP server. When my FreeBSD 6.0 is booting, there are several DHCPDISCOVERY messages, finally it shows no DHCPOFFER received. Do I need to configure a DHCP server myself? If I need a DHCP server? Bridged networking makes the guest behave like another physical installation with respect to networking. If your network doesn't have a DHCP server then for DHCP to work one is required. You don't need DHCP for networking however, you could simply assign static addresses. Where it should be? Now I only have one test machine, Ubuntu as the host OS, two VMs (both are FreeBSD 6.0) on this machine. I want this two VMs communicate with each other. Why are you using such an old version of FreeBSD? Just go back to the DHCP stuff, when I use NAT mode, the guest OS FreeBSD 6.0 could get DHCPOFFER successfully. Who is the DHCP server then? In NAT mode, VirtualBox provides it's internal DHCP server. When running dhclien em0, the results are similar to the DHCPDISCOVER results during booting. No DHCPOFFERS received. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Thu, Dec 9, 2010 at 4:55 PM, Adam Vande More amvandem...@gmail.comwrote: On Thu, Dec 9, 2010 at 12:48 PM, Weihang Wang weih...@vt.edu wrote: Clipped for brevity. https://help.*ubuntu*.com/community/VirtualBox/Networking https://wiki.*ubuntu*.com/VirtualBox http://ubuntuforums.org/showthread.php?t=667952 http://www.virtualbox.org/manual/ch06.html#id2741763 Here are the links that should help you, I *suggested* you read them this time and learn how to install, configure and use the bridging adapter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Dec 9, 2010, at 4:55 PM, Adam Vande More wrote: On Thu, Dec 9, 2010 at 12:48 PM, Weihang Wang weih...@vt.edu wrote: I do not configure a DHCP server. When my FreeBSD 6.0 is booting, there are several DHCPDISCOVERY messages, finally it shows no DHCPOFFER received. Do I need to configure a DHCP server myself? If I need a DHCP server? Bridged networking makes the guest behave like another physical installation with respect to networking. If your network doesn't have a DHCP server then for DHCP to work one is required. You don't need DHCP for networking however, you could simply assign static addresses. Where it should be? Now I only have one test machine, Ubuntu as the host OS, two VMs (both are FreeBSD 6.0) on this machine. I want this two VMs communicate with each other. Why are you using such an old version of FreeBSD? Just go back to the DHCP stuff, when I use NAT mode, the guest OS FreeBSD 6.0 could get DHCPOFFER successfully. Who is the DHCP server then? In NAT mode, VirtualBox provides it's internal DHCP server. When running dhclien em0, the results are similar to the DHCPDISCOVER results during booting. No DHCPOFFERS received. Hi, I have to use FreeBSD 6.0 because the network stack I will test is only based on 6.0. BTW, I am using internal networking mode now, these two VMs could communicate with each other now. This mode seems could satisfy my needs, because my VMs only need to communicate with each other, not with the outside world. Thank you so much for help. Best, W.W. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Dec 9, 2010, at 5:48 PM, Chris Brennan wrote: On Thu, Dec 9, 2010 at 4:55 PM, Adam Vande More amvandem...@gmail.comwrote: On Thu, Dec 9, 2010 at 12:48 PM, Weihang Wang weih...@vt.edu wrote: Clipped for brevity. https://help.*ubuntu*.com/community/VirtualBox/Networking https://wiki.*ubuntu*.com/VirtualBox http://ubuntuforums.org/showthread.php?t=667952 http://www.virtualbox.org/manual/ch06.html#id2741763 Here are the links that should help you, I *suggested* you read them this time and learn how to install, configure and use the bridging adapter. Hi, I do read these documents already. Anyway, I have changed the mode the internal networking mode, it works fine.Thank you so much for your help. Best, W.W.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Dec 3, 2010, at 4:25 AM, Timm Wimmers wrote: Am Freitag, den 03.12.2010, 00:33 -0500 schrieb Weihang Wang: Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! In most cases it is better to use bridge mode. In NAT mode your VM get a private subnet and other devices in your network can't find your VM, because the VM is behind (or encapsulated in) your HOST (as like as your HOST is behind your router to the internet). This can work if you define routes, but bridging is mostly easier. In Bridge mode your VM acts like any other machine in your network and will get an IP-Adress from your DHCP server (if you use DHCP). -- Timm [1] HSOT = your Ubuntu Workstation Hi, Could someone tell me how to enable Bridge mode? I just change the network settings of my virtual machine, change it to bridged mode. I also select the eth0, which is the physical interface of my system. Then in my virtual machine, I add one line: ifconfig_em0=DHCP in /etc/rc.conf file. I have changed each of the five virtual interfaces Intel and ..., but I could not get network access. If I use NAT mode, one of these five interfaces works fine. But now I do need the Bridged mode because one of my machine would be a server in my experiment. Hope to hear from you. Thanks in advance. Best, W.W.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Wed, Dec 8, 2010 at 10:34 PM, Weihang Wang weih...@vt.edu wrote: Hi, Could someone tell me how to enable Bridge mode? Seems like you already know how since you do it below. I just change the network settings of my virtual machine, change it to bridged mode. I also select the eth0, which is the physical interface of my system. Then in my virtual machine, I add one line: ifconfig_em0=DHCP in /etc/rc.conf file. I have changed each of the five virtual interfaces Intel and ..., but I could not get network access. ifconfig_em0=DHCP would only work for the intel adapters, not amd ones. If I use NAT mode, one of these five interfaces works fine. But now I do need the Bridged mode because one of my machine would be a server in my experiment. You do have a DHCP server correct? What happens when you do dhclient em0? Does bridged networking work with a different guest OS as maybe it's some problem with your host. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Wed, Dec 8, 2010 at 11:34 PM, Weihang Wang weih...@vt.edu wrote: Hi, Could someone tell me how to enable Bridge mode? I just change the network settings of my virtual machine, change it to bridged mode. I also select the eth0, which is the physical interface of my system. Then in my virtual machine, I add one line: ifconfig_em0=DHCP in /etc/rc.conf file. I have changed each of the five virtual interfaces Intel and ..., but I could not get network access. If I use NAT mode, one of these five interfaces works fine. But now I do need the Bridged mode because one of my machine would be a server in my experiment. Hope to hear from you. Thanks in advance. Weihang, Basically what you want to do is select bridging in your vBox settings for your VM. Then select your real system's ethernet adapter, expand the little drop down below that and it will allow you to choose which vNIC you want. I choose the Intel 82545EM device which gives me an em0 vNIC. in my FreeBSD VM I have the following three lines pertaining to setting up my network sshd_enable=YES ifconfig_em0=inet 192.168.0.20 netmask 255.255.255.0 defaultrouter=192.168.0.1 hostname=freebsd-bsd.xaerolimit.net and of course, that hostname does resolve on my lan, but that's not what this e-mail is about. Hope this helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On 03/12/2010 09:25, Timm Wimmers wrote: Am Freitag, den 03.12.2010, 00:33 -0500 schrieb Weihang Wang: Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! In most cases it is better to use bridge mode. In NAT mode your VM get a private subnet and other devices in your network can't find your VM, because the VM is behind (or encapsulated in) your HOST (as like as your HOST is behind your router to the internet). This can work if you define routes, but bridging is mostly easier. In Bridge mode your VM acts like any other machine in your network and will get an IP-Adress from your DHCP server (if you use DHCP). Hmmm I don't know about bridge mode being appropriate in most cases. NAT and bridge modes are useful in different circumstances * NAT mode means that your VMs are not exposed to incoming connections on the net. * Bridge mode means that the VMs can run network services for users on other machines. Which one of those you prefer depends very much on how you're using the VMs. Eg. for a dev playground and for local testing, NAT looks like a better idea. Now, I run VirtualBox on my Mac with FreeBSD (inter alia) as a guest OS. Your setup may differ, but I find NAT mode to be the best choice. In addition to the considerations above, I also see: * In NAT mode, the FreeBSD guest is insulated from how the Mac connects to the network. Switching between wired or wireless networking, or even using a 3G dongle just works as far as the FreeBSD guest is concerned. * Similarly if the MAC gets a new IP when switching between different networks and DHCP servers, the guest OS just doesn't care. You don't need to worry about configuring routing and so forth in the guests: just use DHCP for the i/f, and it all works automagically. Actually, I generally enable two network interfaces for unixoid guests (ie. capable of running sshd) -- set to NAT and vboxnet0. This means I can ssh into local guest OSes from a Terminal.app session, which I find more convenient than logging in via the console. Again, it's all configured effortlessly with DHCP. My only complaint is that IPv6 doesn't work in these modes, but I can live with that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD on Virtualbox: No network access
Hi, Thank you so much for your advices. I am using NAT mode now. Just as you said, there is no need to configure DHCP in /etc/rc.conf. I just choose the Intel PRO/1000 T Server as my virtual network interface. It works well. Thank you very much. : ) Best, W.W. On Dec 4, 2010, at 8:32 AM, Matthew Seaman wrote: On 03/12/2010 09:25, Timm Wimmers wrote: Am Freitag, den 03.12.2010, 00:33 -0500 schrieb Weihang Wang: Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! In most cases it is better to use bridge mode. In NAT mode your VM get a private subnet and other devices in your network can't find your VM, because the VM is behind (or encapsulated in) your HOST (as like as your HOST is behind your router to the internet). This can work if you define routes, but bridging is mostly easier. In Bridge mode your VM acts like any other machine in your network and will get an IP-Adress from your DHCP server (if you use DHCP). Hmmm I don't know about bridge mode being appropriate in most cases. NAT and bridge modes are useful in different circumstances * NAT mode means that your VMs are not exposed to incoming connections on the net. * Bridge mode means that the VMs can run network services for users on other machines. Which one of those you prefer depends very much on how you're using the VMs. Eg. for a dev playground and for local testing, NAT looks like a better idea. Now, I run VirtualBox on my Mac with FreeBSD (inter alia) as a guest OS. Your setup may differ, but I find NAT mode to be the best choice. In addition to the considerations above, I also see: * In NAT mode, the FreeBSD guest is insulated from how the Mac connects to the network. Switching between wired or wireless networking, or even using a 3G dongle just works as far as the FreeBSD guest is concerned. * Similarly if the MAC gets a new IP when switching between different networks and DHCP servers, the guest OS just doesn't care. You don't need to worry about configuring routing and so forth in the guests: just use DHCP for the i/f, and it all works automagically. Actually, I generally enable two network interfaces for unixoid guests (ie. capable of running sshd) -- set to NAT and vboxnet0. This means I can ssh into local guest OSes from a Terminal.app session, which I find more convenient than logging in via the console. Again, it's all configured effortlessly with DHCP. My only complaint is that IPv6 doesn't work in these modes, but I can live with that. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
Am Freitag, den 03.12.2010, 00:33 -0500 schrieb Weihang Wang: Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! In most cases it is better to use bridge mode. In NAT mode your VM get a private subnet and other devices in your network can't find your VM, because the VM is behind (or encapsulated in) your HOST (as like as your HOST is behind your router to the internet). This can work if you define routes, but bridging is mostly easier. In Bridge mode your VM acts like any other machine in your network and will get an IP-Adress from your DHCP server (if you use DHCP). -- Timm [1] HSOT = your Ubuntu Workstation ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On Fri, Dec 3, 2010 at 12:33 AM, Weihang Wang weih...@vt.edu wrote: Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! Best, W.W. Good, glad it works for you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
03.12.2010 04:03, Weihang Wang wrote: I am running FreeBSD 8.1 in Virtualbox OSE as a guest OS on Ubuntu. Now the guest OS does not have network access. When using ifconfig, the virtual ethernet card le0 (when using PCI II) or pcn0 (when using PCnet FAST III) has no IP address. I have configured ifconfig_le0/pcn0=DHCP in /etc/rc.conf. But it still has no network access. In the virtualbox, I choose the networking mode Bridged or NAT, they don't work, either. I found in the virtualbox the name of this virtual network interface is eth0. But when i use ifconfig, there is no eth0 in this operating system. I am a little mass and struggling in this problem several days and could not find a solution from the Internet. Hope who have ideas about this could give me some possible solutions. Thanks in advance. If you do use amd64 version of freebsd try not to stick to the hardware from the ISA days. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
On 12/02/2010 09:03 PM, Weihang Wang wrote: Now the guest OS does not have network access. When using ifconfig, the virtual ethernet card le0 (when using PCI II) or pcn0 (when using PCnet FAST III) has no IP address. Have you attempted to select different available network interfaces? I have a similar issue when I first started using virtualbox, and it was due to not having the correct interface drop-down option from within the Settings tab on the VirtualBox Gui. (Where all the VMs are listed.) -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Virtualbox: No network access
Hi Martes, I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option Intel PRO/1000 T Server and in NAT mode, it works now Thank you so much, you do me a great favor!! Hope this also works for Chris! Best, W.W. On Dec 2, 2010, at 11:55 PM, Martes G Wigglesworth wrote: On 12/02/2010 09:03 PM, Weihang Wang wrote: Now the guest OS does not have network access. When using ifconfig, the virtual ethernet card le0 (when using PCI II) or pcn0 (when using PCnet FAST III) has no IP address. Have you attempted to select different available network interfaces? I have a similar issue when I first started using virtualbox, and it was due to not having the correct interface drop-down option from within the Settings tab on the VirtualBox Gui. (Where all the VMs are listed.) -- Respectfully, Martes G Wigglesworth M. G. Wigglesworth Holdings, LLC www.mgwigglesworth.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
