similar to: [PATCH node] Change DNS setup to match NTP. rhbz#508677

--- scripts/network.py | 207 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 207 insertions(+), 0 deletions(-) create mode 100644 scripts/network.py diff --git a/scripts/network.py b/scripts/network.py new file mode 100644 index 0000000..28e32f2 --- /dev/null +++ b/scripts/network.py @@ -0,0 +1,207 @@ +#!/usr/bin/python + +from ovirtfunctions import * +import tempfile

When the user runs o-c-networking then it ensures that all features of networking that we configure are reset and only those settings touched are applied. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 46 +++++++++++++++++++++++++------------- 1 files changed, 30 insertions(+), 16 deletions(-) diff --git a/scripts/ovirt-config-networking

Added a new function, "ask_yes_or_no", to ovirt-functions. It contains a default prompt if none is provided. Changed all prompts that ask for yes, no and/or abort to use this new method. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-boot-wrapper | 8 ++--- scripts/ovirt-config-collectd | 39 +++++++++++++++-----------

If the vlan kernel argument is provided, then it is used during networking auto-configuration. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 56 ++++++++++++++++++++++++++++++++------ scripts/ovirt-early | 7 ++++- 2 files changed, 53 insertions(+), 10 deletions(-) diff --git a/scripts/ovirt-config-networking

This patch obsoletes the previously submitted patch. It adds a warning message to the user when they select to change the NTP settings.

This fixes networking changes when switching from dhcp/static to disabled. Before the ifcfg scripts would contain old values from the previous configuration. Support for disabled devices is now added and some useless remnant bash->python coding cleaned up --- scripts/network.py | 45 +++++++++++++++++++--------------------- scripts/ovirt-config-setup.py | 34

If an existing set of configuration files exist they are deleted. While in the configuration menu, only one NIC is configured. If the user selects a second network card to configure then the previous configuration is discarded and only the new one saved. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 29 ++++++++++++++++++++++++++--- 1 files

parse input augtool strings to oper,key,value --- scripts/network.py | 32 ++++++++++++++++---------------- 1 files changed, 16 insertions(+), 16 deletions(-) diff --git a/scripts/network.py b/scripts/network.py index f51ee7c..65b551c 100644 --- a/scripts/network.py +++ b/scripts/network.py @@ -165,11 +165,11 @@ class Network: ntpconf = ntpconf.split("\n") for line

Now, rather than displaying yet another warning, the NTP configuration just requires that the user select a NIC to configure first. That act alone provides the single warning to the user that they'll be changing their network configuration.

This is a repost of patches for ovirt-config-* ACK to all. Pushed.

My firewall''s configuratione is like this: |-FW--------------------| | eth0 - LAN | | IP1_ISP1 - eth1 | | IP1_ISP2 - eth2 | |-----------------------| I have configured firewall as specified on http://lartc.org/howto/lartc.rpdb.multiple-links.html and all works ok, except for connections between my firewall and other hosts of "other" ISP. Example: I

Hi, yesterday i tried to join a domain as a DC with bind9 as dns-backend on Debian Wheezy with samba 4.1.11 from backports. I followed the tutorial in the wiki https://wiki.samba.org/index.php/Join_a_domain_as_a_DC but didn' find the instruction completely clear, so perhaps i made a mistake during the join. It is written there: "If you choose BIND as DNS backend, instead of the

Hi CentOS users We are running CentOS 4.5 with NTP 4.2.0. # cat /etc/ntp.conf restrict default ignore restrict dns1.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict dns2.xxx.xxx mask 255.255.255.0 nomodify notrap noquery restrict 127.0.0.1 server dns1.xxx.xxx server dns2.xxx.xxx fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift broadcastdelay 0.008 authenticate no The problem is

Hi Felix > Dear Simon, > > every second IP-address is unwanted. We restarted? eno4: > > nmcli con down eno4; nmcli con up eno4 > > and the second address vanishes. Then after a few ours, the second ip > address reappears. That's really interesting. Doesn't NetworkManager also store other settings in a different location, not the ifcfg files? I think it does so and

Checks any entered address for DNS and NTP servers against previously entered ones in order to prevent duplicates. Resolves: rhbz#555373 Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 41 ++++++++++++++++++++++++-------------- scripts/ovirt-functions | 7 ++++++ 2 files changed, 33 insertions(+), 15 deletions(-) diff --git

given machine with C6 x86_64 (seen on C 6.6 but also before and probably still present on C6.7) only 1 interface, there is dhcp on this network (for kickstarting) but the machines have static ip's, and NO networkmanager installed contents of resolv.conf search some.domain.here nameserver x.x.x.x #dns1 nameserver y.y.y.y #dns2 change resolv.conf to: search some.newdomain.here nameserver

> Dear Simon, > > >> And can you diff the config of eno1 and eno4. > > # pwd > /etc/sysconfig/network-scripts Okay, nothing to find here. What about eno2, you also have two IP addresses there and even in the same subnet, is this wanted or not? Can the second address of eno2 be found in the ifcfg file? Both eno2 and eno4 have "scope global secondary dynamic"

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Jonathan Kreider via samba > Verzonden: woensdag 16 september 2020 2:20 > Aan: samba at lists.samba.org > Onderwerp: [Samba] AD DC DNS question > > OS = Ubuntu 18.04 in an LXD container > Samba 4.11.x and up > > Is there a way to have DNS resolution on the server

Hi All, I have 2 NICS in this system. CentOS 6.4 eth0 is the virtual IP from PFSense mapping connected to the router, works fine. eth1 is a second NIC that I have assigned a private IP to and connected it to a switch on the private network. I have many other private devices, so I know this setup works. When I connect the cable to the switch and bring up eth1 the system basically stops taking

Hello /etc/sysconfig/network-scripts/ifcfg-eth0 looks like this: # Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no IPV4_FAILURE_FATAL=yes UUID=cc2635ff-3c14-48ba-b19a-84c5b9d36a9d ONBOOT=yes DEVICE=eth0 BOOTPROTO=none HWADDR=00:50:56:01:00:01 BROADCAST=192.168.0.255 IPADDR=192.168.0.10 NETMASK=255.255.255.0 NETWORK=192.168.0.0