Hey guys, First post here. I'm a Network Admin/Network Security student and have decided to use ClearOs in my home network as my final Linux project and to get more hands on experience with IPS, Firewall, etc. I have the OS installed and I purchased a couple of network cards in order to connect the box to my modem and then connect my AP to the ClearOS box. While setting things up I was planning to just plug the box into my current network for initial configuration but I can't seem to get an IP address. I'm not sure if this is a NIC driver issue or if I'm just missing something rather simple. I have searched the forums and have some basic output:
ifconfig -a
enp1s7: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether d8:eb:97:69:49:75 txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
lspci -k | grep Eth -A 3
01:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Kernel driver in use: r8169
The NIC light is on and green. I tested the ethernet cable on my laptop to make sure it had connection. (this cable is coming from my home wireless router)
Any idea?
Thank you!
Shane
ifconfig -a
enp1s7: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether d8:eb:97:69:49:75 txqueuelen 1000 (Ethernet)
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
lspci -k | grep Eth -A 3
01:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
Kernel driver in use: r8169
The NIC light is on and green. I tested the ethernet cable on my laptop to make sure it had connection. (this cable is coming from my home wireless router)
Any idea?
Thank you!
Shane
In IP Settings
Share this post:
Responses (7)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
You should not need to create the ifcfg files, ClearOS should so it for you (and they'd be ifcfg-enp1s6 etc). You should be able to see the configuration options on the console. Note when I installed a few months ago, if the NIC's were in the server but not connected the console hung which was a PITA to diagnose. It also meant I could not proceed to configure them. Easiest is to start with a single NIC in standalone mode and set to receive an IP by DHCP.
You can check for a driver issue by doing an "lspci -k | grep Eth -A 3" where you should see the Driver in use is r8169. -
Accepted Answer
Thank you both for the quick replies!
My intention of only installing 1 NIC at a time was so that I could make sure that they work in this system since the package said Windows only.
The NIC's are Trendnet Gigabit PCI TEG-PCITXR
My initial configuration was a standalone behind my current router just to get things set up. I intend to connect directly to my modem.
I did not configure the NIC at all, I'm looking for documentation on how to do this now. If you could point me in the right direction I'd be grateful.
I noticed that there is not an ifcfg-eth0 file inside /etc/sysconfig/network-scripts. There is only the ifcfg-lo. Maybe I need to create those two files? ifcfg-eth0 & ifcfg-eth1?
Since it doesn't seem to be a driver issue I went ahead and installed the second NIC. I'm assuming I need to configure one of the NICS for DHCP from my ISP.
now when i type ifconfig -a i get
enp1s6: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether d8:eb:97:69:48:f6 txqueuelen 1000 (Ethernet)
enp1s7: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether d8:eb:97:69:49:75 txqueuelen 1000 (Ethernet)
next I brought up enp1s6 with the "ip link set enp1s6 up" command (that is the NIC connected to my router for the moment)
ifconfig -a
enp1s6: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet6 fe80::daeb:97ff:fe69:48f6 prefixlen 64 scopeid 0x20<link>
ether d8:eb:97:69:48:f6 txqueuelen 1000 (Ethernet)
So I'm now getting a link-local address. I'm still not sure how to go about configuring the interface and possibly assigning the interfaces to eth0 & eth1.
Thank you! -
Accepted Answer
Nick is correct. It looks like your computer isn't recognizing the additional nic. A link light simply tells you if there is power coming to the NIC from the other host. NICs will send a signal and a voltage down the line which causes the other nic to illuminate on the link light. In some cases this link is power actually derived from the other box and as such till illuminate regardless of the power situation on the local machine. Some nics don't function that way but the design is only to demonstrate hardware links...not software compatibility or drive function.
If you have a link to a website that shows the model of your other NIC we might be able to give some pointers. But without knowing what kind it is, it make it kind of hard. Worst case scenario, take a picture of it (both sides) and post that here in this thread. -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »