netdev - Re: WAN device configuration, again...

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: <1256745788.3850.31.camel@localhost.localdomain>
Date:	Wed, 28 Oct 2009 09:03:08 -0700
From:	Dan Williams <dcbw@...hat.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	netdev@...r.kernel.org
Subject: Re: WAN device configuration, again...

On Wed, 2009-10-28 at 14:28 +0100, Krzysztof Halasa wrote:
> Hi,
> 
> I'm currently at final stages of "producing" two WAN drivers and there
> is one thing to solve: they have really complex options. It's no longer
> a V.35 with ca. 4 clock modes, a clock rate and few encodings etc. They
> need many options unique to each driver/board. I think I need a more
> capable interface to configure the devices than the current ioctl-based
> one.
> 
> I think of something:
> - using netlink or similar interface

If you're doing a new config interface, I'd suggest netlink like the
wireless guys did to replace WEXT with cfg80211.  Using netlink makes
your interface easily available from programs/libraries without having
to screenscrape anything.  If you want some advice on netlink API stuff,
ask Johannes Berg.

Dan

> - with potentially unlimited "payload" size (data may be transfered in
>   smaller packets)
> - the "command" and "response" should be variable-length ASCII-based,
>   instead of fixed structures. This way I don't have to duplicate all
>   option handling in userspace, only the specific driver has to know
>   about them.
> 
> Comments? Perhaps there is already an example?
> Should I use something else?
> 
> I also thought about using /sys read/write calls, but I'm not sure it's
> a good idea.

--
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