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>] [day] [month] [year] [list]
Message-ID: <001701c9045f$79f51980$d00414ac@quest.dynamicquest.com>
Date:	Fri, 22 Aug 2008 10:00:47 -0400
From:	"Jarrad Waterloo" <jwaterloo@...amicquest.com>
To:	<netdev@...r.kernel.org>
Subject: Adding Packet to Network Queue

How do I add a packet to the network queue preferably if I am not a network
driver? I have found the function netif_rx but I am unsure if that is the
function I should be calling. Further I don't know sk_buff how to properly
initialize the sk_buff structure that has dozens of parameters. Following is
my code that throws a Segmentation fault whenever netif_rx. The variable
test1 is my packet. It does not have a frame header since it isn't coming
from a device. The first 20 bytes is the IP part of the packet. The next 8
bytes is for UDP and the last byte confirms to the DAYTIME protocol.

	printk(KERN_ALERT "device_write\n");
	printk(KERN_ALERT "%s:%d\n", __FUNCTION__, __LINE__);
	char test1[] = {0x45, 0x00, 0x00, 0x1d, 0x00, 0x00, 0x40, 0x00,
0x40, 0x11, 0x3c, 0xce, 0x7f, 0x00, 0x00, 0x01, 0x7f, 0x00, 0x00, 0x01,
0xcd, 0x54, 0x00, 0x0d, 0x00, 0x09, 0xfe, 0x1c, 0x00};
//	char test1b[] = {0x00, 0x00, 0x03, 0x04, 0x00, 0x06, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x00, 0x45, 0x00, 0x00, 0x1d,
0x00, 0x00, 0x40, 0x00, 0x40, 0x11, 0x3c, 0xce, 0x7f, 0x00, 0x00, 0x01,
0x7f, 0x00, 0x00, 0x01, 0xcd, 0x54, 0x00, 0x0d, 0x00, 0x09, 0xfe, 0x1c,
0x00};
	char test2[] = {0x45, 0x00, 0x00, 0x35, 0x00, 0x00, 0x40, 0x00,
0x40, 0x11, 0x3c, 0xb6, 0x7f, 0x00, 0x00, 0x01, 0x7f, 0x00, 0x00, 0x01,
0x00, 0x0d, 0xcd, 0x54, 0x00, 0x21, 0xfe, 0x34, 0x54, 0x75, 0x65, 0x20,
0x41, 0x75, 0x67, 0x20, 0x31, 0x39, 0x20, 0x31, 0x31, 0x3a, 0x32, 0x35,
0x3a, 0x30, 0x36, 0x20, 0x32, 0x30, 0x30, 0x38, 0x0a};
//	char test2b[] = {0x00, 0x00, 0x03, 0x04, 0x00, 0x06, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x00, 0x45, 0x00, 0x00, 0x35,
0x00, 0x00, 0x40, 0x00, 0x40, 0x11, 0x3c, 0xb6, 0x7f, 0x00, 0x00, 0x01,
0x7f, 0x00, 0x00, 0x01, 0x00, 0x0d, 0xcd, 0x54, 0x00, 0x21, 0xfe, 0x34,
0x54, 0x75, 0x65, 0x20, 0x41, 0x75, 0x67, 0x20, 0x31, 0x39, 0x20, 0x31,
0x31, 0x3a, 0x32, 0x35, 0x3a, 0x30, 0x36, 0x20, 0x32, 0x30, 0x30, 0x38,
0x0a};
	len = sizeof(test1);
	printk(KERN_ALERT "%s:%d\n", __FUNCTION__, __LINE__);
	struct sk_buff *skb = dev_alloc_skb(len);// + NET_IP_ALIGN
	unsigned char* data = NULL;
	int intret = 0;
	if(skb == NULL)
	{
		printk(KERN_ALERT "dev_alloc_skb: Could not allocate skb of
%d bytes.\n", len);
		return -ENOMEM;//EFAULT;
	}
	printk(KERN_ALERT "%s:%d\n", __FUNCTION__, __LINE__);
	data = skb_put(skb, len);
	if(data == NULL)
	{
		dev_kfree_skb(skb);
		printk(KERN_ALERT "skb_put: Could not extend user data area
by an additional %d bytes.\n", len);
		return -ENOMEM;//EFAULT;
	}
	//if(copy_from_user(data, buff, len))
	//{
	//	dev_kfree_skb(skb);
	//	return -EFAULT;
	//}
	printk(KERN_ALERT "%s:%d\n", __FUNCTION__, __LINE__);
	memcpy(data, test1, len);
	skb->protocol = htons(ETH_P_IP);
	printk(KERN_ALERT "%s:%d\n", __FUNCTION__, __LINE__);
	intret = netif_rx(skb);// Segmentation fault
	switch(intret)
	{
	case NET_RX_SUCCESS:
		printk(KERN_ALERT "no congestion\n");
		break;
	case NET_RX_CN_LOW:
		printk(KERN_ALERT "low congestion\n");
		break;
	case NET_RX_CN_MOD:
		printk(KERN_ALERT "moderate congestion\n");
		break;
	case NET_RX_CN_HIGH:
		printk(KERN_ALERT "high congestion\n");
		break;
	case NET_RX_DROP:
		printk(KERN_ALERT "packet was dropped\n");
		break;
	default:
		printk(KERN_ALERT "Unknown netif_rx return value\n");
		break;
	}
	return len;

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ