Missing /var/run/network

[jaimie]

Hello all,

I seem to be having an odd problem with 1.4 beta with /var/run/network folder is missing on 3 our 6 cts so networking fails to start. Was wondering if any one else has seen this and how to fix it. All cts are ubuntu 9.04 upgrades from 8.0464 template varied services from DHCPD to MYSQL, LDAP, DNS.

example confs from /etc/vz/conf
ORIGIN_SAMPLE="pve.auto"
IP_ADDRESS="192.168.0.5"
HOSTNAME="dhcp.xxxx.net"
NAMESERVER="192.168.0.1"
SEARCHDOMAIN="xxxx.net"

they all match with other hosts that work

on proxmox server network is nothing fancy
auto vmbr0
iface vmbr0 inet static
address 192.168.0.10
netmask 255.255.255.0
gateway 192.168.0.254
bridge_ports eth0
bridge_stp off
bridge_fd 0

Once I create the folder /var/run/network I can start the networking and the interfaces are up. Once the ct is restarted the folder is gone.

I am new at proxmox and this is the first install I have done.

Another problem I have run across is DHCP3 server wont run due to interface problems cant bind to interface even though its set up to for the network. Any one get a Linux DHCP server to run on proxmox? any help would be appreciated.

 

[dietmar]

Not sure it this applies here, but in 'dab' we do somethin like:

sed -e 's/RAMRUN=yes/RAMRUN=no/' -e 's/RAMLOCK=yes/RAMLOCK=no/'  -i /etc/default/rcS
mkdir /var/run/network

Does that help?

 

[jaimie]

That did the trick. So this was an issue with Ubuntu cts and not Proxomox then I take it?

Thanks a bunch if I ever make it to your neck of the woods I'll buy yah a beer!

So any clues on how to get dhcp3-server to listen to the interface venet0:0?
output from dhdcpd

Oct 13 13:04:14 dhcp dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Oct 13 13:04:14 dhcp dhcpd: Connecting to LDAP server 192.168.0.4:389
Oct 13 13:04:14 dhcp dhcpd: Successfully logged into LDAP server 192.168.0.4
Oct 13 13:04:14 dhcp dhcpd: Found dhcpServer LDAP entry 'cn=dhcp,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: LDAP: Parsing dhcpServer options 'cn=dhcp,dc=domain,dc=net' ...
Oct 13 13:04:14 dhcp dhcpd: LDAP: Parsing dhcpService DN '"' ...
Oct 13 13:04:14 dhcp dhcpd: Found LDAP entry 'cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Parsing external DNs for 'cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Sending config line 'ldap-server "radius.domain.net"; ldap-port 389; ldap-base-dn "dc=domain,dc=net"; ldap-debug-file "/var/log/dhcp-ldap-start
up.log"; ldap-dhcp-server-cn "dhcp"; ldap-method dynamic; ddns-update-style none; default-lease-time 600; max-lease-time 7200; authoritative; log-facility local7; option domain-
name "domain.net"; option domain-name-servers ns.domain.net; '
Oct 13 13:04:14 dhcp dhcpd: Found LDAP entry 'cn=192.168.0.0,cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Parsing external DNs for 'cn=192.168.0.0,cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Sending config line 'subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.100 192.168.0.200; } '
Oct 13 13:04:14 dhcp dhcpd: Found LDAP entry 'cn=127.0.0.0,cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Parsing external DNs for 'cn=127.0.0.0,cn=DHCP Config,dc=domain,dc=net'
Oct 13 13:04:14 dhcp dhcpd: Sending config line 'subnet 127.0.0.0 netmask 255.0.0.0 { } '
Oct 13 13:04:14 dhcp dhcpd: Internet Systems Consortium DHCP Server V3.1.1
Oct 13 13:04:14 dhcp dhcpd: Copyright 2004-2008 Internet Systems Consortium.
Oct 13 13:04:14 dhcp dhcpd: All rights reserved.
Oct 13 13:04:14 dhcp dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Oct 13 13:04:14 dhcp dhcpd: Wrote 0 leases to leases file.
Oct 13 13:04:14 dhcp dhcpd:
Oct 13 13:04:14 dhcp dhcpd: Not configured to listen on any interfaces!


I am going to add the network thats in my routing table to the dhcp config with no assignments. I am not sure where it gets 192.0.2.1 assigned from my guess is the server uses this ip for the vmbr0.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.0.2.1 * 255.255.255.255 UH 0 0 0 venet0
default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0


I tried setting up an aliases to eth0:1 and creating a new bridge vmbr3 with the assigned IP. Set the ct to use the vmbr3. This sorta worked but the ct could not ping any other cts but was accessible from outside the proxmox server.

Basically what I am doing here is cloning our server set up for testing and development. DHCP is 100% needed the company is an ISP which offers WISP services. This proxmox server is for development of the walled garden and hot spot so i need DHCP working which is the last service I have yet to figure out.

 

[dietmar]

So any clues on how to get dhcp3-server to listen to the interface venet0:0?

venet is a high level 'routed' network without layer 2 (no MAC address). But DHCP works on layer 2, and needs MAC addresses. So I guess this will be impossible.

And venet IP addresses are assigned by vzctl - you can't control that inside the container anyways.

 

[jaimie]

Actually I got it to work but your right what I was trying to do would never work.

I did not need DHCP for the cts but for outside clients IE wisp cpes and wifi devices.

What had to do to get a working virtual DHCP server is add a NIC to the server and connect it to my lan. Then create new bridge on the host:
auto vmbr3
iface vmbr3 inet manual
bridge_ports eth3
bridge_stp off
bridge_fd 0

Then in the ct add the bridge /etc/vz/conf/103.conf

NETIF="ifname=eth0,bridge=vmbr3,mac=00:0c:29:9e:df:ef,host_ifname=veth103.0,host_mac=00:0c:29:3d:ea:7b"

Added the ip information to /etc/network/interfaces.tail in the ct
auto eth0
iface eth0 inet static
address 192.168.0.5
netmask 255.255.255.0
up /sbin/ip route add 192.168.0.254 dev eth0

reboot and now I have a working DHCP server for clients.