From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 26 Aug 2009 13:01:31 +0200 From: Andrew Lunn Message-ID: <20090826110131.GI20818@lunn.ch> References: <20090826064151.GE21827@ma.tech.ascom.ch> <200908261001.31814.sven.eckelmann@gmx.de> <200908261651.16980.lindner_marek@yahoo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200908261651.16980.lindner_marek@yahoo.de> Subject: [B.A.T.M.A.N.] Configuration interface... Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking > > > Should /proc/net/batman-adv/interface be replaced with an IOCTL interface > > > similar to brctl? > > > > How to design the kernel<->userspace interface that it doesn't end like > > wireless-tools? > > I'm not so familiar with the iwconfig situation you seem to refer to. Could you > outline the issues ? It is complex and horrible. It is also badly implemented by many wireless devices so is inconsistent. However, batman has a much simpler interface. There is a lot less to configure: originator interval aggregation to enable/disable vis server/client mode interfaces to use So it should be possible to implement a reasonably simple interface. I think only the interfaces is somewhat tricky and needs thinking about. The rest can be individual files in /sys. Andrew