Date: 21 Feb 2001 10:12:40 -0500 From: Lowell Gilbert <lowell@world.std.com> To: freebsd-questions@freebsd.org Subject: Re: DHCP [ WAS: Problem Adding 2nd NIC] Message-ID: <443dd8nk7r.fsf@lowellg.ne.mediaone.net> In-Reply-To: richard@sparky.uk.net's message of "21 Feb 2001 10:15:25 %2B0100" References: <200102210051.f1L0pHm04406@grumpy.dyndns.org> <NDBBJAMCELCBDMINDKAAKEEJCEAA.richard@sparky.uk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
richard@sparky.uk.net (Richard Morte) writes: > ifconfig -l shows both pn0 and pn1 once only together with the usual lo0, > lp0 etc. > ifconfig -a shows pn0 with the IP Addresses set as per rc.conf, up and > running > ifconfig -a shows pn1 with no IP addresses set (because it fails at boot > time) and not up and not running. > pn0 works fine for the _internal_ network - all PC's can see each other. > > after issuing "dhclient pn1" at the command prompt, ifconfig -a now shows > the IP address provided by the DHCP server: inet 62.31.2.... etc, with > netmask correctly assigned, up and running. Just as expected. > > Now on to rc.network. I'm no shell programmer, but it's kind of followable. > This file has never been modified since installation, so my guess is that > it's correct. The only thing I don't understand is the different references > to the various enable flags : = X"YES" for example , then later = "XYES", > but the LHS seems to mirror the RHS, so I guess all is well. I cannot see > any reference to the 'Bad Value' string, so some other script must be > reporting this. It's coming directly from ifconfig, actually. The problem is that you are using a syntax: > > ifconfig_pn1="DHCP" which is not supported at all by the script on your system. Remember that you are running a system that is more than half-a-dozen releases out of date, and not all of the documentation may apply to your system any more. I don't have a 3.2 system available, but I think that putting "dhclient pn1" in /etc/rc.local should work for you, and is probably the easiest approach. Good luck. > I don't think there's a request for DHCP on pn0. I think the problem lies > elsewhere... > > Ric > > > > Richard Morte > e-mail : richard@sparky.uk.net <mailto:richard@sparky.uk.net> > phone : 0114 233 7993 > fax : 0114 220 6075 > mobile : 0779 091 8736 > > > -----Original Message----- > From: dkelly@grumpy.dyndns.org [mailto:dkelly@grumpy.dyndns.org]On > Behalf Of David Kelly > Sent: 21 February 2001 00:51 > To: Richard Morte > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: DHCP [ WAS: Problem Adding 2nd NIC] > > > "Richard Morte" writes: > > OK everyone, > > > > Resolved the problem with the NIC - just wasn't compatible, so I swapped > it > > for a spare FA310 and all is well - I now have pn0 and pn1. The FA311 has > > now gone into a windows machine! > > > > Now I have a new problem: I've added the line: > > ifconfig_pn1="DHCP" > > into rc.conf > > > > On reboot I get the message: > > ifconfig: DHCP: Bad value > > and, of course, no IP address is set for the NIC. > > > > However if I run : > > dhclient pn1 > > from the command prompt, I am provided with an IP address by the remote > host > > and I can ping the world. I'm running 3.2 - any idea what should be put in > > rc.conf to start DHCP client at each re-boot? > > First I would try "ifconfig -l" to see if it lists your NICs. > > Then I'd look into /etc/rc.network and discover when dhclient is run it > is started once only for all DHCP interfaces at the same time. Possibly > like this for you: > > dhclient pn0 pn1 > > I'd try that in my keyboard single-stepping to see where the problem is > happening. I wonder if its asking the DHCP server on pn0 for an address > to use on pn1, and is being refused. That is, if you use DHCP on both. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443dd8nk7r.fsf>