[U-Boot-Users] Issue with Ethernet operation in non-promiscuous mode.
upakul at gmail.com
Thu Dec 27 16:40:11 CET 2007
I have just tested this with the Ping and Dhcp commands.
Ping <serverip>: With Promiscuous mode enabled, the <serverip> is shown
alive. When promiscuous mode is disabled, the <serverip> is shown to be not
Dhcp: With Promiscuous mode enabled, the device gets an IP address . When
promiscuous mode is disabled, it keeps broadcasting the Bootp packets, but
is perhaps not able to receive the Bootp reply packets sent by the server.
The same Mac address works fine in case of Linux and Nucleus, so i think the
Mac address should not be a problem.
On Dec 27, 2007 9:00 PM, Ben Warren <bwarren at qstreams.com> wrote:
> Hi Upakul,
> Upakul Barkakaty wrote:
> > Hi all,
> > I am using an ethernet driver, working in Polling mode, ARM
> > architecture. It works fine in Promiscuous mode. However, when the
> > promiscuous mode is disabled, then the network operations are not
> > functional. Does the Uboot network stack have any limitation, or is it
> > a bug in the ethernet driver itself? Please share your inputs.
> Your description is a bit vague... I don't know what type of traffic
> you're dealing with, what commands you're using etc. Enabling
> promiscuous mode essentially bypasses any hardware MAC address matching
> that your controller does and thus lets everything in. Since that
> works, the driver is probably fine, and I suspect that you haven't
> properly configured a valid unicast MAC address.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the U-Boot