I say with 99% certainty that assigning 0.0.0.0 to
the interface is a requirement of dhcp.
You can't stop using it and expect dhcp to work.
In message <[EMAIL PROTECTED]>, "Alexander N. Kabaev" writes:
>FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT
>in order to brin
No...
In message <[EMAIL PROTECTED]>, Mathew Kanner writes:
>On Apr 07, Donn Miller wrote:
>> Since I started using a cable modem and dhclient, my system has been
>> literally overwhelmed with messages like:
>>
>> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
>>
>
> I ha
I have seen that situation before as well
and there may be more slight tolerance-style improvements
that could be made but I can't think of any at the moment.
In message <[EMAIL PROTECTED]>, Donn Miller writes:
>This is a multi-part message in MIME format.
>--ABD696746D33D54680111FE2
The 3940U2W has two pci devices. One for each scsi interface.
Each interface uses a separate pci interrupt.
One uses INTA the other probably uses INTB and which irq
they uses depends on your motherboard.
In message , Brad Knowles writes:
>At 9:53 AM -0800 20
To David Greenman or.. whoever is maintaining if_fxp.c
I picked up an 82559 card from compusa today...
Guess what?! It's device id was 0x1030 instead of 0x1229.
I adjusted my driver to match and it seems to work fine.
Of course, I haven't tried it yet with FreeBSD.
(I was using vxWorks.)
To Un
Is it possible to load kernel modules that are supposed
to operate on pci devices?
... Does pci_rescan() need to be finished ?
What am I missing here?
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message