netdev - Re: [PATCH 00/39] merge request for WiMAX kernel stack and i2400m driver v2

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87k5ap2xw6.fsf@basil.nowhere.org>
Date:	Thu, 27 Nov 2008 12:47:53 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Johannes Berg <johannes@...solutions.net>,
	Inaky Perez-Gonzalez <inaky@...ux.intel.com>,
	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 00/39] merge request for WiMAX kernel stack and i2400m driver v2

Marcel Holtmann <marcel@...tmann.org> writes:
>
> Either we do Ethernet framing or a pure IP device. I am for the pure
> IP device with a separate ARP header (which we managed to get
> allocated). Wrapping everything into Ethernet only because dhclient is
> broken is not an answer. An alternate option would be a point-to-point

It's not only dhclient, but also lots of other raw packet users like
tcpdump etc.

> device like the HSO driver or PPP is using. However then the usage of
> DHCP becomes a lot more trickier.

I personally think user convenience is more important at least short term.
It's also not that the pseudo header is that much overhead.

-Andi
-- 
ak@...ux.intel.com
--
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