>>I am sure this is a problem, because most people have small blocks (4, 8 or >>16 IPs). >>Yes, but with blocks range, they generaly use 1 ip as gateway (see my >>schema),which can be also use for dhcp.
I also forget to say, with a block range, you can assign ip in 2 ways example with 4ip blocks (/30 network) 1) like my schema, you use /30 for you vms. That mean that only 2 ip are usable 172.168.0.1 (network) 172.158.0.2 (first usable ip) 172.158.0.3 (first usable ip) 172.158.0.4 (brodcast address) and on 2 usables ip, you need to use 1 for gateway/dhcp on proxmox host 2) or you route the 4 ips from proxmox host with /32 range with route add 172.168.0.1/32 gw tap1 route add 172.168.0.2/32 gw tap2 route add 172.168.0.3/32 gw tap3 route add 172.168.0.4/32 gw tap4 (this is similar as if you buy 1 failover ip on ovh) I don't known if we can done some dhcp tricks with a /32, they are no broadcast address, don't known how it's work. ----- Mail original ----- De: "Alexandre DERUMIER" <[email protected]> À: "Dietmar Maurer" <[email protected]> Cc: [email protected] Envoyé: Mercredi 28 Août 2013 06:44:55 Objet: Re: [pve-devel] dnsmasqd needs extra ip >>I miss the route for 172.16.1.1 and gateway 172.16.0.1 on the host? oh,sorry, I wan to say 172.168.0.10,172.168.1.10 instread 172.168.1.1,172.16.0.1 > #route add 172.168.0.10 gw tapguest1 > #route add 172.168.1.10 gw tapguest2 >>I am sure this is a problem, because most people have small blocks (4, 8 or >>16 IPs). Yes, but with blocks range, they generaly use 1 ip as gateway (see my schema),which can be also use for dhcp. >>But so far I also have no idea to avoid the usage of an extra IP. How does it work with userland kvm nic and internal dhcp server ? ----- Mail original ----- De: "Dietmar Maurer" <[email protected]> À: "Alexandre DERUMIER" <[email protected]> Cc: [email protected] Envoyé: Mercredi 28 Août 2013 06:23:55 Objet: RE: dnsmasqd needs extra ip > indivual ips: (aka failover ip) > > http://www.ovh.co.uk/dedicated_servers/ip_failover.xml > Theses ip are individuals and non contiguous, routed from ovh routers to > proxmox main ip > > This is really a problem because we don't have extra ip for dhcp. > > ex: client buy failoverip 172.16.0.1/32 && 172.16.1.1/32 routed to main > proxmox ip 192.168.1.2 > > client 10.0.0.2----------->external router(192.168.1.1)--------- > >(192.168.1.2)proxmox-------------->(172.16.0.10/32)guest1 > -------------- > >(172.16.1.10/32)guest2 > > host config: > auto eth0 > iface eth0 inet static > address 192.168.1.2 > netmask 255.255.255.0 > gateway 192.168.1.1 > > #route add 172.168.0.10 gw tapguest1 > #route add 172.168.1.10 gw tapguest2 > > guest1 config: > iface eth0 inet static > address 172.16.0.10 > netmask 255.255.255.255 > gateway 172.16.0.1 > > guest2 config: > iface eth0 inet static > address 172.16.1.10 > netmask 255.255.255.255 > gateway 172.16.1.1 I miss the route for 172.16.1.1 and gateway 172.16.0.1 on the host? > range block ip: (aka failover ripe/arin block) > http://www.ovh.com/us/dedicated-servers/arin_ip_block.xml > > Not too much a problem,minimum block size is 4 ips I am sure this is a problem, because most people have small blocks (4, 8 or 16 IPs). > ex: client buy failoverip range block 172.16.0.0/24 && 172.16.1.0/24 routed > to > main proxmox ip 192.168.1.2 > > proxmox host have one ip of the range, which is used as gateway by guests > and also used as dhcp server ip > > client 10.0.0.2---->external router(192.168.1.1)------ > >(192.168.1.2)proxmox(vmbr1 172.16.0.1/24)--------->(172.16.0.10/24)guest > (vmbr2 172.16.1.1/24)--------- > >(172.16.1.10/24)guest > > host config: > auto eth0 > iface eth0 inet static > address 192.168.1.2 > netmask 255.255.255.0 > gateway 192.168.1.1 > > guest1 config: > iface eth0 inet static > address 172.16.0.10 > netmask 255.255.255.0 > gateway 172.16.0.1 > > guest2 config: > iface eth0 inet static > address 172.16.1.10 > netmask 255.255.255.0 > gateway 172.16.1.1 But so far I also have no idea to avoid the usage of an extra IP. _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
