similar to: Promiscuous mode of bridge-networking in Dom0

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

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 would like to submit a use case we are here: our company make network probes with 1 administravia interface and the rest in promiscuous mode to listen traffic. I've made virtualized server with Qemu. All Qemu instances (with 2 tap) listen on: br0 (admin int) br1 (receive traffic) The need is each tap on br1 must listen *all* traffic (unicast, multicast...). For this, I sets

hi @all sometimes after a reboot the complete network is down the difference in the logs shows: in a failed reboot the eth0 does not entering promiscuous mode; in both cases the eth0 gets sucessful its ip configuration via dhcp - any idea ? the nic is a 3com 3c905C-TX/TX-M and the configuration is a suse 9.3 with xen-kernel 2.6.11.4-21.10-xen and xen 2.0.5.c ----------------[ failed reboot ]

Hi Everyone, Is it normal to see this in /var/log/message once a DomU starts up? kernel: device vifu22195 entered promiscuous mode These DomUs are for "untrusted" customers, so I do have iptables running which *should* prevent packets destined for other DomUs from appearing on the wrong DomU interface. Nonetheless, the message is still worrying Thanks

Good day. Found strange behavior in PV-domains. Application like tcpdump or iftop require promiscuous mode for interface. And this feature is disabled by default, as I understand. message from iftop: pcap_open_live(eth0): eth0: You don''t have permission to capture on that device (socket: Address family not supported by protocol) As I understand promiscuous:on in other-config for vif

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

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

Hi, I am trying to set up a uPnP server on a Linux box (Debian Sarge Stable kernel 2.6.8). uPnP works using multicast packages for locating servers. This does however seem to fail unless I set the relevant NIC in promiscuous mode. If I do so, it works well. I have added ip route add 224.0.0.0/4 dev eth0 and echo 1 >/proc/sys/net/ipv4/ip_forward and the kernel is set up to enable

As a heads up to everyone, VMware requires you to take special precautions when trying to put a virtual nic into promiscuous mode, which is required for Xen networking to work. I spent a fair amount of time diagnosing Xen network problems when it wasn''t Xen at all. As I was just beginning to learn Xen, I was convinced it was something I was doing wrong, when it wasn''t at

Hello all, Playing with Xen on GNU/Debian Lenny, I just discovered that all my virtual network cards are in promiscuous mode by default. Changing that manually does not seems to change anything (that is, everything still works great). Is there any reason to have virtual network cards in promiscuous mode ? And where can I change this default behaviour ? Thanks, JB

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

Author: prafull Repository: /hg/zfs-crypto/gate Revision: 95c55f804e6251aa87677ff29f6de677f407d04d Log message: 6375481 eri driver doesn''t reset promiscuous mode correctly (fix lint) Files: update: usr/src/uts/sun/io/eri.c

Hi all, I am trying to enable promiscuous mode on a kvm switch due to sniff all traffic using snort installed on a kvm guest. I have found a partial solution configuring this bridge with "brctl setaging br0 0", but all vms sees all traffic. I think the soultion is using ebtables but I didn't found any doc about how can I do under kvm (and upstream recommends disable this

Hi, I am looking for some direction on how to configure KVM networking so that a promiscuous bridge/host nic/guest nic allows two different network monitoring packages to sniff the same physical traffic. The idea is to run a commercial package on the CentOS 6.5 host and Snort, via Security Onion, on the guest, both being fed by a physical switch SPAN or physical firewall TAP. The host has two

Hi, I had a quick question. I''ve few machines available in a cluster. Now, if I want to install Xen on them, do I individually install in all of them (one by one); or can I have on single image available over a network/SAN and can I boot Xen from there? Are there any other smarter ways to do that? Thanks, Amitayu _______________________________________________ Xen-users mailing list

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

Hi, I have a Centos5 machine running xen 3.0.3-41 with two NICs each on its own subnet: 192.168.1.x and 192.168.0.x. All DomUs can talk to each other OK through two xen bridges. There are 3 DomUs: Dom0, Dom1 and Dom2 The scenario: I''m trying to capture packets on Dom2 on 192.168.0.x from external devices that are sending SIP stuff to Dom1, but fail to capture any packets. I

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''ve got a HT-enabled dual-preocessor Xeon machine, on which I''m running xen-3.0-testing. I''ve specified entries like the following in the configuration scripts for DomU''s to prevent them running on CPU 0: cpus = "1-4, ^0" My question is 1. Does this type of specificaiton mean Dom0 would *always* be running on CPU0? Please note that this