On Tue, Oct 19, 2010 at 11:58 AM, Bryce Stenberg <[email protected]> wrote: > I'm trying to set up a very basic install of Ubuntu Server 10.04 to act > as a basic router for a virtual network setup.
Well, if you give the VirtualBox guest machine a "NAT" interface instead of a "Host-Only" one, it will all work automatically. You won't be able to connect inwards to the VM guest in either case. If you want to do that, you either give the guest a proper external IP address by using Bridging mode on the network, or use host-only and mess about with iptables to do inbound NAT, not recommended. > I just want all traffic passed from host-only network side of this > virtual server to go out through its external interface (which is a > NAT'd and handled by VirtualBox). That's contradictory. Either the interface is a VirtualBox NAT one, or it is a VirtualBox host-only one (or Bridged ...). > >From this ubuntu server I can ping external networks on the internet and > machines on the internal host-only network. > But from a server on the host-only network I can't get a response from > pings to external networks. Correct, because you connected it to "host *only*". It can *only* talk to the host. Change that :-) > So, can someone please tell me what the missing piece is? As in what > settings of software do I need to setup to get the traffic to go both > ways. By "both ways", do you mean that you want a third machine on the network to make inbound connections to the virtual server? (i.e. if the virtual server were running apache or something). If so, Bridging is the simplest network setup. -jim _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
