I have an usused ethernet port that causes chatter in one of the log files. I know the command
ifconfig “port” down
will turn off the port. Where is the proper place (director/file) to add this command so it will be done upon booting?
Note there is no place in the bios to turn off this port.
If you blacklist the kernel module that drives it? Is that an option?
I don’t know how to blacklist anything, but it seems to me I need the module for the other ethernet port to work.
2014-01-20T00:50:31.089662-08:00 linux-wh01 dhcpcd[6352]: enp2s0: timed out
2014-01-20T00:50:31.091918-08:00 linux-wh01 dhcpcd[6352]: enp2s0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-enp2s0.info'
2014-01-20T00:50:31.109895-08:00 linux-wh01 dhcpcd[6352]: enp2s0: broadcasting for a lease
The system log will fill up with “broadcasting for a lease” messages unless I do the “ifconfig enp2s0 down”. If I knew where to put the command so it would be executed upon start up, that would just leave the error message only on boot up.
You could use YaST to disable the interface. Instead of activating at boot time, you could select ‘Manually’ or ‘Never’.
You don’t want to block that port (DHCP client).
If you do, your DHCP lease will expire.
Then another machine booting on your network can be assigned your IP address and your machine will be SOL.
Read up on how DHCP works, particularly DHCP lease TTL and why renewal is necessary.
Do as Deano suggests,
Disable (or remove) the interface. If you’re running NM, you can go into the network connection properties in NM and remove. If you’re running "classic ifup/ifdown) then you can disable in YAST as Deano describes.
HTH,
TSU
I found the “never” selection. Perfect. Thanks.
I have nothing plugged into that port. The mobo has two ethernet ports and I only use one. However, I don’t recall similar mobos with multiple ethernet ports filling up the system log with chatter.
I have the same messages regarding my ethernet interface… To be honest, I usually don’t concern myself with informational messages like that, as I know the cause. I predominantly use my wireless LAN , but my ethernet does get used at work for connecting to various network appliances, and the ethernet interface is set to ‘At Boot Time’, although I could just as easily set it to ‘On Cable Connection’ or ‘On Hotplug’. (Once NM starts up, the both interfaces are managed by that anyway.)