It is rather odd.

Firstly I thought that the DHCP client was based on a
Linux one.  The same PC with the same Xircom card work
fine in Linux, though I'm sure I read somewhere that
in Linux the PC has to have an IP address (like a
private one) before it can use the DHCP learnt one).

Next, I also tried the OSI stack.  I haven't made it
talk to another OSI End System yet, but it does send
out OSI ESHs correctly.

You would think that if there was something wrong with
the driver that the OSI stack would be pretty unlikely
to work.

It sounds like someone has broken a layering rule in
the DHCP client code or in the Xircom driver.

Thanks, Philip

> 
> In
>
http://mail-index.netbsd.org/netbsd-help/2002/07/19/0001.html
> I talked about a Xircom carbus card that would not
> configure with
> dhcp. After the referenced article was posted, I set
> up a series
> of dhcp configurations that work with any other nic,
> but none of
> them worked with the Xircom cardbus card. Never
> solved the problem.
> The laptop is no longer available to test with.
> 
> >> I am running NetBSD 1.6 i386 on a laptop
> >> it has a Xircom creditcard 10/100 + 56k
> >> 
> >> When the machine boots it detects the card as a
> xircom
> >> realport which isn't quite right (I thought that
> >> realport was a different product to the
> creditcard),
> >> however I don't think that this is the problem as
> I
> >> can manually ifconfig an IP address into the PC
> and
> >> get the IP stack working that way. 

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com