similar to: Static DHCP assignments to VMs connected to bridge

Displaying 20 results from an estimated 8000 matches similar to: "Static DHCP assignments to VMs connected to bridge"

2017 Oct 30
2
libvirt/dnsmasq is not adhering to static DHCP assignments
Given the following network configuration: =========== <network> <name>osc_mgmt</name> <uuid>d93fe709-14ae-4a0e-8989-aeaa8c76c513</uuid> <forward mode='route'/> <bridge name='osc_mgmt' stp='on' delay='0'/> <mac address='52:54:00:3f:fe:10'/> <ip address='192.168.80.254'
2017 Oct 31
1
Re: libvirt/dnsmasq is not adhering to static DHCP assignments
Hi, It looks like that's the issue: # cat /var/lib/libvirt/dnsmasq/osc_mgmt.hostsfile 52:54:00:2c:85:92,192.168.80.1,openstack-controller-00 But it makes me wonder...libvirt should be generating and managing this file right? Do I need to edit this myself or should libvirt be updating this file? If so then why isn't it? On Mon, Oct 30, 2017 at 5:21 AM, Yalan Zhang
2017 Oct 30
0
Re: libvirt/dnsmasq is not adhering to static DHCP assignments
Please check the dnsmasq hostsfile, should have all the records there: # cat /var/lib/libvirt/dnsmasq/osc_mgmt.hostsfile 52:54:00:2c:85:92,192.168.80.1,openstack-controller-00 52:54:00:e2:4b:25,192.168.80.2,openstack-database-00 52:54:00:50:91:04,192.168.80.3,openstack-keystone-00 52:54:00:fe:5b:36,192.168.80.7,openstack-rabbitmq-00 52:54:00:95:ca:bd,192.168.80.5,openstack-glance-00 -------
2008 Nov 22
2
[Bridge] bridge changes id on addif - is that normal?
hi i've setup the following on debian etch with bridge-utils 1.4 (backported) and kernel 2.6.26 from backports.org: vlan10 with raw device eth0 vlan20 with raw device eth0 br10 with initial port vlan10 br20 with initial port vlan20 i've set hw addr to DE:AD:BE:EF:34:10 for br10 and DE:AD:BE:EF:34:20 for br20 the bridges are used to connect virtual machine nic's. "brctl
2015 Jul 09
2
Bonds & Bridge best practices
Hi All I have two bond interfaces namely, bond0 and bond1. bond0 has two ethernet interfaces associated with it and bond1 also has two ethernet interfaces associated with it. Now i create a bridge interface namely br20 (20 being the VLAN) and assign it a IP Address , subnet mask and the default gateway. I will use this IP to reach the server. So it is like a management bridge for me.
2013 Oct 06
1
Re: Automatically assign static ipv4 via dhcp to new VMs (Tim)
You can do this with the built in dhcp server for the virtual network. The definition is passed to dnsmasq. ... <ip address="192.168.122.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.122.100" end="192.168.122.254" /> <host mac="00:16:3e:e2:ed" name="foo.example.com"
2013 Oct 07
0
Re: Automatically assign static ipv4 via dhcp to new VMs
On 10/04/2013 12:09 PM, Tim wrote: > Hi guys, > > I'm running a KVM/libvirt host in a datacenter and got a fancy IPv4 > subnet from my provider. I'm able to assign IPs from that subnet via > dhcp to my VMs: > > host01 ~ # virsh net-dumpxml internet > <network connections='3'> > <name>internet</name> >
2019 Aug 02
0
Re: libvirt/dnsmasq is not adhering to static DHCP assignments
On 8/1/19 4:21 AM, Christian Kujau wrote: > This is basically a continuation of an older posting[0] I found, but > apparently no solution has been posted. So, I'm trying to setup static > DHCP leases with dnsmasq that is being started by libvirtd: > > > ----------------------------------------------------------- > $ sudo virsh net-dumpxml --network default >
2013 Oct 17
1
Re: Automatically assign static ipv4 via dhcp to new VMs
Thanks for the hint with net-update, thats exactly that what I was looking for. Am 07.10.2013 13:10, schrieb Laine Stump: > On 10/04/2013 12:09 PM, Tim wrote: >> Hi guys, >> >> I'm running a KVM/libvirt host in a datacenter and got a fancy IPv4 >> subnet from my provider. I'm able to assign IPs from that subnet via >> dhcp to my VMs: >> >>
2019 Aug 01
2
libvirt/dnsmasq is not adhering to static DHCP assignments
This is basically a continuation of an older posting[0] I found, but apparently no solution has been posted. So, I'm trying to setup static DHCP leases with dnsmasq that is being started by libvirtd: ----------------------------------------------------------- $ sudo virsh net-dumpxml --network default <network> [...] <dns enable='no'/> <ip
2013 Oct 04
2
Automatically assign static ipv4 via dhcp to new VMs
Hi guys, I'm running a KVM/libvirt host in a datacenter and got a fancy IPv4 subnet from my provider. I'm able to assign IPs from that subnet via dhcp to my VMs: host01 ~ # virsh net-dumpxml internet <network connections='3'> <name>internet</name> <uuid>37b888cc-510f-46f1-9246-346da96222ed</uuid> <forward dev='enp5s0f0'
2012 Apr 08
2
[Bug 48441] New: gnome-control-center crashes with nouveau driver
https://bugs.freedesktop.org/show_bug.cgi?id=48441 Bug #: 48441 Summary: gnome-control-center crashes with nouveau driver Classification: Unclassified Product: Mesa Version: 8.0 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:
2016 Apr 07
2
KVM Virtualization Network VLAN CentOS7
On Thu, Apr 7, 2016 at 1:26 PM, Subscriber <ml-lists at agoris.net.ua> wrote: > Hello FrancisM, > > Thursday, April 7, 2016, 8:03:38 AM, you wrote: > > > > I tried last night and it seems like the vlans that I created is failing > to > > bring-up. So this is what Im doing > > > in my DATA trunk port at my HomeLab Im doing this > > > 2 port
2013 Jul 30
0
Fwd: nut package with Riello UPS support
Here is what I did: # cd /root/nut/ # nut here it's checkouted repository # ./configure --with-user=_ups --with-group=_ups # cd drivers/ # make riello_ser # chgrp bin riello_ser # cp riello_ser /usr/local/bin # here I copied builder driver to folder where nut-package will store their files/drivers # pkg_add nut-2.6.5p1 # ls -la /dev/tty00 crw-rw---- 1 _ups _ups 8, 0 Jul 30
2015 Sep 08
0
Samba AD DC, DHCP & Address Assignments
On 09/08/2015 09:04 AM, Jim Seymour wrote: > Hi All, > > I should have considered this beforehand... Assumed the info would be > in the Wiki somewhere. Cannot find. > > The way our LAN has been working is clients use DHCP, but all address > assignments are static. Thus, when a given PC asks "what's my > address?", the DHCP server looks at the MAC address
2015 Sep 08
0
Samba AD DC, DHCP & Address Assignments
On Tue, 8 Sep 2015, Jim Seymour wrote: > I should have considered this beforehand... Assumed the info would be > in the Wiki somewhere. Cannot find. [snip] > Problem with the AD DC is that it lives in a sub-domain, > "addc.example.com", and the zone for that sub-domain is a dlz. So... > how do I set/assign client PCs' IP addresses? It's here:
2015 Sep 08
0
Samba AD DC, DHCP & Address Assignments
On 09/08/2015 10:21 AM, Jim Seymour wrote: > On Tue, 8 Sep 2015 09:19:22 -0400 > Robert Moskowitz <rgm at htt-consult.com> wrote: > >> On 09/08/2015 09:04 AM, Jim Seymour wrote: >> > [snip] >>> And the zone file on deepthought might read something like... >>> >>> somepc IN A 192.168.0.10 > [snip] >>> Problem with
2015 Sep 08
0
Samba AD DC, DHCP & Address Assignments
On 09/08/2015 11:22 AM, Jim Seymour wrote: > NOTE: Please honour the "Reply-To" and do not "Reply-All". I'm reading > the mailing list. I wouldn't be posting to it if I was not and I don't > need two copies. Thanks! Each list is different, and some work right like this, others the only way to reply to list is to reply-all, thus I get a little lazy at
2013 Dec 08
2
assign static external IP to container
hello i have a server colocated in a datacenter with several external IP addresses available to use. the physical server is using one of these IPs, and i want to assign another, unused IP to the virtual machine. i thought i could just do this by editing the container's /etc/network/interfaces, setting a static IP address for eth0 much like i did for br0 on the host machine.... but doesn't
2015 Sep 08
2
Samba AD DC, DHCP & Address Assignments
On Tue, 8 Sep 2015 09:19:22 -0400 Robert Moskowitz <rgm at htt-consult.com> wrote: > > On 09/08/2015 09:04 AM, Jim Seymour wrote: > [snip] > > > > And the zone file on deepthought might read something like... > > > > somepc IN A 192.168.0.10 [snip] > > Problem with the AD DC is that it lives in a sub-domain, > >