similar to: no PROMISC mode ..

Add raw network backend option which uses a packet socket to provide raw networking access. Once the socket is opened it's bound to a provided host interface, such that packets received on the interface are delivered to the VM and packets sent by the VM are sent to the interface. This is functionally similar to the existing pcap network backend, with the same advantages and problems.

Add raw network backend option which uses a packet socket to provide raw networking access. Once the socket is opened it's bound to a provided host interface, such that packets received on the interface are delivered to the VM and packets sent by the VM are sent to the interface. This is functionally similar to the existing pcap network backend, with the same advantages and problems.

Please see the following thread to get some context on this http://marc.info/?l=linux-netdev&m=121564433018903&w=2 Basically the issue is that current multi-cast filtering stuff in the TUN/TAP driver is seriously broken. Original patch went in without proper review and ACK. It was broken and confusing to start with and subsequent patches broke it completely. To give you an idea of

Please see the following thread to get some context on this http://marc.info/?l=linux-netdev&m=121564433018903&w=2 Basically the issue is that current multi-cast filtering stuff in the TUN/TAP driver is seriously broken. Original patch went in without proper review and ACK. It was broken and confusing to start with and subsequent patches broke it completely. To give you an idea of

I am still unable to get the following command to work correctly. The x's replace the correct entry obviously. smbclient -Lboss -Uxxxxxx%xxxxxxxx I decided to run the command as root preceeded by 'truss' so I could generate a debug output. This is the output from the command without 'truss' Domain=[BOSS] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename

On Fri, Dec 01, 2017 at 05:10:37AM -0500, wexu at redhat.com wrote: > From: Wei Xu <wexu at redhat.com> > > tun_recvmsg() supports accepting skb by msg_control after > commit ac77cfd4258f ("tun: support receiving skb through msg_control"), > the skb if presented should be freed no matter how far it can go > along, otherwise it would be leaked. > > This

From: Wei Xu <wexu at redhat.com> tun_recvmsg() supports accepting skb by msg_control after commit ac77cfd4258f ("tun: support receiving skb through msg_control"), the skb if presented should be freed no matter how far it can go along, otherwise it would be leaked. This patch fixes several missed cases. Signed-off-by: Wei Xu <wexu at redhat.com> Reported-by: Matthew Rosato

Hi Graham Can you perhaps share with me the mr-mips metarouter image you are using? Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Tue, Jan 19, 2016 at 8:01 PM, Graham Cobb <g+tinc at cobb.uk.net> wrote: > On 19/01/16 03:57, Yazeed Fataar wrote: > > Hi Marek > > > > I managed to setup everything in openwrt. However I am getting errors > > when

I''m running Xen 3.0.2 on a system that''s based on Slackware 10.2 as Dom0. DomU is also slackware 10.2. Am using the kernel that came with 3.0.2 - no custom config, just a "make world", etc.. Did have to add grub of course. When I start up xend, I get the following on /var/adm/messages: Apr 23 21:04:11 rc25 kernel: Bridge firewalling registered Apr 23 21:04:11 rc25

>[root@localhost ~]# /etc/xen/scripts/network-bridge start > >Device "static" does not exist. > >usage: ifdown <device name> > >Device "static" does not exist. > >Cannot find device "static" > >SIOCGIFFLAGS: No such device requirements: - Interface (eth1) must be "up". (ifup eth1) (setting "ifconfig eth1

On 19/01/16 03:57, Yazeed Fataar wrote: > Hi Marek > > I managed to setup everything in openwrt. However I am getting errors > when trying to run tinc daemon. Below is my debug output. Please help.. > How do I fix tunnel interface error? > > root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d3 > > tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 3 > >

Hi Graham Regarding the tun lib , see mine. root at OpenWrt:~# /lib/modules/3.3.8/tun.ko And like i mention to Maxim , i have tinc running in a Linux Debian environment with 4 nodes successfully. I am experimenting now in openwrt due to the "light weight" environment. Regards Yazeed Fataar <yazeedfataar at hotmail.com> On Tue, Jan 19, 2016 at 8:27 PM, Yazeed Fataar

Hi Marek I managed to setup everything in openwrt. However I am getting errors when trying to run tinc daemon. Below is my debug output. Please help.. How do I fix tunnel interface error? root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d3 tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 3 /dev/net/tun is a Linux ethertap device Executing script tinc-up ifconfig: SIOCGIFFLAGS: No

Hi my friends, I am running into a problem with my NIC. [root@xxxx ~]# ifup eth0 Error for wireless request "Set Encode" (8B2A) : SET failed on device eth0 ; No such device. SIOCGIFFLAGS: No such device Failed to bring up eth0. eth0 is not a wireless device. Below are some information about my host: [root@xxxx ~]# lspci |grep -i ether 00:04.0 Ethernet controller: Intel Corporation

Hi, I tried already a long time to enable network in my domU but I always fail with: # ifconfig eth0 192.168.0.1 up SIOCSIFADDR: No such device SIOCGIFFLAGS: No such device Do I need to load a kernel module? I use OpenSuse 10.2 with kernel 2.6.18.8-0.5-xen (for both domU and dom0). My config: kernel = "/boot/vmlinuz-xen" ramdisk = "/home/jens/initrd.gz" memory = 1024 name

I dont think its a OS problem, Im using suse 8.1. If you log into the windows box as root you can see the groups and the users in the groups. Any other user including domain admins can not. This would indicate that there is a problem with samba, either with ACLs accessing group information or passing group/user information from the system to a smbd process owned by a user other than root.

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

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

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