Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 May 2015 21:14:07 -0700
From:      Jeffry Killen <jekillen@prodigy.net>
To:        Doug Hardie <bc979@lafn.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: configuration script?
Message-ID:  <223D6233-6743-4B7F-8451-52950EB4DD78@prodigy.net>
In-Reply-To: <9C3B386F-9D42-4B26-8264-C9B9D73B7296@lafn.org>
References:  <B35DDDCD-1255-423E-AF54-95FEF589B31E@prodigy.net> <9C3B386F-9D42-4B26-8264-C9B9D73B7296@lafn.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

On May 15, 2015, at 7:43 PM, Doug Hardie wrote:

>
>> On 15 May 2015, at 18:47, Jeffry Killen <jekillen@prodigy.net> wrote:
>>
>> In the past when I installed from cds ordered from FreeBSD mall, =20
>> there
>> was a lot of software I could add after the installation process was
>> concluded. I did not see that here. Is that what the "Live Cd" is =20
>> all about.
>> (I have been browsing the  handbook and haven't found anything
>> revealing in this respect)
>
> I normally reboot the system and get it running on the newly =20
> installed system and then add ports.
>
>> When there are two or more network interfaces that have names
>> like en0, en1... etc. How do I tell which physical port is used by =20=

>> which
>> network device? When there are only two, it is easy to switch back =20=

>> and
>> fourth and look at ifconfig output, and do pinging for hosts on the
>> same networks. In this case at least one will be used for internet =20=

>> connectivity
>> via DHCP to dsl/modem, and another will be connected with manual =20
>> address
>> to local network. If I have a cable plugged into the wrong socket, =20=

>> things can
>> get confusing for me and the system.
>
> The easy way to identify the ports is to use a switch and connect =20
> one cable from the switch to one port.  Then run =93ifconfig=94 and =
see =20
> which port is =93UP=94.  Then label the jack.  Move on to the next and =
=20
> so forth.
>
>>
>> This machine came with two built in networking interfaces & sockets =20=

>> (RJ45)
>> that were not supported by FreeBSD at the time. So I got two more =20
>> interface
>> cards that did have driver support. That makes a total of four on =20
>> this machine.
>> Is there a standard pattern for matching the physical port to the =20
>> device name?
>
>
> The same procedure above should resolve this also.
>

Thanks for advice, info, etc
JK




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?223D6233-6743-4B7F-8451-52950EB4DD78>