From owner-freebsd-questions Wed May 31 10: 6: 2 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 2DFF737B69E for ; Wed, 31 May 2000 10:05:59 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e4VH5un29973 for ; Wed, 31 May 2000 10:05:56 -0700 (PDT) Message-Id: <200005311705.e4VH5un29973@ptavv.es.net> To: freebsd-questions@freebsd.org Subject: Problems with dhclient on 3-Stable Date: Wed, 31 May 2000 10:05:56 -0700 From: "Kevin Oberman" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to get the dhclient to work with the DHCP server built into my SonicWALL firewall. Of course, it works fine with Windows, but on my FreeBSD boxes dhclient exits after sending out the message: "select: Invalid argument". The configuration of the network is often incomplete. I captured the packet from the SonicWALL server and see only one problem...the domain name is a null terminated string. But the RFC states that clients MUST accept null terminated ASCII strings even though server SHOULD not send them. So I'm very unsure that this is the problem. Unfortunately, the dhclient is stripped, so gdb is not very helpful. On other possible issue is that option 52 is included with a value of 3. Both the SNAME and FILE fields start with 255 which indicates the end of data. Any ideas on how to work around or fix this? It really is a pain on my laptop which moves between several nets on a regular basis. Thanks, R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message