This patch removes the (ugly and racy) packet receiving thread and the
kernel socket usage. Instead, packets are received directly by registering
the ethernet type and handling skbs instead of self-allocated buffers.
Some consequences and comments:
* we don't copy the payload data when
Simon Wunderlich wrote:
+/* receive a packet with the batman ethertype coming on a hard
+ * interface */
+int batman_skb_recv(struct sk_buff *skb, struct net_device *dev,
+ struct packet_type *ptype, struct net_device *orig_dev)
+{
+ struct batman_packet *batman_packet;
+ struct
I tried to start batmand with
batmand wlan0
got back and error stating
which iptables /dev/null returned an error
Does anyone know what is the cause and/or solution to this problem?
Thanks
Eric
Conner, Eric wrote:
Does anyone know what is the cause and/or solution to this problem?
Either iptables is not installed, iptables not installed in a path which is is
part of $PATH, batmand is not started as root or which is not installed/not a
builtin function of the shell.
Best regards,
On Wed, Dec 23, 2009 at 09:34:17AM -0800, Gus Wirth wrote:
On 12/23/2009 02:20 AM, Sven Eckelmann wrote:
[snip]
This is explained in Understanding Linux Network Internals, Christian
Benvenuti, December 2005, O'Reilly, 2.1.5.5. Cloning and copying
buffers
Where did the 2.1.5.5 come