similar to: Network problem: packets are lost in domU

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

A site I administer has dual T1''s. We have this set up according to NANO-HOWTO[1] using Julian''s routes patch on a late model 2.4 kernel. All is well, has been working well for a long time. Recently one of our T1 providers went belly up and we got something better. Now we have a /28 where previously we only used one IP per interface. Present interfaces: eth0 - T1#1, single

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

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, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi, I''m using CentOS 5.5 x86_64 xen 3.43 from gitco.de and I have an Openvox A1200P voip card and am passing it thru to another centos 5.5 DomU, when I 1st start the domain driver loads and everything seems quite nice and the device works, but after a reboor of the DomU, this is shown on my Dom0 dmesg Here''s Dom0 info [root@xen ~]# dmesg Bootdata ok (command line is ro

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

My domains dont see any traffic until you try to connect out from within the domain. Tried this several times and it was consistent. I have no firewall either. running each domain on different cpu probably doesn''t help, although Im no network expert. Here is some info. ================ [root@a root]# xm info system : Linux host : a.b.com release

Hello! I am using xen some years now and it just runs without any problems. But now one customer needs a stupid WinXP domU and I am trying to get this running for about two weeks... I am using 2.6.26-2-xen-amd64 kernel, set up a dummy network auto dummy0 allow-hotplog dummy0 iface dummy0 inet static address 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255 xend-config: (network-script

I''m working with LEAF boxes as gateway machines. I''m trying to implement Proxy-ARP to build a bandwidth manager for my network. I''ve gone as per the lartc howto to implement a transparent bridge in an existing network and plan to put in my tc script after this. I''m configuring the box as a standalone one before plugging it into the network. I''m getting

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 >

Thanks a lot , Everythings is working now. Quoting Alex Martin <alex@rettc.com>: > > > At this point point ip addr show: > > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 scope host lo > > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000

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

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

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

So Working on CEntOS 5 I am trying to sett up Xen with 2 bridges, one that connects dom0 and most of the domU to the physical card and the out to the network. Got that figured out no problem, now i want to have a second bridge that runs a local network for all the doms that doesn''t connect to the network. With code I have found used in multiple places I can easily get 2 bridges, and

Hi, this is my first message to the list and I want to thank the the autor for developing Shorewall. And now the problem. I''m using version 1.3.13 and I have eth0 (IP a.b.c.d/24) as a public interface. I have an alias on eth0:0 (address a.b.c.e/24) and my dns servce listens on this IP (in this moment the dns is stopped). This is my policy file: #SOURCE... fw all