Re: bootme problem

From: Marco Contenti <marco.contenti@xxxxxxxxxx>
Date: Fri, 27 Oct 2006 10:45:20 +0200

ali88z@xxxxxxxxx ha scritto:

I build a bootloader, it can send bootme well and the PB5.0 can
reply to it too. But here is a stange problem, bootloader can accept
destination 59.77.17.255 UDP packet but can't accept destination
59.77.17.100

Addresses ending with .255 are multicast, so they will be received by all adapters in the subnet. I suspect a MAC address conflict because directed packets, instead, must match exactly the MAC address.
If in doubt, try using a network analyzer.

--

Marco Contenti
PROJECT s.a.s. (MSWEP)
www.projectsas.it
marco.contenti@<see domain above>
.

Follow-Ups:
- Re: bootme problem
  - From: ali88z@xxxxxxxxx

References:
- bootme problem
  - From: ali88z@xxxxxxxxx

Prev by Date: Re: Hive Based Registry Problem
Next by Date: AT91SAM9261-EK CETK Results set for this BSP
Previous by thread: Re: bootme problem
Next by thread: Re: bootme problem
Index(es):
- Date
- Thread

Relevant Pages

Re: Problem with etherchannel between 2 3550 FXs
... :I have a 3550's in different buildings with ~2km of multimode fiber between ... and destination MAC addresses. ... of the final bits of each of the source and destination ... You get to choose which logical operation you want, ...
(comp.dcom.sys.cisco)
Re: Problem with etherchannel between 2 3550 FXs
... > and destination MAC addresses. ... > of the final bits of each of the source and destination ... > You get to choose which logical operation you want, ... > provided you aren't fragmenting packets; ...
(comp.dcom.sys.cisco)
Re: ARP requests on my net?
... But my machine is not configured to be a router, bridge, or gateway. ... But why would it need the MAC for the router? ... my machine is the destination IP. ... only for passing along to another device closer to the destination ...
(Fedora)
Re: Ip forwarding
... Packets that are meant to be forwarded by a router must be sent to its MAC address on the link. ... The gateway column optionnally contains the address of the next hop router if the destination is not directly reachable on the network attached to the output interface. ... In both cases the packet is sent on the link to the next hop MAC address. ...
(comp.os.linux.networking)
Re: Hey Jim! Need to find an article on "isaserver.org" but can find it
... It was the MAC address that became the problem, ... source MAC and the destination MAC were identical in the packet header ... rather than just going directly to the resource as they should have done. ... listed in both the Source and Destination field of the Layer2 Header ...
(microsoft.public.isa)