LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 09-08-2013, 07:04 PM   #1
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 965

Rep: Reputation: 44
Slackware inet script no longer working


Hello,

I have migrated an existing slackware64 14 machine to a new machine which uses a Intel 82574L dual gigabit ethernet controller. After I had migrated the OS to the new machine, and setup things so I could login in the terminal locally, I have soon noticed that the machine was not acquiring an IP from my local router. Nothing on the LAN side (router, wiring, etc) has changed.

When I issue a manual

Code:
/etc/rc.d/rc.inet1 restart
it outputs nothing and after a second or two, returns to the prompt. On my other machines, when I issue the same command I see something like:

Code:
bash-4.1# /etc/rc.d/rc.inet1 restart
Polling for DHCP server on interface eth0:
dhcpcd[14022]: version 5.2.12 starting
dhcpcd[14022]: eth0: broadcasting for a lease
dhcpcd[14022]: eth0: offered 192.168.0.106 from 192.168.0.100
dhcpcd[14022]: eth0: acknowledged 192.168.0.106 from 192.168.0.100
dhcpcd[14022]: eth0: checking for 192.168.0.106
dhcpcd[14022]: eth0: leased 192.168.0.106 for 7200 seconds
dhcpcd[14022]: forked to background, child pid 14051
I tried to remedy to this problem by re-launching "netconfig" which last ran during the slackware install process. I kept the config the same as it was before.

On the faulty machine:

lspci
Code:
...
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
ifconfig -a

Code:
eth1: flags=4098<BROADCAST,MULTICAST>  mtu 1500
       ether XX:XX:XX:XX:05:03  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0  overruns 0  carrier 0  collisions 0
       device interrupt 47  memory 0xfeae0000-feb00000

eth2: flags=4098<BROADCAST,MULTICAST>  mtu 1500
       ether XX:XX:XX:XX:05:02  txqueuelen 1000  (Ethernet)
       RX packets 0  bytes 0 (0.0 B)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 0  bytes 0 (0.0 B)
       TX errors 0  dropped 0  overruns 0  carrier 0  collisions 0
       device interrupt 47  memory 0xfe9e0000-fea00000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
       inet 127.0.0.1  netmask 255.0.0.0
       inet6 ::1  prefixlen 128 scopeid 0x10<host>
       loop txqueuelen 0  (Local Loopback)
       RX packets 5543  bytes 899152 (878.0 KiB)
       RX errors 0  dropped 0  overruns 0  frame 0
       TX packets 5543  bytes 899152 (878.0 KiB)
       TX errors 0  dropped 0  overruns 0  carrier 0  collisions 0
dmesg | grep eth
Code:
[     16.....] e1000e 0000:02:00.0: eth0: (PCI Express:2.5GT/s:Width x1) XX:XX:XX:XX:05:02
[     16.....] e1000e 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection
[     16.....] e1000e 0000:02:00.0: eth0: MAC: 3, PJY: 8, PBA No: FFFFFF-0FF
[     16.....] e1000e 0000:03:00.0: eth1: (PCI Express:2.5GT/s:Width x1) XX:XX:XX:XX:05:03
[     16.....] e1000e 0000:03:00.0: eth1: Intel(R) PRO/1000 Network Connection
[     16.....] e1000e 0000:03:00.0: eth1: MAC: 3, PJY: 8, PBA No: FFFFFF-0FF
[     18.....] udevd[1837]: renamed network interface eth0 to eth2
The line in bold where udev moves eth0 to eth2 confuses me... And it would explain why ifconfig lists the interface having its MAC ending with "05:03" as eth1 while the other interface as eth2, but why would udev do that? Leftovers from the previous machine in the configuration??

lsmod lists the driver e1000e as being loaded and in use.

Id like to post more output but since there is no network connectivity, I am left to type everything by hand...

I hope someone can shed some light on this..

Last edited by lpallard; 09-08-2013 at 07:08 PM.
 
Old 09-08-2013, 07:15 PM   #2
lpallard
Member
 
Registered: Nov 2008
Location: Milky Way
Distribution: Slackware (various releases)
Posts: 965

Original Poster
Rep: Reputation: 44
LOL I fixed myself....

http://lordfu.wordpress.com/2010/10/...-eth0-to-eth1/

In case people wonder what happened..
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Wacom Bamboo no longer working in Slackware 13 metageek Slackware 7 11-11-2009 01:13 PM
Slackware 13.0. RT2500 wireless no longer working vdemuth Slackware 2 09-26-2009 03:09 PM
eth0 no longer works; does not have inet address (Ubuntu 8.10) BigNate37 Linux - Networking 2 02-14-2009 06:25 PM
Expect script to log in to server no longer working - fork broken?? mallarj Linux - General 1 05-06-2007 11:28 AM
inet not working after upgrading to mdk 10.0 combrains Linux - Networking 1 09-12-2004 04:32 PM


All times are GMT -5. The time now is 09:01 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration