Messages in this thread | | | Date | Tue, 3 Jun 2003 15:06:42 +0530 (IST) | From | Madhavi <> | Subject | problem with VLAN tagged ICMP |
| |
Hi
I am writing a device driver that can send VLAN Tagged packets on linux-2.4.19. I have written a function mydev_hard_header() and assigned dev->hard_header to mydev_hard_header.
The function mydev_hard_header() creates ethernet header + VLAN header, if the packet is not already tagged.
When I tried ping on this device, I am seeing that the first 6-7 packets are tagged and later, they are all going untagged. mydev_hard_header() function is also not being called for these packets. I have also confirmed that the control is not going to mydev_rebuild_hard_header() function.
ARP packets are always getting tagged. This problem is seen only with ICMP.
Any guesses why this could be happening? Could there be any cache-related issues?
Thanks & regards Madhavi.
Madhavi Suram Software Engineer Customer Delivery / Networks Sasken Communication Technologies Limited 139/25, Ring Road, Domlur Bangalore - 560071 India Email: madhavis@sasken.com Tel: + 91 80 5355501 Extn: 8062 Fax: + 91 80 5351133 URL: www.sasken.com
************************************************************************
SASKEN BUSINESS DISCLAIMER
This message may contain confidential, proprietary or legally Privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly, use, Disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.
***********************************************************************
| |