similar to: vmware promiscuous mode

Hello wine people, this is my first posting here. I am using the gimp printing ppd,cups and lpr on a hpdj842c. Wine release 20011226. On Debian woody with 2.4.17. Everything rocks so far except whenever i try to print wine freaks out and dies. Crossover is using Wine release 20010629. I have tried printing in linux and it works fine. I also have crossover installed (I actually paid for it).

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

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.

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

I am using CentOS 5.5 with KVM as a host and have a need for one guest to be able to have promiscuous read access to one port on the physical host (which is an HP BL460 G6 blade server with Intel 2 port 1Gb ethernet mezzanine card.) I initially tried to use PCI passthrough, but I was unable to get it to work. I set everything up as documented in RHEL documentation

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

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

List, A Cisco 7960 is registered to servers A and B, where B is the backup server, only used by the 7960 if A is unreachable. That is the behavior of these phones. A call comes from server B to the 7960, which is successful. The 7960 then tries to park the call via an attended transfer, so the 7960 calls 700 at serverA. However, the transfer fails, though I am not sure why. I have

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

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

Hi! I have a strange problem with shorewall on one of our routers. When i configure a rule like ACCEPT loc:192.x.x.x net tcp 80 this rules will only work if i do a tcpdump -i all port 80 After doing the tcpdump the clientrules works. When i don''t use tcpdump before the connection will be refused. Best regards, Kai.

Hi We have the following situation: A hypervisor using KVM-Qemu/libvirt with a single VM. The VM has the internal IP 192.168.122.151 on the default network pool using virbr0 on the hypervisor. We've set up netfilter rules to DNAT requests on one IP of the hypervisor to the VM. So, first of all, forwarding to the internal IP range is allowed: > $IPTABLES -I FORWARD -m state -d

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