From: Mike Kershaw <[EMAIL PROTECTED]>
Date: Wed, 24 Aug 2005 09:39:00 -0400
> > Do you need to do some range validation on arg before setting
> > tun->dev->type?
>
> I shouldn't think so, the worst you could do is set it to a link type
> nothing understands, and then they just either go to cook
> Do you need to do some range validation on arg before setting tun->dev->type?
I shouldn't think so, the worst you could do is set it to a link type
nothing understands, and then they just either go to cooked socket
(pcap) or confuse the app (anything that looks at type directly) or
nothing (anyt
On Tue, Aug 23, 2005 at 05:28:00PM -0400, Mike Kershaw wrote:
> Very small patch to allow setting of the link type of the virtual tapX
> interfaces in tun/tap. Needed for writing packets of other arp link
> types to tap, ie 80211 wireless frames.
>
> Implemented as a simple IOCTL to set the arpty
From: Mike Kershaw <[EMAIL PROTECTED]>
Subject: [Patch] Set link type on tun/tap virtual interface
Date: Tue, 23 Aug 2005 17:28:00 -0400
> Very small patch to allow setting of the link type of the virtual tapX
> interfaces in tun/tap. Needed for writing packets of other arp link
&g
Very small patch to allow setting of the link type of the virtual tapX
interfaces in tun/tap. Needed for writing packets of other arp link
types to tap, ie 80211 wireless frames.
Implemented as a simple IOCTL to set the arptype.
-m
--
Mike Kershaw/Dragorn <[EMAIL PROTECTED]>
GPG Fingerprint: 3
