Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have two OS Fedora 9 and Fedora 10 Dsktop Version running on Virtualbox on Ubuntu 9.04. I want to testdrive Sendmail throuhg Fedora 9 as server and Fedora 10 as Client. How to setup the sendmail server?
So each instance of Fedora will run in a virtual machine (VM) defined by configuration in VirtualBox on the host. By default, the VMs' NICs will be NAT-attached. For NAT-attached VM NIC's, VirtualBox running on the host acts like a router. It provides a DHCP server and NAT translation. This is, in effect, like the common arrangement of a private LAN connected via router to an ISP.
It has the same restrictions; services running on computers on the (virtual) private LAN can only be reached through the router by port forwarding. And it has more restrictions (from VirtualBox 2.0.6 documentation) that are seldom significant but are included here for completeness:
Quote:
There are four limitations of NAT mode which users should be aware of:
ICMP protocol is very limited: Some frequently used network debugging tools (e.g. ping) rely on sending/receiving messages based on the ICMP protocol. The ICMP protocol cannot be used directly by normal applications such as VirtualBox, as it would, at least on Linux hosts, require root permissions (more precisely CAP_NET_RAW). Since this is not desirable, no attempt has been made to support ICMP to addresses other than 10.0.2.2 and 10.0.2.15. If you try to ping any other IP address you will not get any response.
Receiving of UDP broadcasts is not reliable: The guest does not reliably receive broadcasts, since, in order to save resources, it only listens for a certain amount of time after the guest has sent UDP data on a particular port. As a consequence, NetBios name resolution based on broadcasts is not always working (but WINS always works). As a workaround, you can use the numeric IP of the desired server in the \\server\share notation.
Protocols such as GRE are unsupported: Protocols other than TCP and UDP are not supported. This means some VPN products (e.g. PPTP from Microsoft) cannot be used. There are other VPN products which use simply TCP and UDP.
Forwarding host ports < 1024 impossible: On Unix-based hosts (e.g. Linux, Solaris, MacOS X) it is not possible to bind to ports below 1024 from applications that are not run by root. Therefore if you try to configure such a port forwarding, then the VM will refuse to start.
What network connectivity do you want? From Internet (or real LAN) to your VM(s)? From applications running on your host OS to your VM(s)? Only between the VMs?
I need the server and client architecture in between my Two VM ware Machines ..ie Fedora 9 and Fedora 10.. so that I can do R&D with Various Servers Setup.
OK -- if you only want to network between the VMs then the simplest thing to do is go with VirtualBox's default NAT-attached but not use DHCP. This is not the only option but it is the simplest.
There might be a problem if you clashed with the 10.0.2.0/24 address of the virtual router. Not knowing what that is (and not wanting to research it right now), the simplest would be to pick some other non-routeable IP range addresses -- say 192.168.1.128 and 129 -- and configure those within your Fedora instances.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.