|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
Dear fundoos,
I am currently using vxworks 6.0. My problem is mmmm, little bit tricky.. !!! I am trying to send following packet to accesss one of the network processor oops, i forgot to mention the name it is AXEL-X fujitsu processor. The setup :: (1) X86 machine loaded with vxworks image. (2) Options enabled :: all network related support. No INCLUDE_MUX_L2 and INCLUDE_L2CONFIG are enabled. (3) AXEL_X network processor code is included into my vxworks image. (4) AXEL-x board is connected through GigaBit ethernet cable to my X86 machine. The Task - ) ::(1) I have my linux x86 OS from which I am sending a packet using sockaddr_ll structure ( link layer ) ......yahooo.. my packet is visible in ethereal. !!! Here below is the dump... /***************start packet frame *****************/ Frame 127 (60 bytes on wire, 60 bytes captured) Arrival Time: Sep 25, 2007 15:09:48.764626000 Time delta from previous packet: 10.880253000 seconds Time relative to first packet: 244.831101000 seconds Frame Number: 127 Packet Length: 60 bytes Capture Length: 60 bytes Ethernet II, Src: 00:07:e9:0b:6f:9e, Dst: 00:00:0e:ff:f0:df Destination: 00:00:0e:ff:f0:df (Fujitsu_ff:f0:df) Source: 00:07:e9:0b:6f:9e (Intel_0b:6f:9e) Type: Unknown (0x88b5) Data (46 bytes) 0000 00 00 0e ff f0 df 00 07 e9 0b 6f 9e 88 b5 00 02 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00. 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0030 00 00 00 00 00 00 00 00 00 00 00 00 /************end packet... frame.. **************/ Well the above is not a problem LINUX helps me out,, very well... If you see the above packet it doesn't have IPAddress.. !!!! coming to vxworks - ((((waaaaaaaaaaaaa(2) I would like to get the same output using vxworks stack.. i have searched.. searched.. and tired... but unable to simulate the same environment... and output.. !!!! I would like to send the following formatted.. data... --------------------------------------------------------------------------------------------------------------------------------------------------- |DA(6)| SA(6)|Proto Type(2)|msgCode(2)|msgLen(2)|Flag/status(2)| Identifier(2)|SeqNo.(2)|OptionalData(xx)| FCS(4) | ---------------------------------------------------------------------------------------------------------------------------------------------------- I am able to send the packet using IP layer ( including IP address.. )But, unable to send using ONLY MAC ADDRESS... \ Vxworks 6.x doesn't support sockaddr_ll structure and link layer packet simulation.. !!!! So, I AM CRYING AND FACING LOT OF PROBLEMS.. !!! Tried with the following sockaddr_dl, sockaddr_in e t c.. But, I am unable to strip and throw out IPADDRESS from my packet... !!! This packet will be understandable by AXEL-X Processor.. through ethernet cable.. ( GBIC )....... CAN PLEASE PLEASE SOME BODY HELP US REGARDING THIS.. thanks in advance for your help.. what we feel, is there must be some configuration which is missing so that i can send packets using mac address also.. !!! CHEERS AND WAITING - )))With love skywalker. !!! siva.ieee@gmail.com |
|
#2
|
|||
|
|||
|
(E-Mail Removed) wrote:
> Dear fundoos, > > I am currently using vxworks 6.0. My problem is mmmm, little bit > tricky.. !!! I am trying to send following packet to accesss one of > the network processor oops, i forgot to mention the name it is AXEL-X > fujitsu processor. > > The setup :: > > (1) X86 machine loaded with vxworks image. > (2) Options enabled :: all network related support. No > INCLUDE_MUX_L2 and INCLUDE_L2CONFIG are enabled. > (3) AXEL_X network processor code is included into my vxworks image. > (4) AXEL-x board is connected through GigaBit ethernet cable to my X86 > machine. > > The Task - ) ::> > (1) I have my linux x86 OS from which I am sending a packet using > sockaddr_ll structure ( link layer ) ......yahooo.. my packet is > visible in ethereal. !!! Here below is the dump... > > /***************start packet frame *****************/ > Frame 127 (60 bytes on wire, 60 bytes captured) > Arrival Time: Sep 25, 2007 15:09:48.764626000 > Time delta from previous packet: 10.880253000 seconds > Time relative to first packet: 244.831101000 seconds > Frame Number: 127 > Packet Length: 60 bytes > Capture Length: 60 bytes > Ethernet II, Src: 00:07:e9:0b:6f:9e, Dst: 00:00:0e:ff:f0:df > Destination: 00:00:0e:ff:f0:df (Fujitsu_ff:f0:df) > Source: 00:07:e9:0b:6f:9e (Intel_0b:6f:9e) > Type: Unknown (0x88b5) > Data (46 bytes) > > 0000 00 00 0e ff f0 df 00 07 e9 0b 6f 9e 88 b5 00 02 > 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00. > 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0030 00 00 00 00 00 00 00 00 00 00 00 00 > > /************end packet... frame.. **************/ > > Well the above is not a problem LINUX helps me out,, very well... > If you see the above packet it doesn't have IPAddress.. !!!! Well, it is not an IP packet. It is a vendor-specific protocol packet! The authority on ethernet types is: <http://standards.ieee.org/regauth/ethertype/eth.txt> Robert > > [snip] |
![]() |
| Tags |
| layer, linux, packets, protocol, sending |
| Thread Tools | |
| Display Modes | |
|
|