On Fri, Sep 16, 2005 at 11:00:26AM +0200, Karsten Horsmann wrote:
> Hello.
>
> On my servers i used the Vserver-Patch 2.0 and i like it. So i took
> the patch vs2.1.0-pre7 on my laptop with 2.6.13.1 Kernel.
>
> Works find with Debian/Sarge and the Debian util-vserver from Sid.
>
> Now i ve two problems. I want to use an dhcpd within the vserver
> guest and i want diffrent networkdevice for the vps.
>
> Question #1 Whats the right setup for an dhcpd inside a vps?
>
> the dhcpd (or dnsmasq, provides dhcp/dns)
> I need some capabilities.
>
> cat /etc/vservers/mobil/bcapabilities
> CAP_NET_RAW
> CAP_NET_BROADCAST
> Okay, that works fine and i can start the dnsmasq (dhcp-Service).
>
> The old Config Style use this Entries:
> IPROOT=192.168.0.210
> IPROOTBCAST=192.168.0.255
> IPROOTBCAST=255.255.255.255
>
> I try this
>
> cat /etc/vservers/mobil/interfaces/0/dev ath0
> cat /etc/vservers/mobil/interfaces/0/ip 192.168.100.210
> cat /etc/vservers/mobil/interfaces/0/prefix 24
> cat /etc/vservers/mobil/interfaces/0/name mo0
>
> cat /etc/vservers/mobil/interfaces/1/dev ath0
> cat /etc/vservers/mobil/interfaces/1/ip 192.168.100.255
> cat /etc/vservers/mobil/interfaces/1/prefix 24
> cat /etc/vservers/mobil/interfaces/1/name mo1
>
> cat /etc/vservers/mobil/interfaces/2/dev ath0
> cat /etc/vservers/mobil/interfaces/2/ip 255.255.255.255
> cat /etc/vservers/mobil/interfaces/2/prefix 32
> cat /etc/vservers/mobil/interfaces/2/name mo2
haven't tried this, but I'd specify the broadcasts
as 'existing' IPs and not as new 'assigned' IPs
so you probably want to make them:
1/nodev 1/ip=192.168.100.255 1/prefix=24
2/nodev 2/ip=255.255.255.255 1/prefix=32
> Maybe the ip/netmask setup is the Problem?
for me, the question is: what is the problem? :)
> Question #2 How can i switch between 2 nics?
>
> This mobile Vserver guest shouldt provide some services
> on my ath0 (wireless network) or on my eth0 (wired) device.
>
> The Host should have network access too.
>
> Whats the right solution for this?
>
> Put the VPS on an dummy0 and add this to an bridge with the
> connected device? Or something else?
depends on the networks you use ...
if you have for example 192.168.100.x on ath0
and 192.168.200.x on eth0, then you probably
want a setup for the following:
mo0=ath0:192.168.100.210/24
mo1=eth0:192.168.200.210/24
192.168.100.255/24
192.168.200.255/24
255.255.255.255/32
> Thanks for any hints :-).
HTH,
Herbert
> --
> MfG
> Karsten Horsmann
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
