[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dhcp prob on 2 nics during installation
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: dhcp prob on 2 nics during installation
- From: Kenneth R Westerback <kwesterback_(_at_)_rogers_(_dot_)_com>
- Date: Fri, 28 Jun 2002 19:54:25 -0400
I will assume that when you try to configure the 2nd interface you
see an error message like:
Can't find free bpf: No such file or directory
Because the ramdisk kernels are configured by default with only a
single bpf device, and each running dhclient 'consumes' one bpf
device, and configuring an interface with dhcp leaves a dhclient
process running, well you can do the math. :-).
You can probably get around the problem by exiting to a shell with
'!', and killing the running dhclient (see /var/run/dhclient.pid since
ps may not be available). Now the 2nd interface can probably be
configured with dhcp.
Alternatively you can change RAMDISKxx to have more bpf devices and
generate a new boot image for your system.
The GENERIC kernel has 8 bpf devices so it will work up to that many
concurrent dhclient processes.
The problem you are probably encountering is that there is only one
bpf device configured in the ramdisk kernels. dhclient uses one per
invocation (and currently each invocation of dhclient sticks around
indefinately), and so the 2nd and subsequent invocations of dhclient
during the install process will fail.
You could forcibly
On Fri, Jun 28, 2002 at 01:19:41AM -0500, Taylor Geraldson wrote:
> i am doing an install on my IBM ThinkPad 560X where i have two pcmcia
> network cards, a 3com 56k/10Mb LAN NIC(3CXEM556B) and a SMC2632W
> wireless nic. I have begun installs with the latest snapshot and
> regular 3.1, both of them recognize both cards fine, and both setup the
> first card fine as well. The problem arises when i try to configure the
> second card for dhcp in the install, it will not work. I have tried
> different times doing one card first then the other, the first card
> always works, the second one always doesn't(with dhcp, if i manually
> specify the 2nd its fine). While i probably will be able to configure
> them both for dhcp once i have completed the install without too much of
> a problem i just wanted to note this, seemingly, odd behaviour. Maybe
> its a bug, maybe its intended, i couldn't find anything about it on
Visit your host, monkey.org