From: Christian Mayrhuber (christian.mayrhuber_at_gmx.net)
Date: Mon 25 Oct 2004 - 11:11:36 BST
On Sunday 24 October 2004 18:54, TK Lew wrote:
> hi herbert :
> Thank for the replies .
> a. Understood. We cannot set default route inside vserver. It will
> mess up the host routing table :) Tested.
> I have read the LARTC but until now I still cannot ping or get
> vapt-get working.
> I started the a vserver using eth1 and have a ppp0 connection to the
> Vserver IP : 192.168.100.200
I'm afraid this is no routing problem. Your vserver is using a private
IP address. Private IP addresses don't get routet on the Internet at all.
To enable access for the vserver to the Internet via ppp0 you have to
either use NAT with iptables, or install a http proxy server on
the host system.
I'm using the NAT approach with the shorewall (http://www.shorewall.net)
firewall scripts for this purpose with the dummy0 device being the dmz
# apt-get install shorewall
The setup of shorewall + ppp could become tricky, so I'd suggest to
run dns and http proxy servers on your host or use a simple X11 firewall
tool like firestarter (http://firestarter.sf.net), which should be
good enough for playing around.
# apt-get install firestarter
You have to activate NAT in the "Internet connection sharing" display of
the "Firewall Wizard".
Hope this helps.
-- lg, Chris _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver