Older Newer
Sun, 03 Jul 2005 17:58:01 . . . . caladan.roxor.cx
Sat, 02 Jul 2005 19:37:36 . . . . caladan.roxor.cx
Sat, 02 Jul 2005 19:36:22 . . . . caladan.roxor.cx
Sat, 02 Jul 2005 19:20:51 . . . . caladan.roxor.cx
Fri, 27 May 2005 12:13:15 . . . . (Vudumen)?
Fri, 21 Jan 2005 13:05:51 . . . . ice.aspic.com
Fri, 21 Jan 2005 13:00:31 . . . . ice.aspic.com

Changes by last author:

Changed:
:Setup Linux-Vserver to use the future Network virtualization for testing purpose. While this new code is higly experimental and not yet integrated in util-vserver, we will have to use some dirty tricks.
:Setup Linux-Vserver to use the future Network virtualization for testing purpose. While this new code is highly experimental and not yet integrated in util-vserver, we will have to use some dirty tricks.
Changed:
Feel free to enhance this script, it's really a first try. We could take some info in environment/args set by vshelper and compute some uniq ids and then put this script in /etc/vservers/.defaults/apps/vshelper/statup. I you do such a script, please edit this page!
Feel free to enhance this script, it's really a first try. We could take some info in environment/args set by vshelper and compute some uniq ids and then put this script in /etc/vservers/.defaults/apps/vshelper/statup. If you do such a script, please edit this page!
Changed:
The en0 device of the vserver is binded to eth0 of the host. This really depend on your setup. You may change eth0 by something else if eth0 isn't the network device used for your vservers.
The en0 device of the vserver is bound to eth0 of the host. This really depends on your setup. You may change eth0 by something else if eth0 isn't the network device used for your vservers.
Changed:
To be able to set up your network interfaces inside the Vserver you should give it a NET_ADMIN capability. It's easy with util-vserver just edit /etc/vservers/<vserver_name>/bcapabilities and add a line to this file which is NET_ADMIN.
To be able to setup your network interfaces inside the Vserver you should give it a NET_ADMIN capability. It's easy with util-vserver: just edit /etc/vservers/<vserver_name>/bcapabilities and add a line to this file which is NET_ADMIN.
Changed:
Now, you vserver is started with to devices not configured: lo and en0. It's now the work of the vserver to setup network devices. So you can use scripts provided by the distribution to setup network devices and IPs. Iptables rules allow only some ips to talk to the network, but you can setup any IPs you want on your vserver devices.
Now, you vserver is started with two devices not configured: lo and en0. It's now the work of the vserver to setup network devices. So you can use scripts provided by the distribution to setup network devices and IPs. Iptables rules allow only some IPs to talk to the network, but you can setup any IPs you want on your vserver devices.