Hello Olivier,
Thanks for you hard work.
I'm testing your BSDRP release 1.70, and espacially netmap-fwd with Robert
Zollner patch.
Is there an issue with this fork ?
Indeed, I have a simple lab
Generator(ix0) <> (ix0)DUT(ix1) <> Receiver (ix1).
Generator and Receiver is the same server.
My pkt-gen rules are:
pkt-gen -f tx -i ix0 -l 60 -d 198.19.0.1:2000-198.22.0.99:4000 -U -D
90:e2:ba:83:66:60 -s 172.16.51.1:2000-172.16.51.100
pkt-gen -f rx -i ix1 -d 198.19.0.1:2000-198.22.0.99:4000
My DUT have a default route to Receiver (ix1).
When I keep kernel routing, I have "normal" performances on my Intel(R)
Xeon(R) CPU E5606 @ 2.13GHz => reach 2.4 Mpps.
Unfortunately, when i lauch netmap-fwd, I have some errors, and forwarding
does not work anymore. I seem to have ARP resolution issue.
Here tcpdump on Receiver (ix1).
[root@pktgen]~# tcpdump -ni netmap:ix1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on netmap:ix1, link-type EN10MB (Ethernet), capture size 262144
bytes
20:39:40.126157 ARP, Request who-has 192.168.45.1 tell 192.168.45.10,
length 46
20:39:40.972682 ARP, Request who-has 192.168.45.1 tell 192.168.45.10,
length 46
20:39:41.972839 ARP, Request who-has 192.168.45.1 tell 192.168.45.10,
length 46
The most disturbing is 192.168.45.1 configured as a static arp entry on my
(kernel) table:
? (192.168.45.1) at 90:e2:ba:83:3d:29 on ix1 permanent [ethernet]
Do you have an idea why arp resolution is KO on netmap and Ok on kernel
mode ?
I don't have test netmap-fwd Netgate release, only the BSDRP one....
Regards,
__
Jean-Bapriste,
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bsdrp-users mailing list
Bsdrp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bsdrp-users
