lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 27 Aug 2014 19:06:04 +0200
From:	Martin Rusko <martin.rusko@...il.com>
To:	netdev@...r.kernel.org
Subject: Sending undersized ARP packets with VXLAN L3 interface

I tried to use VXLAN interface as an L3 interface. Something like this:

  ip link add name vxln7 \
  type vxlan id 7007 group 232.1.42.7 \
  local 10.7.12.250 dev vlan482 \
  dstport 0 ageing 300

  ip ad ad 192.168.3.200/24 brd + dev vxln7
  ip li set vxln7 up

Now this doesn't work very well for small packets like those carrying
ARP protocol. Because resulting ethernet frames which are encapsulated
in VXLAN are not padded to minimum 64bytes required for Ethernet. Once
the inner frame traverse through any switch, it will get dropped as
undersized (runt) packet.

I'm wondering, where is the proper place to fix this. Should
arp_create() function allocate skb big enough to produce ethernet
frame with at least minimum size? Or is it somewhere in NIC drivers
where small packets are padded with zeros?

Regards,
Martin
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists