From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27811 invoked by alias); 20 Nov 2003 18:44:43 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 27804 invoked from network); 20 Nov 2003 18:44:42 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sources.redhat.com with SMTP; 20 Nov 2003 18:44:42 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1AMtnB-0003QG-00; Thu, 20 Nov 2003 19:44:37 +0100 Date: Thu, 20 Nov 2003 18:44:00 -0000 To: kevin_lemay@agilent.com Cc: sebastien.couret@elios-informatique.fr, ecos-discuss@sources.redhat.com Message-ID: <20031120184437.GB2130@lunn.ch> Mail-Followup-To: kevin_lemay@agilent.com, sebastien.couret@elios-informatique.fr, ecos-discuss@sources.redhat.com References: <1BEBA5E8600DD4119A50009027AF54A010FAE47B@axcs04.cos.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1BEBA5E8600DD4119A50009027AF54A010FAE47B@axcs04.cos.agilent.com> User-Agent: Mutt/1.5.4i From: Andrew Lunn Subject: Re: [ECOS] Sending Raw Ethernet packets (ether_output, ether_output_frame, __enet_send ?) X-SW-Source: 2003-11/txt/msg00281.txt.bz2 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