Date: Thu, 18 Aug 2016 01:05:13 +0200 From: Polytropon <freebsd@edvax.de> To: Doug Hardie <doug@sermon-archive.info> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Non working NIC Message-ID: <20160818010513.0c95f8df.freebsd@edvax.de> In-Reply-To: <6A68E1F3-95CC-42AE-94B4-02B153E4E83F@mail.sermon-archive.info> References: <224DCDD3-162F-4E67-8C1D-9332C85FC032@mail.sermon-archive.info> <C5192B10-AD4E-4966-88EA-486AE1DA9116@mail.sermon-archive.info> <6A68E1F3-95CC-42AE-94B4-02B153E4E83F@mail.sermon-archive.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Aug 2016 15:56:15 -0700, Doug Hardie wrote: > Added a new NIC (rl0). Removed any reference to msk0 in rc.conf. > Set rl0 for DHCP. Same result, but some additional messages: > > Starting Network: mske0 > Starting Network: rl0 > rl0: link state changed to up > Starting Network: lo0 > Starting dhclient > rl0: not found > exiting > > I am out of ideas here. How can I figure out what is going on and correct it? This almost looks like a problem with the contents of rc.conf. Can you show all the relevant lines? Can you manually run "dhclient rl0" at any stage? What does "ifconfig -a" show? It would be strange for the device to disappear between the message "rl0: link state changed to up" and the dhclient call... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160818010513.0c95f8df.freebsd>