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
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
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
>
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
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
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
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
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
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
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
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:
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
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
13 matches
Mail list logo
