search for: networker

Guys, OK, now that we have the new core contributors squared away, we can go back to finishing the contributors list. There were some people who got added and then there is existing contributors list. I think Darren''s suggestion to wait to add new core contributors is fine (let the new constitution settle down and we can in the meanwhile have a more inclusive look at both rather than

----- Mail original ----- > De: "Gordon Messmer" <gordon.messmer at gmail.com> > ?: "centos" <centos at centos.org> > Envoy?: Vendredi 18 D?cembre 2015 12:06:26 > Objet: Re: [CentOS] Network services start before network is up since migrating to 7.2 >>> The network service is not blocking the flow so it executes and systemd >>>

There's still room for additional refactoring as we may want to eventually split out nic, bonding, and ip address manipulation into their own controller/svc module, but that would be a much more extensive redesign than we want to deal with for the overall service layer creation refactoring. Signed-off-by: Scott Seago <sseago at redhat.com> --- src/app/controllers/network_controller.rb

Hi, on our cluster we have 5 network interfaces. I was surprised to discover that the ifcfd-* files under /etc/sysconfig/networking and /etc/sysconfig/network-scripts were not the same. So I have searched a little bit, but I'm now confused: - the files under /etc/sysconfig/networking come from system-config-network. - the files under /etc/sysconfig/network-scripts are read by the

Hello James, > Well it looks like you are using the network service rather than the > recommended NetworkManager ... Yes. That's the way our security experts made the models I use to setup my servers. I'll test a migration to NetworkManager, and take their advice on it. > > The network service is not blocking the flow so it executes and systemd > carries on ... >

I have need to use the old network-scripts and not NetworkManager. I did yum install network-scripts, I have ifcfg-eth0 set for ONBOOT=yes but it is not starting on boot. What have I missed ? Jerry

Deep in the discussion of this bug, unfortunately mostly in private comments: https://bugzilla.redhat.com/show_bug.cgi?id=1594515 we decided it'd be more flexible for RHV if we had a way to map individual NICs to target networks and bridges. This can be done by adding a new --mac option so you can specify the exact mapping you need: $ virt-v2v [...] \ --mac

On 5/5/20 8:11 AM, john doe wrote: > On 3/30/2020 4:10 PM, Michal Prívozník wrote: >> On 30. 3. 2020 15:26, john doe wrote: >>> On 3/30/2020 1:20 PM, Andrea Bolognani wrote: >>>> On Mon, 2020-03-30 at 12:04 +0200, Michal Prívozník wrote: >>>>> On 27. 3. 2020 20:49, john doe wrote: >>>>>> If my understanding is correct, using

On Thu, 3 Oct 2019, Jerry Geis wrote: >>> systemctl status network > > > AT BOOT: > ? network.service - LSB: Bring up/down networking > Loaded: loaded (/etc/rc.d/init.d/network; generated) > Active: inactive (dead) > Docs: man:systemd-sysv-generator(8) > > After: service network restart > ? network.service - LSB: Bring up/down networking >

Hi all, I need some guidance to get my problem fixed. I believe there is an issue with the ''nth'' patch from the patch-o-matic, which is labeled as status ''works''. I have tunnels back and forth across the internet, using ''nth'' to balance packets between different public networks (over the tunnels). I need to access some networks over two

Hi, I am using the function plot.network from the network library. However, I noticed that every time when I use the function I get a different layout (the network is rotated?). I would like to get the exact same picture every time when I use the function. Is that possible (maybe set a seed or some layout parameters?)? How? Here is an example: n<-6 dat <- rbinom(n*(n-1)/2,1,.6)

created/edit network information is all specified on one simpler form --- src/app/controllers/network_controller.rb | 27 +++++++++++++++---- src/app/models/bonding.rb | 2 +- src/app/models/network.rb | 2 +- src/app/models/nic.rb | 2 +- src/app/views/network/_form.rhtml | 15

OK, this is the first important vuln I've seen since joining the centos list, and represents a good opportunity to ask "What happens now?" Do you accept contributed rebuilds? What is the rebuild/test/release procedure? Is there anyone who is tracking time between RH releases and centos yum repo updates? What can I do to help? thanks, -ryan -- Ryan Sweet

Hey! Another question. The documentation about networks say: ╭─────┤ http://libvirt.org/formatnetwork.html#elementsConnect ├───── │Inclusion of the forward element indicates that the virtual network is │to be connected to the physical LAN.Since 0.3.0. The mode attribute │determines the method of forwarding. If there is no forward element, the │network will be isolated from any other network

Hi, When I click on "Edit Network" on my managed node in the hosts tab of the oVirt UI I only see one NIC. My managed node has 2 NICs, one on the guest network and one on the admin network. The NIC on the admin network is not listed in the network editor. Is this normal? I'm trying to create a VM and boot the cobbler profile I created for Fedora 10 but I can only boot the VM

Hi, I have some guests running in the "default" network (virbr0) and I've also created a similar (NAT) network (virbr1). Therefore, the FORWARD chain for the CentOS 6.4 host looks like this: http://fpaste.org/29229/75281379/ ...where line 3-7 are related to virbr0 and 8-12 to virbr1. My 2 questions: 1) I've noticed that I can ping from a guest within virbr0 to any guest on

This is just one possible way to fix this bug, but the simplest. Others I considered: - Keeping the network disabled by default. Options like --install wouldn't work and there would be no actionable error message telling users what to do to fix it. - Modifying virt-customize to warn/error/suggest if operations like --install were used but the network was disabled. However

From: Scott Seago <sseago at redhat.com> This adds some of the network API stuff to ovirt-agent. It's still not complete but what is there is functional. Signed-off-by: Ian Main <imain at redhat.com> --- src/ovirt-agent/lib/ovirt.rb | 3 + .../ovirt/controllers/hardwarepool_controller.rb | 2 +- .../lib/ovirt/controllers/network_controller.rb |

- Default NETWORKING=no in /etc/sysconfig/network - Update to yes when configuring network through TUI or firstboot - After configuration in TUI, (re)start ntp daemons rhbz#675870 Signed-off-by: Mike Burns <mburns at redhat.com> --- recipe/common-post.ks | 6 ++++++ scripts/network.py | 10 +++++++++- scripts/ovirt-config-networking | 1 + 3 files

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some