This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Sending Raw Ethernet packets (ether_output, ether_output_frame, __enet_send ?)


On Thu, Nov 20, 2003 at 10:52:46AM -0700, kevin_lemay@agilent.com wrote:
> Oops,
> 

> You Said SERVER. I quick check of the DHCP request services from my
> linux box shows that it uses standard UDP using the assigned IP
> address for the destination.

> It would appear that you could use the standard UDP socket routines
> if you could manually add the entry into the routing table. This
> would be easier to do that using a non-standard ethernet
> interface. Usually stacks have routines to add routes.

I don't see why you need to add a route entry? You are probably
assigning addresses for the subnet the server is already on. If not,
the default route will probably do the job of getting the reply to the
DHCP proxy.

The problem is with the arp entry. Since the device requesting the
address does not have an IP address, it obviously cannot have an arp
entry. Hence you cannot send a packet to it. It will also not respond
to arp requests. 

What you may be able to do is add a static arp entry, send the packet,
and then remove the static arp entry. 

    Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]