similar to: Xen''s interface in promiscuous mode

Hello, I have understand that : ---------------------------- guest ---------------------------- driver_device0_guest ---------------------------- hypervisor ---------------------------- driver_device0_hypervisor ---------------------------- device0 ---------------------------- in order to access to a device, a guest use driver_device0_guest The

Hi, im using a fedora core 8 domU and fedora core 8 as my dom0 on xen3.1.0-13, my config file reads: kernel = "/boot/vmlinuz-2.6.21-2950.fc8xen" ramdisk="/boot/initrd-2.6.21-2950.fc8xen-no-scsi.img" memory = 428 name = "fedora1.fc8" vif = [ ''mac=00:16:3e:00:00:03,ip=192.168.2.105'' ] dhcp = "off" netmask = "255.255.255.0" gateway

Hello Everyone, I recently had a question that got no responses about GFS+DRBD clusters for Xen VM storage, but after some consideration (and a lot of Googling) I have a couple of new questions. Basically what we have here are two servers that will each have a RAID-5 array filled up with 5 x 320GB SATA drives, I want to have these as useable file systems on both servers (as they will both be

Hello, After a few of us have spent a week google''ing around for answers, I feel compelled to ask this question: how do I stop packet loss between my dom0 and domU? We are currently running a xen-3.3.0 (and have tried with xen-3.2.1) on a Gentoo system with 2.6.18 kernel for both domU and dom0. We have also tried a 2.6.25 kernel for dom0 with exactly the same results. The goal is to

I have a really basic question (I think). We have two boxes connected to a lan segment on a hub. One is a Windows box running "Show Traffic", the other is a CentOS 5 Linux box running "ntop". Both boxes should be able to sniff all of the traffic on that hub (not a switch). The Windows box does just fine, Show Traffic is able to display traffic destined for other boxes

El Lunes 01/02/2016, Daniel Ruiz Molina escribi?: > Hi, > > After installing CentOS 7 in a server with 2 NICs, system detects eth0 > and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as > eth1. I have forced HWADDR attribute in > /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting, > order is the same... > > How can I solve it? >

Hi list, I have been using xen for a while with success on the following environment: Hardware: Dell PowerEdge 2950 / 2GB Ram / Intel(R) Xeon(R) CPU / 800 GB RAID 5 System: Debian etch Xen packages: # dpkg -l | grep xen libc6-xen linux-image-2.6.18-6-xen-686 linux-modules-2.6.18-6-xen-686 xen-hypervisor-3.0.3-1-i386-pae xen-ioemu-3.0.3-1 xen-linux-system-2.6.18-6-xen-686 xen-tools

El Lunes 20/03/2017, PJ Welsh escribi?: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it. > On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes <johnny at centos.org> wrote: > > On

On 03/25/09 12:30, James Carlson wrote: > Girish Moodalbail writes: > >> bash-3.2# dladm show-link >> LINK CLASS MTU STATE PROMISC OVER >> e1000g0 phys 1501 up off -- >> e1000g1 phys 1502 up on -- >> > > That (plus or minus some column alignment) seems

Hello, I have been using the bridging facilities provided by Linux (vanilla 2.6.7 SMP with UML skas host patch applied) to bridge a regular physical ethernet network (on interface eth0) with a virtual network (on interface tap0, cf uml_switch, http://user-mode-linux.sourceforge.net/networking.html). A couple of virtual machines (run using user-mode linux, a tool that enables you to run linux

Hi there -- I want to have eth1 on my system run in promiscuous mode. I modified the /etc/sysconfig/network-scripts/ifcfg-eth1 file to read as follows: DEVICE=eth1 BOOTPROTO= ... ONBOOT= TYPE=Ethernet ... I reboote the system and when I did an /sbin/ifconfig, eth1 appeared without an ip address. I did a check in the /var/log/messages file and while eth0 is in promiscuous mode, eth1 does not

Windows make any "Levenshtein distance" into domains and fix them??? ummm.... ----- Mensaje original ----- De: "Ing. Luis Felipe Domínguez Vega" <luis.dominguez at mtz.desoft.cu> Para: "Sonic" <sonicsmith at gmail.com> CC: "samba" <samba at lists.samba.org> Enviados: Lunes, 20 de Febrero 2017 15:08:59 Asunto: Re: [Samba] strange auth

Can I ask you a quick question? I''ve set up bridge-networking for Xen 4.1 (xen-4.1.3-25.el5.22) and networking was being done properly for Dom0 and DomUs. However, I noticed that Dom0 receives a lot of network interrupts or network packets even when they were not actually meant for either Dom0 or DomU. Now, here are the questions: 1. Dom0 is acting in promiscuous mode, right? 2. If

How can I find out that someone is using it's network card in promiscuous mode in a subnet? Thank you!

I have just noticed this message in my kernel logs, reporting the possibility of an error with my memory. This would go a long way towards explaining the problems i''ve been having. This particular error is occuring when i''m not running xen so is obviously not something brought on by xen itself. The strange thing is that the NMI error is always followed by the TLAN: eth0: Adaptor

Hola a todos, a ver si me pueden echar una mano que estoy atascado.tengo estas dos tablas: > head (intento1)      codigo     categoria         talla             num1       1                904                400               12       1                904                460               13       1                904                470               44       1                904  

On 03/21/2017 07:48 AM, PJ Welsh wrote: > On Mon, Mar 20, 2017 at 5:21 PM, Ricardo J. Barberis > <ricardo at palmtx.com.ar <mailto:ricardo at palmtx.com.ar>> wrote: > > El Lunes 20/03/2017, PJ Welsh escribi?: > > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > > Thanks > > PJ > > Edit grub's entry

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

Hi, I hope someone can help me, I cannot seem to get a system's ethernet interface to correctly work in promiscuous mode... I have a Centos 6.4 system with 2 bnx2 interfaces on it. I have set up eth1 in promiscuous mode and am sending traffic to it using the port mirroring configuration on a Nortel 3510-24T switch. The switch reports that it is sending a fair amount of traffic to the

Hello everyone, I''m new in contributing and i saw in the contributing-guides, that i have to write an email at this list. I hope, that''s the right place for this. If it''s not, i''M really sorry.. ;) Could someone please give me feedback about this lighthouse-ticket?