similar to: Bridg and dhclient

If you select an option that's not listed during ipv4/ipv6 setup it will accept it without verification. This corrects that behavior and forces a valid option to be picked. --- scripts/ovirt-config-networking | 106 +++++++++++++++++++++------------------ 1 files changed, 58 insertions(+), 48 deletions(-) diff --git a/scripts/ovirt-config-networking b/scripts/ovirt-config-networking index

--- 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

Signed-off-by: Joey Boggs <jboggs at redhat.com> --- scripts/network.py | 8 ++++++-- scripts/ovirt-config-setup.py | 15 +++++++++++++++ 2 files changed, 21 insertions(+), 2 deletions(-) diff --git a/scripts/network.py b/scripts/network.py index fd78877..8159283 100644 --- a/scripts/network.py +++ b/scripts/network.py @@ -78,7 +78,6 @@ class Network:

AHOI! I've big trouble by setting up CentOS 6.3 for my new vDSL. As I've found out, the German Telekom is using VLAN7 for her internet-(data) connections. => http://workaround.org/blog/vdsl O.K. what I've done: The NIC where's my DSL-modem is connectet is eth0. cat /etc/sysconfig/network-scripts/ifcfg-eth0 # device for vDSL-modem DEVICE=eth0 HWADDR=00:30:1B:14:08:67

On 21 December 2015 at 03:37, Eugene Vilensky <evilensky at gmail.com> wrote: > On Wed, Dec 16, 2015 at 4:47 PM, Earl A Ramirez <earlaramirez at gmail.com> > wrote: > > > I don't see 'System' in any of the CentOS 7.2.1511 boxes or VMs that were > > recently upgraded: > > > > ?Hi Earl, > > Have you tried a new install?? I agree,

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

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. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes

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

We had problem using tagged vlans inside domU. Testing shows that this is caused by changing network interfaces in network-bridge script. Following patch should allow to use vlans in guest. Testing scenario: configure vlan network (e.g. vlan 1 on eth0 => eth0.1) start xend create domU and configure same vlan inside it You can see that vlan is still <interface>.<vlan_id>. You can

Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>>On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>>> Wed, Feb 21, 2018 at 04:56:48PM CET, alexander.duyck

Wed, Feb 21, 2018 at 09:57:09PM CET, alexander.duyck at gmail.com wrote: >On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: >> Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>>> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck

On Thu, Feb 22, 2018 at 12:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 09:57:09PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri

On Thu, Feb 22, 2018 at 12:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 09:57:09PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri

> On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen > <smooge at gmail.com> wrote: > >> On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen <aommundsen at gmail.com> >> wrote: >>> >>> Hi, >>> >>> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after >>> a >>> reboot of the first server the

On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen <smooge at gmail.com> wrote: > On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen <aommundsen at gmail.com> > wrote: >> >> Hi, >> >> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a >> reboot of the first server the network was unavailable. In IPMI console >>

On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri

On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri

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

On 12/16/18 4:59 PM, Marc Haber wrote: > Hi, > > I would like to run a network firewall as a VM on a KVM host. There are > ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP > or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs > 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. > > To save

- 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