similar to: Completely in despair - Xen and Windows domU

Hello i have some problems on 2.6.14 kernel dummy and iproute :) i have server with 2 nics : eth0 <> inet eth1 <> lan dummy0 (i want to shape incoming traffic from lan machine on this interface) my config: tc qdisc del dev dummy0 root tc qdisc add dev dummy0 root handle 1: htb tc class add dev dummy0 parent 1: classid 1:1 htb rate 100kbit ceil 100kbit tc class add dev dummy0

Have you tried to use NetworkManager ? After all ,anything network related should be done by it. [root at system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy ? Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. [root at system ~]# reboot Shared connection to glustera closed. [root at system ~]# uptime 03:23:44 up 0 min, ?1 user, ?load

No. Network Manager is always disabled on our builds since at least Cent5 days. The network stack has always been able to be managed properly without relying on Network Manager. Is that now an absolute requirement? It never has been prior. On Mon, Oct 26, 2020 at 6:26 PM Strahil Nikolov via CentOS <centos at centos.org> wrote: > > Have you tried to use NetworkManager ? > After

Requirement is a very strong word , but you should consider using it and here is a short demo why: - By default, RHEL uses NetworkManager to configure and manage network connections, and the /usr/sbin/ifup and /usr/sbin/ifdown scripts use NetworkManager to process ifcfg files in the /etc/sysconfig/network-scripts/ directory. [root at system ~]# ls -l /usr/sbin/ifup lrwxrwxrwx. 1 root root 22 21

Hello, I am having big problems with Xen virtual network interfaces. First I tried typical bridge support, no luck. The packets sent from dom0 to domU seemed to disappear somewhere. Then, to debug the problem I have set up a simple point-to-point link and still have the same problem. I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU. I have tried kernel 2.6.16.35 and 2.6.16.41. I

I am trying to configure load balancing for a couple of CentOS4 servers. In order to make it work, I need to add a hidden networking device on each server with the virtual IP. I found the following instructions on linuxvirtualserver.org for doing this, but they don't work. echo 1 > /proc/sys/net/ipv4/ip_forward ifconfig dummy0 0.0.0.0 up echo 1 >

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a linux system with 4 ethernet interfaces, eth0 goes to the internet, eth1, eth2, and eth3 are NAT''d LANs. I want to use an ingress filter to prioritize bandwidth (downstream from internet) to various IPs. I want to sett it up something like this.... eth0 <--[NAT]--> dummy0 <---> dummy1 <---> eth1,eth2,eth3 dummy1

hello ! i try to use a network technology on one single host, which wasn`t designed for that. to give a short overview of what i`m talking about: AoE is just like a "networked blockdevice" (just like nbd/enbd) - but without tcp/ip. AoE kernel driver is the "client end" (see this like an iSCSI initiator) - and an etherblade storage appliance is the "server end"

Anyone have any ideas? It's rather annoying that I can't get these to persist across reboots without using some kind of helper script. On Fri, Oct 16, 2020 at 6:37 AM Frank Even <lists+centos.org at elitists.org> wrote: > > Hello all, hoping someone can help me out here. > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > On Cent7

Hello all, hoping someone can help me out here. I cannot get dummy interfaces on a new Cent8 build to persist across reboots. On Cent7 - this is the process I use: Create Dummies: # cat /etc/modules-load.d/dummy.conf dummy # cat /etc/modprobe.d/dummyopts.conf options dummy numdummies=4 # ip link add dummy0 type dummy ## - repeating a/ ascending dummyN adapters for as many needed # service

Hi, Back in October I reported that I noticed a problem whereby flow control breaks down when openvswitch is configured to mirror a port[1]. I have (finally) looked into this further and the problem appears to relate to cloning of skbs, as Jesse Gross originally suspected. More specifically, in do_execute_actions[2] the first n-1 times that an skb needs to be transmitted it is cloned first and

Hi, Back in October I reported that I noticed a problem whereby flow control breaks down when openvswitch is configured to mirror a port[1]. I have (finally) looked into this further and the problem appears to relate to cloning of skbs, as Jesse Gross originally suspected. More specifically, in do_execute_actions[2] the first n-1 times that an skb needs to be transmitted it is cloned first and

tl;dr - a renamed dummy interface is not persisting across reboots on Cent6. I have a situation where I need to rename a dummy interface on my system. I have a total of 3 dummy interfaces: dummy0 dummy1 adummy0 I've been doing some puppet testing in a vbox VM to get this all sorted out to deploy to a group of boxes. Every time I reboot my VM, it comes up WITHOUT adummy0, but I notice

hi, i am getting an error when calling the impute.knn function (see the screenshot below). what is the problem here and how can it be solved? screenshot: ################## *** caught segfault *** address 0x513c7b84, cause 'memory not mapped' Traceback: 1: .Fortran("knnimp", x, ximp = x, p, n, imiss = imiss, irmiss, as.integer(k), double(p), double(n), integer(p),

hi, I want to share my odysse from yesterday until now with someone who might help me. (my real problem starts after the mass effect 3 part) So yesterday I bought MassEffect 3 after reading the topic on it http://appdb.winehq.org/objectManager.php?sClass=version&iId=25500 and http://appdb.winehq.org/objectManager.php?sClass=version&iId=25350 hmm doesnt sound to bad, lets give it a

Hi all, I managed to get all my VMs (5 in total) up and running in bridged mode with public IP addresses from my ISP. All are running Debian Etch in a Dom) of Debian Etch with Xen 3.1 using the instructions here: http://www.howtoforge.com/debian_etch_xen_3.1 But ideally I only want two of the DomUs on the public internet with the other three only on an internal network and the two

Hello, can I use the Lotus Domino LDAP Server as backend for Samba? Has anyone tried this, or some experiences in that? Mit freundlichen Gr?ssen / Kind regards Norman Trapp System Management objective partner GmbH Bergstrasse 45 D-69469 Weinheim Tel. +49 (0)6201 3986 24 Fax. +49 (0)6201 3986 12 _______________________________________________ objective partner - keep IT in e.motion Diese

Hi, I've downloaded and installed the Xen packages from backports.org in a box with sarge, and it doesn't work. That's the short story. Now the long one :-) The problem is that I can't bring up the domUs. This is the error displayed when I try: ~# xm create -c chen.cfg Using config file "/etc/xen/chen.cfg". Error: Device 0 (vif) could not be connected. Hotplug

Can someone verify that using fw as a filter in iproute2-2.6.11-050330 is broken. Doesn''t seem to work in any case and I saw an earlier post that would lead me to believe this is the case. If so does anyone have a temporary fix? Thanks, Troy