cap). Attaching to the lagg0 with
tcpdump, filters out the freebsd’s LACP packets, but still sees the TP-Link’s
packets.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
lacp.pcap
Description: Binary data
lacp-lagg0.pcap
Description: Binary data
signature.as
someone would have some insight before I start looking at each bit
of the packets what’s not aligned.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
signature.asc
Description: Message signed with OpenPGP using GPGMail
s from 192.168.0.2: icmp_seq=195 ttl=64 time=1.031 ms
64 bytes from 192.168.0.2: icmp_seq=241 ttl=64 time=0.993 ms
64 bytes from 192.168.0.2: icmp_seq=242 ttl=64 time=1.095 ms
64 bytes from 192.168.0.2: icmp_seq=243 ttl=64 time=1.482 ms
Feels like some there is
74L Gigabit Network Connection'
class = network
subclass = ethernet
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
signature.asc
Description: Message signed with OpenPGP using GPGMail
Thanks ryan - this did appear work around the issue.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
On Dec 10, 2014, at 10:25 AM, Ryan Stone wrote:
> From a quick look at the code, whenever an interface is added to a
> bridge, if that interface does not sup
ary/wire format … if someone can point me to the reference for that, that
would be helpful (at least my own understanding).
Not exactly sure what these extra 4 bytes are at the end of the packet. Still
trying to figure that out.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidD
On Dec 15, 2014, at 11:33 AM, Alan Somers wrote:
> On Sun, Dec 14, 2014 at 6:23 PM, David P. Discher wrote:
>>
>> So, I think I’ve identified the issue. In sys/net/ieee8023ad_lacp.c,
>> lacp_pdu_input() has a sanity check :
>>
>>
et would work
well, even back-to-back, but even used this looks to be a bit pricey for
home/hobby setup. I’m now looking towards Infiniband, as the cards and parts
on the use market are a great value (but this is the wrong list for talking
about that.)
Thanks !
-
David P. Discher
http://da
different vendors switches with LACP and see what I can find out.
-
David P. Discher
http://davidpdischer.com/
AIM: DavidDPD | Y!M: daviddpdz
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe
I’m going to look into other switches/routers and read the spec a bit closer,
but linux seems to think the LACPDU check is packet size => sizeof(struct
lacpdu) :
-
https://github.com/torvalds/linux/blob/70e71ca0af244f48a5dcf56dc435243792e3a495/drivers/net/bonding/bond_3ad.c#L2185
-
Davi
.
So, does IPSec use AESNI ? I would have at least expected 600-700 Mbps.
--
David P. Discher
https://davidpdischer.com/
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
> On Aug 8, 2018, at 10:37 PM, Andrey V. Elsukov wrote:
>
> On 09.08.2018 06:57, David P. Discher wrote:
>> I’m suspecting that IPSec in FreeBSD is not leveraging AESNI on Intel. Is
>> this correct ?
>
> IPsec uses crypto(9) framework that works by default with
ec4
refcnt=1
::/0[any] ::/0[any] any
out ipsec
esp/tunnel/10.245.0.201-10.245.0.203/unique:4
spid=16 seq=0 pid=2443 scope=ifnet ifname=ipsec4
refcnt=1
--
David P. Discher
https://davidpdischer.com/
408.368.3725 • d...@dpdtech.com
gb1: on cxgbc0
cxgb1: Using defaults for TSO: 65518/35/2048
cxgb1: bpf attached
cxgb1: Ethernet address: 00:07:43:0a:a0:85
cxgbc0: Firmware Version 7.11.0
-
David P. Discher
http://davidpdischer.com/
signature.asc
Description: Message signed with OpenPGP using GPGMail
14 matches
Mail list logo