Re: Netmap - Vale switch - tcp problem

Il giorno sab 6 giu 2020 alle ore 20:32 Anthony Arnaud < antho.arnaudi...@gmail.com> ha scritto: > This works!! > A good news! > It works even if I connect the nic to vale switch directly from ssh, the > connection does not drop like before your patch. > Yes, connecting the vtnet0 to the vale swi

Re: Netmap - Vale switch - tcp problem

This works!! A good news! It works even if I connect the nic to vale switch directly from ssh, the connection does not drop like before your patch. Can you list the steps to setup the bridge in your tests? I thing "ifconfig bridge create" etc. Now I have to understand why it doesn't work in my prev

Re: Netmap - Vale switch - tcp problem

Il giorno ven 5 giu 2020 alle ore 18:16 Anthony Arnaud < antho.arnaudi...@gmail.com> ha scritto: > Hi Vincenzo, > Thank you for your answers. > I upgraded a guest machine in proxmox env to FreeBSD 13.0-CURRENT #0 > r361830. > After that I compiled the tools as usual from /src/tools/tools/netmap >

Re: Netmap - Vale switch - tcp problem

Hi Vincenzo, Thank you for your answers. I upgraded a guest machine in proxmox env to FreeBSD 13.0-CURRENT #0 r361830. After that I compiled the tools as usual from /src/tools/tools/netmap I configured 2 NIC vtnet vtnet0 with an ip 192.168.1.x vtnet1 without ip and csum disabled as mirror of vtnet

Re: Netmap - Vale switch - tcp problem

Hi Anthony, I fixed more bugs in the vtnet driver (in FreeBSD-CURRENT). As of r361760, I'm now able to run the following steps in a VM with a vtnet device # ifconfig vtnet0 -txcsum -rxcsum -tso4 192.168.100.2/24 # vale-ctl -h vale:vtnet0 # netperf -H 192.168.100.1 # Run a netperf TCP_STREAM tes

Re: Netmap - Vale switch - tcp problem

Hi Anthony, I think there is more than a bug, drivers-related, that show up when you attach the interface to a vale switch. I've found and fixed some related to if_vtnet (see below). In any case, in my tests there is no difference between TCP traffic and other (UDP, ICMP, STP,...). The issues are

Re: Netmap - Vale switch - tcp problem

Hi Vincenzo, To simplify the scenario I have installed from scratch FBSD12.1 on a new machine, without any virtualization env. I have encountered the same problem, when i attach an ethernet interface to vale switch (in this case an intel card em5) the tcp traffic disappears and tcpdump shown only

Re: Netmap - Vale switch - tcp problem

Il giorno ven 29 mag 2020 alle ore 19:01 Anthony Arnaud < antho.arnaudi...@gmail.com> ha scritto: > Hi Vincenzo, > > thanks for your hints! > I rebooted my guest FBSD 12.1 machine, and I have perfomed your steps > > #ifconfig vtnet1 -txcsum -rxcsum -tso4 -tso6 up promisc > > vtnet1: > flags=28943

Re: Netmap - Vale switch - tcp problem

Hi Vincenzo, thanks for your hints! I rebooted my guest FBSD 12.1 machine, and I have perfomed your steps #ifconfig vtnet1 -txcsum -rxcsum -tso4 -tso6 up promisc vtnet1: flags=28943 metric 0 mtu 1500 options=6c04b8 ether 0e:bd:ec:7a:08:06 media: Ethernet 10Gbase-T statu

Re: Netmap - Vale switch - tcp problem

Hi, I was trying to reproduce your problem (same FreeBSD release as yours). It looks like there is some sort of bad interaction with LRO. Starting from a fresh boot, if you keep lro enabled, e.g. # ifconfig vtnet0 -txcsum -rxcsum -tso4 -tso6 # vale-ctl then I experience no problem (TCP

Re: Netmap - Vale switch - tcp problem

I already disabled the checksum, the vtnet config is: ifconfig vtnet1 -txcsum -rxcsum -tso4 -tso6 -lro -txcsum6 -rxcsum6 -vlanmtu -vlanhwtag -vlanhwfilter -vlanhwtso -vlanhwcsum up promisc vtnet1: flags=28943 metric 0 mtu 1500 options=1800a8 ether 0e:bd:ec:7a:08:06 media:

Re: Netmap - Vale switch - tcp problem

On Thursday, May 28, 2020, Anthony Arnaud wrote: > Hi everyone! > I would like to create a vale switch with an interface attached with the > host stack and some virtual. > My env is a VM with FBSD-12.1 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 > GENERIC amd64 > and VirtIO support. > > I performe

Netmap - Vale switch - tcp problem

Hi everyone! I would like to create a vale switch with an interface attached with the host stack and some virtual. My env is a VM with FBSD-12.1 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 and VirtIO support. I performed: vale-ctl -h vale0:vtnet1 vale-ctl -n vi0 vale-ctl -a vale0:vi0

Re: netmap/vale periodic deadlock

Hi, $ bridge -h for usage. Yes, bridge is just a simple example program, and stays in foreground. Probably using daemon(8) you can turn it into a daemon. Cheers, Vincenzo 2017-11-22 10:18 GMT+01:00 Harry Schmalzbauer : > Bezüglich Harry Schmalzbauer's Nachricht vom 22.11.2017 09:39 (localt

Re: netmap/vale periodic deadlock

Bezüglich Harry Schmalzbauer's Nachricht vom 22.11.2017 09:39 (localtime): > Bezüglich Vincenzo Maffione's Nachricht vom 22.11.2017 09:04 (localtime): >> >> 2017-11-21 21:48 GMT+01:00 Harry Schmalzbauer > >: >> >> Bezüglich Vincenzo Maffione's Nachricht vom 21.11.201

Re: netmap/vale periodic deadlock

Bezüglich Vincenzo Maffione's Nachricht vom 22.11.2017 09:04 (localtime): > > > 2017-11-21 21:48 GMT+01:00 Harry Schmalzbauer >: > > Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 > (localtime): > … > > > > If this is the case, althou

Re: netmap/vale periodic deadlock

2017-11-21 21:48 GMT+01:00 Harry Schmalzbauer : > Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): > … > > > > If this is the case, although you are allowed to do that, I don't think > > it's a convenient way to use netmap. > > Since VLAN interfaces like vlan0 do not have

Re: netmap/vale periodic deadlock

Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): … > > If this is the case, although you are allowed to do that, I don't think > it's a convenient way to use netmap. > Since VLAN interfaces like vlan0 do not have (and cannot have) native > netmap support, you are falling b

Re: netmap/vale periodic deadlock

Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 14:26 (localtime): > It may be that your is not a deadlock but some kind of crash. Enabling > debugging features would probably help (e.g. to get a stack trace). > Maybe your lockup/crash happened because you did some reconfiguration > (ring si

Re: netmap/vale periodic deadlock

It may be that your is not a deadlock but some kind of crash. Enabling debugging features would probably help (e.g. to get a stack trace). Maybe your lockup/crash happened because you did some reconfiguration (ring size, number of rings, etc.) while netmap was active and doing so you triggered some

Re: netmap/vale periodic deadlock

Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): > Hi, > It's hard to say, specially because it happens after two days of > normal use. > Can't you enable deadlock debugging features in your kernel? > https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/k

Re: netmap/vale periodic deadlock

Hi, It's hard to say, specially because it happens after two days of normal use. Can't you enable deadlock debugging features in your kernel? https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html However, if I understand correctly you have created some

netmap/vale periodic deadlock

Hello, sorry for annoying with another question/problem. I'm using netmap's vale (on stable/11) for bhyve(8) virtio-net backed SDN. The guests – unfortunately in production already – quit network services (resp. are not able to transceive any packets anymore) after about 2 days; repeatedly and

Re: Netmap vale + bridge on -STABLE

OK, I am running current now. If I run: tcpdump -ni vale0:2 -w /tmp/2 & tcpdump -ni vale0:1 -w /tmp/1 & pkt-gen -i vale0:0 -f tx I get half of all generated traffic on /tmp/2 and the other half of /tmp/1. I guess this is the expected behavior, different from what I expected. Is that the expecte

Netmap/VALE

se already supported in Netmap/VALE? I'm not able to find any documentation on whether that is do-able. Also, if Netmap/VALE currently don't support the "veth" interfaces, how would I go about creating that support? Regards, Stan ___ freebs

Re: [netmap/vale-ctl] when could process packet

on. > > Cheers > Luigi > > On Thursday, September 18, 2014, upyzl wrote: > >> Hi, >> >> I think it's right place to talk about FreeBSD 10 - netmap question >> (location at FreeBSD 10: /usr/src/tools/tools/netmap ; with kernel device >> netmap

Re: [netmap/vale-ctl] when could process packet

>> Jim >> >> > On Sep 17, 2014, at 9:39 PM, upyzl wrote: >> > >> > Hi, >> > >> > I think it's right place to talk about FreeBSD 10 - netmap question >> > (location at FreeBSD 10: /usr/src/tools/tools/netmap ; with kernel >> d

Re: [netmap/vale-ctl] when could process packet

rnel device > netmap on) > > I'm (entry) study on openflow software switch based on netmap/vale > > It seems very simple in vale-ctl.c and hard to add features for packet > process (such as flow match and forward actions apply) > > Could anyone gi

[netmap/vale-ctl] when could process packet

Hi, I think it's right place to talk about FreeBSD 10 - netmap question (location at FreeBSD 10: /usr/src/tools/tools/netmap ; with kernel device netmap on) I'm (entry) study on openflow software switch based on netmap/vale It seems very simple in vale-ctl.c and hard to add features