On Sun, Jul 28, 2013 at 05:31:07PM -0430, Juan Barriteau wrote: > Thanks a lot for your response Ken, you gave me enough information to > search in the correct direction, and after reading a bit about basic > networking I know that definitely there is no bug to report in here, > the added feature for checking overlapping subnets is okay, lets say > that now the OS is telling me what I've been doing wrong for a > while... > > I'm very sorry for the ignorance-based bug report, > > Juan
Not a problem! Thanks for the update. .... Ken > > On Sun, Jul 28, 2013 at 7:28 AM, Kenneth R Westerback > <kwesterb...@rogers.com> wrote: > > On Sat, Jul 27, 2013 at 11:04:20PM -0430, Juan Barriteau wrote: > >> >Synopsis: Not possible to configure more than one interface with dhclient > >> >Category: Networking > >> >Environment: > >> System : OpenBSD 5.4 > >> Details : OpenBSD 5.4 (GENERIC.MP) #42: Fri Jul 26 12:41:58 > >> MDT 2013 > >> > >> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP > >> > >> Architecture: OpenBSD.i386 > >> Machine : i386 > >> >Description: > >> Having 3 network adapters (alc0, rl0 and rl1) I want to dhcp > >> all of them, always did it with no problem during installation process > >> (from scratch) or in installed systems until 5.2, since 5.3 and with > >> current I'm not able to, doing dhclient works only for the first > >> interface: > >> > >> # dhclient alc0 > >> DHCPREQUEST on alc0 to 255.255.255.255 port 67 > >> DHCPACK from XXX.XXX.XXX.XXX9 (XX:XX:XX:XX:XX:XX) > >> bound to XXX.XXX.XXX.XXX -- renewal in 14400 seconds. > >> > >> But for the second and third adapters it fails: > >> > >> # dhclient rl0 > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 3 > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 6 > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 15 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 16 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 11 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl0 to 255.255.255.255 port 67 interval 10 > >> interface alc0 already has the offered subnet! > >> No acceptable DHCPOFFERS received. > >> No working leases in persistent database - sleeping. > >> > >> # dhclient rl1 > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 3 > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 5 > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 13 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 16 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 19 > >> interface alc0 already has the offered subnet! > >> DHCPDISCOVER on rl1 to 255.255.255.255 port 67 interval 5 > >> interface alc0 already has the offered subnet! > >> No acceptable DHCPOFFERS received. > >> No working leases in persistent database - sleeping. > >> > >> It happens the same no matter if I choose any other of the > >> adapters first, the first one obtains IP address, but second and third > >> fails. > >> > >> >How-To-Repeat: run dhclient after having a first adapter configured with > >> >dhclient > >> >Fix: no one found > >> > >> > >> Thanks in advance, > >> > >> Juan Barriteau > >> > > > > It would appear that dhclient does not like the ip address it gets > > for the 2nd and 3rd interfaces because the subnets overlap. Hard > > to say for sure if this is a bug in your situation since you don't > > provide sufficient information. The check for overlapping subnets > > was added recently. > > > > In particular, > > > > 1) Does the behaviour only occur during the install scripts? > > 2) What are the expected ip addresses and subnets for all the interfaces? > > > > Other useful information would be > > > > 1) The dhclient.conf file. > > 2) The /var/db/dhclient.leases.* files. > > 3) The /etc/hostname.* files. > > 3) A tcpdump of the traffic for working and non-working setups. > > > > .... Ken
