ok cool, cool. Wondering how the Intel NIC is defined. What's the
/etc/sysconfig/network-scripts entry for it? Go on and send over in the
/etc/sysconfig/network-scripts/enp2s0 too.

Do you have the mac address for the Intel NIC handy?

On Sun, Nov 1, 2015 at 11:04 AM, Howard White <[email protected]> wrote:

> Many thanks for the response, Wesley.  I know I am missing a trivial
> detail.
>
> From the beginning, here are the relevant items from lspci:
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)  # this
> interface is currently working, configured DHCP, ultimately static, local
> network
>
> 05:00.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
> 100 (rev 02)  # this interface is currently not responding, ultimately
> configured DHCP to whatever external network.  Jiggery Pokery required to
> use as gateway to "the big bad world."
>
> [root@localhost ~]# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP qlen 1000
>     link/ether e0:cb:4e:1f:35:b2 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.222.152/24 brd 192.168.222.255 scope global dynamic
> enp2s0
>        valid_lft 5848sec preferred_lft 5848sec
>     inet6 fe80::e2cb:4eff:fe1f:35b2/64 scope link
>        valid_lft forever preferred_lft forever
>
> [root@localhost ~]# nmcli -p d
> =================================================
>                 Status of devices
> =================================================
> DEVICE  TYPE      STATE      CONNECTION
> -------------------------------------------------
> enp2s0  ethernet  connected  Wired connection 1
> lo      loopback  unmanaged  --
>
> [root@localhost ~]# nmcli -p g
> =============================================================
>                     NetworkManager status
> =============================================================
> STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN
> -------------------------------------------------------------
> connected  full          enabled  enabled  enabled  enabled
>
>
> No talkey to second NIC.  Have tried more than one, thought to be good
> NICs.
>
> Howard
>
> On 11/01/2015 10:56 AM, Wesley Duffee-Braun wrote:
>
>> Oh and 'nmcli -p g'
>>
>> On Sun, Nov 1, 2015 at 10:55 AM, Wesley Duffee-Braun <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Good morning ;)
>>
>>     When you say "address two NICs"  do you mean assign static IP,
>>     gateway, routes, etc to each NIC? What are your outputs for 'ip a'
>>       and 'nmcli -p d' ?
>>
>>     On Sun, Nov 1, 2015 at 10:49 AM, Howard White <[email protected]
>>     <mailto:[email protected]>> wrote:
>>
>>         Okay, I admit to being lazy.  I am on the course of creating
>>         some tools for phreakNIC next weekend.  Like a fool, I have
>>         chosen to use CentOS 7 as one platform in part as
>>         self-education.  I am having to learn more than I wish to just
>>         to accomplish simple things.
>>
>>         Ergo - add a second NIC to CentOS 7 minimal.  Server is going to
>>         provide an Installfest private network with a firewall to the
>>         (gasp) phreakNIC environment.  Need two NICs.  Have two NICs.
>>         lspci sees two NICs.  May I address two NICs with nmcli, nmtui
>>         or ifconfig (yes, I added the net-tools package)???   Nooooooooo.
>>
>>         Is my google-foo good enough to find an example?  By my
>>         research, people only run CentOS 7 in VMware or VirtualBox.
>> Really?
>>
>>         What gives?
>>
>>         Howard
>>
>
> --
> --
> You received this message because you are subscribed to the Google Groups
> "NLUG" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nlug-talk?hl=en
>
> --- You received this message because you are subscribed to the Google
> Groups "NLUG" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
http://www.wesleyduffeebraun.com
<http://www.ashevillephotobooth.com>

-- 
-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to