search for: promiscous

In current Crossbow''s implementation, vlan tag seems to be unconditionally retained for promisc mode listener even when MAC_OPEN_FLAGS_TAG_DISABLE is not specified. I saw comments in mac_rx_deliver() saying that this is deliberately designed like this. I''m wondering why we design it like this (choose not to respect MAC_OPEN_FLAGS_TAG_DISABLE flag for promisc mode listener)? Or

Hello, Is it normal that eth0 in domain0 is in promisc mode ? [root@vmaster ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0B:CD:4D:C4:8A inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask: 255.255.255.248 inet6 addr: fe80::20b:cdff:fe4d:c48a/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:3602633 errors:0

> From: "Roy" <roy@xxx.lt> > > I want to set interface to promisc mode and do all routing with iptables. > Is it somehow possible? as I see now kernel do not pass everything to > ipables. > > Basicaly I want to ignore ethernet addess and use only ip for routing. > > I suppose this may require writting special kernel driver or it > is possible > in

...de (packets sent to the VM MAC) */ + if (promisc) { + ret = ioctl(fd, SIOCGIFFLAGS, &req); + if (ret < 0) + perror("SIOCGIFFLAGS failed\n"); + req.ifr_flags |= IFF_PROMISC; + ret = ioctl(fd, SIOCSIFFLAGS, &req); + if (ret < 0) + fprintf(stderr, "SIOCSIFFLAGS to promiscous failed\n"); + } + + ret = fcntl(fd, F_SETFL, fcntl(fd, F_GETFL) | O_NONBLOCK); + if (ret < 0) + fprintf(stderr, "O_NONBLOCK set failed\n"); + + return fd; +} + +static void raw_cleanup(VLANClientState *vc) +{ + struct ifreq req; + RAWState *s = vc->opaque; + + qemu_set_fd_hand...

...de (packets sent to the VM MAC) */ + if (promisc) { + ret = ioctl(fd, SIOCGIFFLAGS, &req); + if (ret < 0) + perror("SIOCGIFFLAGS failed\n"); + req.ifr_flags |= IFF_PROMISC; + ret = ioctl(fd, SIOCSIFFLAGS, &req); + if (ret < 0) + fprintf(stderr, "SIOCSIFFLAGS to promiscous failed\n"); + } + + ret = fcntl(fd, F_SETFL, fcntl(fd, F_GETFL) | O_NONBLOCK); + if (ret < 0) + fprintf(stderr, "O_NONBLOCK set failed\n"); + + return fd; +} + +static void raw_cleanup(VLANClientState *vc) +{ + struct ifreq req; + RAWState *s = vc->opaque; + + qemu_set_fd_hand...

From: Andy Lutomirski <luto at amacapital.net> Once virtio starts using the DMA API, we won't be able to safely DMA from the stack. virtio-net does a couple of config DMA requests from small stack buffers -- switch to using dynamically-allocated memory. This should have no effect on any performance-critical code paths. Cc: netdev at vger.kernel.org Cc: "Michael S. Tsirkin"

From: Andy Lutomirski <luto at amacapital.net> Once virtio starts using the DMA API, we won't be able to safely DMA from the stack. virtio-net does a couple of config DMA requests from small stack buffers -- switch to using dynamically-allocated memory. This should have no effect on any performance-critical code paths. Cc: netdev at vger.kernel.org Cc: "Michael S. Tsirkin"

Hello, I've got a very strange problem. Lately I've been setting up my linux servers for network (layer2) redundancy with a bridge interface containing two ethernet interfaces connecting to two switches. So far I didn't have any problems with it, but now a very strange thing happens with a new server I'm installing. The server is an ibm x346 having two onboard BCM5721 cards, the

On Tue, Oct 27, 2015 at 10:30:19PM -0700, Andy Lutomirski wrote: > From: Andy Lutomirski <luto at amacapital.net> > > Once virtio starts using the DMA API, we won't be able to safely DMA > from the stack. virtio-net does a couple of config DMA requests > from small stack buffers -- switch to using dynamically-allocated > memory. > > This should have no effect

----- Forwarded message from John <strgout@mail.unixjunkie.com> ----- Date: Mon, 15 Dec 2003 17:58:15 -0600 From: John <strgout@mail.unixjunkie.com> To: freebsd-stable@freebsd.org Subject: interface bonding User-Agent: Mutt/1.4i Is there any way to bond sniffer interfaces? I've read a little on netgraph and it seems like i maybe able to use that but i'm not sure how to go

Hi folks, the standard config uses bridging with promiscous mode for eth0 (understandable) and the vifs (why that?). Does that mean that EVERY vif receives EVERY packet crossing the bridge - even those packets destined for other domains? Documentation compares bridging to "a cross over cable between virtual machine and domain0" which would th...

Greetings all, I have tried to find a discussion of the removal of support for the PROMISC interface flag with the iproute2 tools. - it used to work (iproute2-2.2.4-$ANCIENT) - there''s a comment about it in the iproute docs [0] - (un-)setting the flag with ifconfig still works Can anybody point me to the discussion (linux-net, maybe?) where support for setting the PROMISC flag

Hello All, While implementing CBQ for my network card , i found it has PROMISC mode enabled by default while installing RedHat-7.3 . What is it ? Is any way related to security. Regards Vanitha

Hello, There is a xen setup in which "brctl show" gives the following output. bridge name bridge id STP enabled interfaces eth1 8000.003048c9d4df no peth1 vif1.0 vif2.0

When sending control commands, virtio net sets up several buffers for DMA. The buffers are all part of the net device which means it's actually allocated by kvmalloc so it's in theory (on extreme memory pressure) possible to get a vmalloc'ed buffer which on some platforms means we can't DMA there. Fix up by moving the DMA buffers into a separate structure. Reported-by: Mikulas

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

From: Andy Lutomirski <luto at amacapital.net> Once virtio starts using the DMA API, we won't be able to safely DMA from the stack. virtio-net does a couple of config DMA requests from small stack buffers -- switch to using dynamically-allocated memory. This should have no effect on any performance-critical code paths. Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc:

On Tue, Oct 27, 2015 at 11:38:58PM -0700, Andy Lutomirski wrote: > From: Andy Lutomirski <luto at amacapital.net> > > Once virtio starts using the DMA API, we won't be able to safely DMA > from the stack. virtio-net does a couple of config DMA requests > from small stack buffers -- switch to using dynamically-allocated > memory. > > This should have no effect

...en ping in de VLAN 2 from one server to the other but without success. I tried the tcpdump also on de XCP1.6 host ''tcpdump -n -i eth1 proto ICMP'' no success , also i tried this with the xenbr1 and vif2.5 but still not getting any ICMP packets through. So i tried the XEN bridge - promiscous mode brctl setageing xenbr1 0 ifconfig eth1 promisc Still not working. I tried this also on pif-param-set uuid=xxxxxxxx other-config:promiscous=´on´ and the vif-param-set uuid = xxxxxxx other-config:promiscous=´on´ still I can not see any ICMP packet getting through the XCP1.6 server. I plug in...

Hi When I start arpwatch or tcpdump the Ethernet card eth0 goes into promiscuous mode but I cannot see it with ifconfig eth0 or ip link show. The only way I can see it is when I looked at dmesg. Ifconfig uses the old style IOFLAG way to determine this but looking into ip code this is supposed to work even with newer kernels (I''m on 2.6.17 now with the latest iproute package) I found