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 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 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
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
FreeBSD on Virtualbox: No network access
Hi all, 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. 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: Got an error: Unknown option DDB_CTF
On Dec 2, 2010, at 9:03 PM, Chris Brennan wrote: Hi Chris, Thanks for your kind help. Now I am running FreeBSD on Virtualbox as a guest OS on Ubuntu. But I got some other problems. I have searched on the Internet but could not find a solution work for me. Now the guest OS does 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 don't know whether this is the reason. Hope you could give me some possible ideas on solutions. I will post a new email on this problem, too. Thank you very much. Best, W.W. Greetings Weihang, I've had a simmilar issue, infact. Having one now in my VM that will be fbsd9+zfs (testing stuff for my environment). The only way I can get proper access to the outside world is to allow VMWare or VBox to install the Bridgeing Adapter. In the VM Software, choose the bridging device and then choose any network device the VM offers you (in vBox I have 2 PCINET devices and 3 others, the choice doesn't matter really). When I assigned a static IP to the VM (in my case 192.168.0.20) but it doesn't work (be sure yo set the default route, 'route add gateway IP). The only way I had it working was to let DHCP get an IP at the command line w/ 'dhclient -q DEVICE_NAME'. Anyway, hope that helps a little. Hi, I will try and see whether the same method works for me. If it could not get network access. I am afraid I could not use virtual machine and might go back to run FreeBSD on real hardware. Thank you very much, 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: Got an error: Unknown option DDB_CTF
On Dec 2, 2010, at 9:40 PM, Chris Brennan wrote: Hi, I will try and see whether the same method works for me. If it could not get network access. I am afraid I could not use virtual machine and might go back to run FreeBSD on real hardware. Thank you very much, Best, W.W. Weihang, The whole point of the VM right now is to try and test your software to see if it works on newer versions of FreeBSD. What is the Host OS? Is the Host OS doing anything strange to connect to the network? Did you allow the VM Software to install the bridge Adapter? C- Hi Chris, I use FreeBSD version 8.1, the host OS is Ubuntu 10.10. The host OS could connect to the Internet correctly. This host uses a private IP address. Yes, I allowed the VM software to install the bridge adapter now, when booting there are some msgs no DHCP offers received. Actually I am a little confused where the DHCP server is, do I need to install a DHCP server? Also, do I need to add that line ifconfig_le0/pcn0=DHCP in /etc/rc.conf? I am also don't understand how to set the static IP address since when setting a static IP address, we should have a router interface address, right? But now it's only a virtual machine running on a real machine, how can we do that? Thank you so much for your help. I am sorry for bring you so much trouble. 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: Got an error: Unknown option DDB_CTF
On Dec 2, 2010, at 10:16 PM, Chris Brennan wrote: Hi Chris, I use FreeBSD version 8.1, the host OS is Ubuntu 10.10. The host OS could connect to the Internet correctly. This host uses a private IP address. Yes, I allowed the VM software to install the bridge adapter now, when booting there are some msgs no DHCP offers received. Actually I am a little confused where the DHCP server is, do I need to install a DHCP server? Also, do I need to add that line ifconfig_le0/pcn0=DHCP in /etc/rc.conf? I am also don't understand how to set the static IP address since when setting a static IP address, we should have a router interface address, right? But now it's only a virtual machine running on a real machine, how can we do that? Thank you so much for your help. I am sorry for bring you so much trouble. Best, W.W. Weihang, It's no trouble, below you will see what I have in my /etc/rc.conf for a static IP. I use this same configuration in FreeBSD7.3 (and old Sony Vaio PIII), FreeBSD8.1-amd64 (My HP Laptop) and in my FreeBSD9 VM. Obviously the device name changes depending on the machine, but otherwise the configuration is the same. If you have a Router that your internet is connected to, that will usually provide DHCP Services, else you would indeed need to set one up on the host and tell the bridge to use it. ifconfig_nfe0=inet 192.168.0.4 netmask 255.255.255.0 defaultrouter=192.168.0.1 A quick search of vBox and Ubuntu revealed this URL: https://help.ubuntu.com/community/VirtualBox/Networking, I suggest giving it a read and see if you missed something. I do believe there are some extra steps necessary to set up a bridging device correctly on a Linux Host. I would also check out the vBox Community wiki as I believe there are some tips there as well for your Host OS. I am purposly vague about instructing you in *Linux* for a reason. Each OS does things differently, just as FreeBSD does things differently then Linux. They all speak a different langauge. The thing with Linux is that they are speak a different dialect of the same root language. The problem here, I don't speak Ubuntu's dialect. So I'll just safely point you to the resources that can help you. Some Links for you https://wiki.ubuntu.com/VirtualBox https://help.ubuntu.com/community/VirtualBox/Networking http://forums.virtualbox.org/viewtopic.php?t=1787 http://ubuntuforums.org/showthread.php?t=716404 http://www.virtualbox.org/manual/ch06.html - This one will be *endlessly* useful for you ... I would suggest checking out the whole handbook. vBox is actually very well documented Hi Chris, Thank you so much. I typed the lines you used in your rc.conf, it does not work here. Perhaps I need do some other things, I do not know. I have to check some of these resources you provide. I got this problem several days ago, but still could not solve it now. It is really time consuming... But anyway, I will check these resources. I will contact you if I have any progress or other problems. : ) Thanks, 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
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
Got an error: Unknown option DDB_CTF
Hi all, I am a totally newbie to FreeBSD. I am building a custom kernel based on FreeBSD 6.0 kernel (I have to use this version cause I need to run an application which is only available for FreeBSD 6.0). I conform to the handbook to add the following lines in kernel configuration file to enable DTrace support: options KDTRACE_FRAME options KDTRACE_HOOKS options DDB_CTF makeoptions WITH_CTF=1 Then I use the following commands to recompile my kernel and install this new kernel: make buildkernel KERNCONF=KERNELNAME make installkernel KERNCONF=KERNELNAME The compiling process encounters an error: Unknown option DDB_CTF, I have no idea how to fix this? Could anyone help me to see why this happens?? Thanks in advance. Best, W. Wang ___ 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: Got an error: Unknown option DDB_CTF
Hi, Thank you so much for your help. But I am still concerned about the backward compatibility. First I have to use DTrace to instrument the kernel to do performance analysis. At the same time, the program I need to build on the FreeBSD is a kind of transport protocol, which is based on the FreeBSD 6.0. The transport protocol may change the network stack of the kernel networking system, so I do not know whether this would work. Hope to hear from you. Thank you very much. Best, W.Wang On Nov 22, 2010, at 12:08 PM, Dan Nelson wrote: In the last episode (Nov 22), Weihang Wang said: I am a totally newbie to FreeBSD. I am building a custom kernel based on FreeBSD 6.0 kernel (I have to use this version cause I need to run an application which is only available for FreeBSD 6.0). I conform to the handbook to add the following lines in kernel configuration file to enable DTrace support: options KDTRACE_FRAME options KDTRACE_HOOKS options DDB_CTF makeoptions WITH_CTF=1 Then I use the following commands to recompile my kernel and install this new kernel: make buildkernel KERNCONF=KERNELNAME make installkernel KERNCONF=KERNELNAME The compiling process encounters an error: Unknown option DDB_CTF, I have no idea how to fix this? Just remove all references to CTF; that's for Dtrace support, which doesn't exist in the 6.* branch. You might also want to try running your application on FreeBSD 8.1 after installing the misc/compat6x package. Backwards binary compatibility support is very good. -- Dan Nelson dnel...@allantgroup.com ___ 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
Re: Got an error: Unknown option DDB_CTF
Hi, Thanks again. The transport protocol is not implemented by me, but I need to run this protocol to see the behavior of this protocol. So now I have no idea about the implementation of the transport protocol and don't know whether it could run on later versions than FreeBSD 6.0. I guess what I could do now is try to see whether this protocol could work on FreeBSD later version (8.1 or later?? ). If it works, then everything is fine. If not, maybe I have to find other instrumenting tools instead of DTrace. Thank you so much. Best, W.Wang On Nov 22, 2010, at 4:31 PM, Dan Nelson wrote: In the last episode (Nov 22), Weihang Wang said: On Nov 22, 2010, at 12:08 PM, Dan Nelson wrote: In the last episode (Nov 22), Weihang Wang said: I am a totally newbie to FreeBSD. I am building a custom kernel based on FreeBSD 6.0 kernel (I have to use this version cause I need to run an application which is only available for FreeBSD 6.0). I conform to the handbook to add the following lines in kernel configuration file to enable DTrace support: optionsKDTRACE_FRAME optionsKDTRACE_HOOKS optionsDDB_CTF makeoptions WITH_CTF=1 Then I use the following commands to recompile my kernel and install this new kernel: make buildkernel KERNCONF=KERNELNAME make installkernel KERNCONF=KERNELNAME The compiling process encounters an error: Unknown option DDB_CTF, I have no idea how to fix this? Just remove all references to CTF; that's for Dtrace support, which doesn't exist in the 6.* branch. You might also want to try running your application on FreeBSD 8.1 after installing the misc/compat6x package. Backwards binary compatibility support is very good. Thank you so much for your help. But I am still concerned about the backward compatibility. First I have to use DTrace to instrument the kernel to do performance analysis. At the same time, the program I need to build on the FreeBSD is a kind of transport protocol, which is based on the FreeBSD 6.0. The transport protocol may change the network stack of the kernel networking system, so I do not know whether this would work. Hope to hear from you. Thank you very much. If your program includes kernel modifications and the modifications only apply cleanly to FreeBSD 6, then you may be stuck unless you can port the changes to a newer version of FreeBSD. DTrace support for the kernel went into FreeBSD 7.1, and DTrace for user processes will be in 9.0 (with backports to 8.2 and 7.4 later). If your program implements its transport protocol completely in userland (by opening raw sockets for example), then it will probably run on FreeBSD 8.1. -- Dan Nelson dnel...@allantgroup.com ___ 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
Re: Got an error: Unknown option DDB_CTF
Hi, Thanks for your reply. Yes, now I still got problems. I have checked the release notes of versions later than 6.0, almost every version has not so few changes in their network protocols kernel. For example, some functions were replaced by others, arguments for a function is not needed in a later version, things like that... This will make the transport protocol does not work. But if I go through to adapt the protocol to a new version, that would be lots of work. Also, that's not what I supposed to do. On the other hand, I could not find other kind of instrumenting tools for FreeBSD either. E.g., Systemtap, LLtng, Oprofile e.t. which are all for Linux kernel. In terms of not on real machine, I have thought of using some kind of simulator, which could be used to get the performance statistics of the kernel. That is, I run the kernel and transport protocol on this simulator, and get information from this simulator. But again, not found a simulator for FreeBSD... BTW, I do not know how to use VM to do this... Could you explain a bit for me? Thank you so much. Best, W.Wang On Nov 22, 2010, at 9:04 PM, Chris Brennan wrote: On Mon, Nov 22, 2010 at 6:41 PM, Weihang Wang weih...@vt.edu wrote: Hi, Thanks again. The transport protocol is not implemented by me, but I need to run this protocol to see the behavior of this protocol. So now I have no idea about the implementation of the transport protocol and don't know whether it could run on later versions than FreeBSD 6.0. I guess what I could do now is try to see whether this protocol could work on FreeBSD later version (8.1 or later?? ). If it works, then everything is fine. If not, maybe I have to find other instrumenting tools instead of DTrace. Thank you so much. Best, W.Wang Why not run this test into a VM to test? It would sav you considerable time. ___ 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
