similar to: [Bridge] Best strategy for forward all packets (simulate promiscuous mode)

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, i'm rather new to kvm. now i set up a centos 7 guest on a centos 6 kvm host. when i try to use bridged networking in the centos7 guest this works for the interface that uses eth1/br1 on the host. when i try to use a second interface in the guest with eth0/br0 on the host this brings the host interface down as soon as i do ip configuration in the guest (so it seems). eth0 shall have

Hi, I'm not sure but I think I suffer under the same problem with a bit different setup with squeeze testing and xen 4.0rc5. In fact I'm using bridges in the dom0 and the connections to the domU get lost sporadically. In don't see where's a solution to the problem... Is it now a bug? When it's an iptables bug, where's the corresponding bug in the iptables bugtracker

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

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

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

Using a Linux bridge I see that none of the interfaces is set to promiscuous mode but on the other hand I don't see any dev_unicast_xxx calls in the bridge code... for the case of one of the interfaces being a physical NIC (e.g eth1), what's the magic that makes the NIC RX filtering be willing to accept frames whos dest mac isn't the NIC "primary" unicast mac? Also is there

Hi, I saw a nice mail about bridging in Xen at http://article.gmane.org/gmane.comp.emulators.xen.user/9538. Can I ask you a quick question? I''ve set up bridge-networking for Xen 3.0and 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.

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

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

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 have an old system. The guest there is defined with: ? <os> ??? <type arch='x86_64' machine='pc-q35-rhel8.2.0'>hvm</type> ? </os> When I try to migrate this guest to a new system I get the error: error: internal error: unable to execute QEMU command 'blockdev-add': Failed to connect socket: Permission denied On the new host I see the

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

Hi folks :), I migrated the host from the Debian Squeeze to Ubuntu 12.10. Old containers work but I can't use the ssh command, /dev/tty is missing. On a new container, /dev/tty is here. The libvirt configuration is the same. Any ideas? Thanks. -- Sebastien Douche <sdouche at gmail.com> Twitter: @sdouche / G+: +sdouche

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

Hi List, I''m in the process of setting up softflowd 0.9.9 on a Centos 6.4 system (compiled from source tarball). The daemon will listen to an unused interface that is receiving port mirrored traffic (a.la. Span port) I am planning on using the softflowd init script and sysconfig file provided in the tar ball. Do I need to manually put the unused interface into promiscuous mode, or